On Wed, 2 Nov 2011 15:06:00 -0700 (PDT)
"Edward K. Ream" wrote:
> 2. As Terry has just corrected me, the difference between one space
> (or tab) and many is not significant, yet the difference between one
> and none is significant. A redesign of the importer (tokens) may be
> needed.
If it help
On Oct 28, 3:49 am, zpcspm wrote:
> Sometimes I have to look at badly aligned HTML code and keep asking
> myself questions like "here's the opening tag, I wonder where it
> closes".
A progress report.
I have spent several hours on this. It's an interesting problem, for
several reasons:
1. html
On Wed, Nov 2, 2011 at 2:45 PM, Terry Brown wrote:
> there's no difference between one whitespace char and an hundred, but
> the difference between zero and one is significant.
Thanks. Back to the drawing board :-)
Edward
--
You received this message because you are subscribed to the Google
On Wed, 2 Nov 2011 13:21:22 -0500
"Edward K. Ream" wrote:
> > foobar
> >
> > is not the same as
> >
> > foo bar
>
> How are they different?
One would display 'foobar', the other 'foo bar'. Same with
foobar
vs
foo
bar
there's no difference between one whitespace char and an hundre
On Oct 31, 11:30 am, "Edward K. Ream" wrote:
> 3. We want three kinds of (local) unit tests::
>
> run-all-unit-tests-locally
> run-selected-unit-tests-locally
> run-marked-unit-tests-locally
The run-marked-unit-tests-locally/externally commands now work with
less surprise.
A. If
On Wed, Nov 2, 2011 at 1:06 PM, mdb wrote:
> It seems Ed is saying this continuation of tinkering will only yield marginal
> improvements.
I am a great believe in marginal (continuous, incremental)
improvements, as I have often said. That's what turned the Wright
Flyer into the 787. It's what
On Wed, Nov 2, 2011 at 10:34 AM, Terry Brown wrote:
> foobar
>
> is not the same as
>
> foo bar
How are they different?
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-editor@googlegroups.com.
I now understand Ed's 2 questions better
My impression is 90% or more of Leo users create and manage computer
programs using outlines with or without clones. A smaller fraction
create and use Leo scripts as buttons or key bindings to make the
program management and use easier. It seems Ed is sa
On Wed, 2 Nov 2011 08:03:19 -0700 (PDT)
"Edward K. Ream" wrote:
> After all, whitespace is completely irrelevant
> outside of comments and strings.
Depends how you define 'string'
foobar
is not the same as
foo bar
hmm, I guess the space is the string. Anyway, probably not relevant.
BTW
For the last several days I've been working on the infrastructure
behind Leo's importers. This is intertwined with Leo's unit-testing
code, mostly via g.app.unitTestDict.
As I did so, I have found several problems.
1. As discussed in another thread, I have improved the support for
running tests
I would have preferred a bit more testing of this change, but I
thought it best to push what I had so as to make the Plugins menu
functional again :-)
All day yesterday I worked on two related tasks:
1. Basing the import checks on tokens, rather than characters. This
gives the verify much more c
On Nov 1, 12:16 pm, "Edward K. Ream" wrote:
> > As of rev 4690, Leo supports "hidden" unit tests. This just may be
> > the missing piece of Leo's unit testing arsenal.
>
> The more I use hidden unit tests, the less I like them. It's
> frustrating: the are *almost* exactly what is wanted, but
On Wed, Nov 2, 2011 at 7:13 AM, Juraj wrote:
> Hello,
>
> I am trying to use macros plugin, when testing the example from
> documentation I get this error:
Thanks for this report. Rev 4707 revises the code properly (I am
guessing) for Leo's present code base. Clearly the old code is
ancient.
H
On Wed, Nov 2, 2011 at 8:24 AM, Kent Tenney wrote:
> Leo _itself_ is the breakthrough tool for understanding. It's a platform
> for data management like no other. As a platform, it can provide the
> tools to break through barriers to understanding complexity by
> accommodating our proclivities.
On Tue, Nov 1, 2011 at 12:08 PM, Edward K. Ream wrote:
> On Tue, Nov 1, 2011 at 9:04 AM, Kent Tenney wrote:
>
>> Right, IYO it is a convenience, IMO it is critical.
>> The difference is due to different learning styles and problem domain.
>
> Ok, so it's critical. It's also not the question I wa
On Wed, Nov 2, 2011 at 4:37 AM, lewis wrote:
> Edward,
>
> Running Leo build 4693 and selecting Plugins>Core>Plugins Menu doesn't
> display any output or window.'
> Also for any active plugin e.g. Plugins>todo there is no output to
> screen.
Thanks for this report. The fix is on the trunk at rev
Hello,
I am trying to use macros plugin, when testing the example from
documentation I get this error:
Traceback (most recent call last):
File "C:\Python32\Leo-4.9-final\leo\core\leoCommands.py", line 408,
in doCommand
val = command(event)
File "C:\Python32\Leo-4.9-final\leo\plugins\macro
Edward,
Running Leo build 4693 and selecting Plugins>Core>Plugins Menu doesn't
display any output or window.'
Also for any active plugin e.g. Plugins>todo there is no output to
screen.
I confirmed previous builds work fine and display plugin info.
Leo Log Window
Leo 4.9.1 devel, build 4669, 4Q/20
18 matches
Mail list logo
