On Wed, Jun 28, 2017 at 2:48 PM, vitalije wrote:
@Edward, I have another question. Where is the point where the actual
reading of Leo document ends and data is transferred in the tree.
To be more concrete I have found in method getLeoFileHelper of
FileCommands class the
On Wed, 28 Jun 2017 12:48:06 -0700 (PDT)
vitalije wrote:
> > I would be happy with that, provided that a) settings can be
> > organized
> >> and b) per-document (.leo file) settings are possible. The best
> >> way of organizing anything is in a .leo file.
> >
> As I
>
> I would be happy with that, provided that a) settings can be organized
>> and b) per-document (.leo file) settings are possible. The best way of
>> organizing anything is in a .leo file.
>
> As I wrote in the earlier post today, it is trivial in sqlite to open
connection to several
On Wed, 28 Jun 2017 13:25:39 -0500
"Edward K. Ream" wrote:
> On Wed, Jun 28, 2017 at 12:05 PM, Terry Brown
> wrote:
>
> > On Wed, 28 Jun 2017 06:39:41 -0700 (PDT)
>
> The success of the current
> >
> > code in the context of 1. is questionable,
On Wed, Jun 28, 2017 at 12:05 PM, Terry Brown wrote:
> On Wed, 28 Jun 2017 06:39:41 -0700 (PDT)
>
The success of the current
>
> code in the context of 1. is questionable, seeing new and even
> experienced users struggle with settings management.
>
Imo few (none?)
On Wed, Jun 28, 2017 at 11:01 AM, vitalije wrote:
By transferring to ClojureScript I have discovered some very cool projects
>> that I could not imagine were possible at all. One of the coolest things is
>> writing reloadable code. I am amazed how cool it is to make small
Yes, Smalltalk has liveness build in the core experience since early
releases. Is something that you can not find almost anywhere the common
experience of programming and computing in general. Recently I was
reading about how this liveness impressed Steve Jobs and his team and
inspired much of the
On Wed, Jun 28, 2017 at 11:01 AM, vitalije wrote:
Every ivar that caches settings can be turned into property that gets its
>> value from c.config.get<
>> something>.
>>
>
Excellent idea. There is a performance penalty, but it is not likely
significant.
It wouldn't be so
On Wed, 28 Jun 2017 12:10:27 -0500
Offray Vladimir Luna Cárdenas wrote:
> Using Pharo Smalltalk I have experienced a similar feeling about a
> direct live system where changes are reflected immediately without
> any reload.
Years ago someone showed me the Squeak Smalltalk
Hi,
Using Pharo Smalltalk I have experienced a similar feeling about a
direct live system where changes are reflected immediately without any
reload. Also I have shared that dealing with traversing the settings
three could be cumbersome and you need to read a lot before having the
change you
On Wed, 28 Jun 2017 06:39:41 -0700 (PDT)
"Edward K. Ream" wrote:
> 1. Clarity and simplicity of *purpose*.
> 2. Stability and simplicity of *user interface*, including gui and
> scripting api.
> 3. Simplicity of *code*.
[snip]
> In this discussion, the first two
On Wed, 28 Jun 2017 07:55:41 -0700 (PDT)
"Edward K. Ream" wrote:
> But in fact, I run all unit tests before virtually every commit. All
> other devs should too.
Here are the fails I get from d1608d30.
I always forget to run unit tests before making changes, so I have to
Thanks.
On Wednesday, June 28, 2017 at 4:51:56 PM UTC+2, Edward K. Ream wrote:
>
> On Wednesday, June 28, 2017 at 8:42:46 AM UTC-5, vitalije wrote:
>>
>> I would prefer if Leo wouldn't report nodes that differ in any number of
>> empty lines.
>>
>
> Rev d1608d of master should fix this. Let me
Someone asked how this proposition can help users. I wasn't clear about
that. It won't help that much unless reloading is also addressed. But there
are some settings that aren't so obvious when represented as a text.
Colors, shortcuts for example. Now it is required that a user writes them
as
>
>
> For example, yesterday I discovered a settings table that inited several
> commander ivars. My first thought was, maybe this table could go away.
> But no. These ivars appear all over Leo. It would be horrible to use
> c.config.getInt or c.config.getBool in their stead. So this
But in fact, I run all unit tests before virtually every commit. All other
devs should too.
And periodically I also run pylint -a
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails
On Wednesday, June 28, 2017 at 8:42:46 AM UTC-5, vitalije wrote:
>
> I would prefer if Leo wouldn't report nodes that differ in any number of
> empty lines.
>
Rev d1608d of master should fix this. Let me know if it doesn't.
Edward
--
You received this message because you are subscribed to
On Wed, Jun 28, 2017 at 8:42 AM, vitalije wrote:
> The other day I think I have read somewhere in Leo's code that it is
> supposed not to report in recovered nodes those nodes that differ in just
> one empty line. In my tool collection something is regularly causing Leo to
>
The other day I think I have read somewhere in Leo's code that it is
supposed not to report in recovered nodes those nodes that differ in just
one empty line. In my tool collection something is regularly causing Leo to
report a lot of recovered nodes that differ not in one empty line but in
On Tuesday, June 27, 2017 at 12:24:24 PM UTC-5, Terry Brown wrote:
> On Tue, 27 Jun 2017 11:27:27 -0500
> "Edward K. Ream" wrote:
>
> > How does that help new users?
>
> That's the problem with this proposal, it's so overloaded with benefits
> it's hard to keep them
This was the binding (created in quicksearch.py) in effect before a recent
change. My apologies for the trouble this has caused. I did not do proper
testing after disabling the binding.
Eventually, leoSettings.leo will contain this default setting, but #510:
bindings to commands...
21 matches
Mail list logo