This thread is inspired (and inspired is the right word) by Kent's
stinging comment about "annoying breakthroughs" :-) Stinging comments
can be a "whack on the side of the head", that is, a spur to
creativity.
First, let me say that my short responses in the thread "Two
questions: quality, unders
On Oct 30, 9:19 am, "Edward K. Ream" wrote:
> I've been thinking about two general questions lately:
I'd like to revise them both slightly:
1. How can we improve Leo's quality?
2. How can we better understand complex computer programs?
The thread "Long/short details/dreams" discussed two appro
On Nov 3, 12:06 am, "Edward K. Ream" wrote:
> 4. html often will contain javascript code that has its own syntax
> rules. I'm not sure this makes any difference, actually.
I am not sure either, isn't javascript supposed to be always wrapped
in a
On Fri, Oct 28, 2011 at 12:30 AM, SegundoBob wrote:
>> On Thu, Oct 27, 2011 at 6:54 AM, Ville M. Vainio wrote:
>>
>> I suppose we shall have to discuss what we think the "right" defaults
>> are--it's a rare case of having to discuss preferences.
>
> I vote for consistency: red border on body pa
On Thu, Nov 3, 2011 at 6:55 AM, Ville M. Vainio wrote:
> Is there a way to disable this red border? It's quite offensive to my
> sensibilities, to the extent that it hurts my concentration when
> writing.
@bool use_focus_border = False disables all borders.
> It's also likely to nullify all the
How about just disabling it in body? I like the focus rect in tree pane.
On 03/11/2011 14:43 Edward K. Ream wrote:
On Thu, Nov 3, 2011 at 6:55 AM, Ville M. Vainio wrote:
> Is there a way to disable this red border? It's quite offensive to my
> sensibilities, to the extent that it hurts my conc
On Thu, Nov 3, 2011 at 8:11 AM, wrote:
> How about just disabling it in body? I like the focus rect in tree pane.
Rev 4717 adds support for @bool use_body_focus_border.
Very sorry, but the default in leoSettings.leo is True ;-)
Edward
--
You received this message because you are subscribed t
On Thu, Nov 3, 2011 at 5:09 AM, zpcspm wrote:
> On Nov 3, 12:06 am, "Edward K. Ream" wrote:
>> 4. html often will contain javascript code that has its own syntax
>> rules. I'm not sure this makes any difference, actually.
>
> I am not sure either, isn't javascript supposed to be always wrapped
>
On Wed, Nov 2, 2011 at 9:17 PM, Terry Brown wrote:
> If it helps at all, the ElementTree model is that elements have
> both .text and .tail attributes.
[snip]
> Pythons flagship XML library is lxml of course, http://lxml.de/, but it
> basically uses ElementTree for element representation.
I do
On Thu, Nov 3, 2011 at 8:58 AM, Edward K. Ream wrote:
> P.S., here is the common tokenizer for the import code...
> But as I write this, I see that there is something simpler.
The new tokenizer is on the trunk at rev 4718. For the first time,
the underindented html comment unit test passes, as
On Thu, 3 Nov 2011 08:43:13 -0500
"Edward K. Ream" wrote:
> Right. The question is, are html tags valid in javascript comments
> :-) It's a question only a compiler writer would ask...
Probably not relevant to Leo import export, but javascript often
contains things not valid in HTML, notably <
Warning, I am still using plain old Leo-4.9
when I try to run the rst3 command on a line like: @rst foo.pdf I
get:
Traceback (most recent call last):
File "/home/dalcolmo/programs/Leo-4.9-final/leo/core/leoRst.py",
line 1891, in writeToDocutils
settings_overrides=overrides)
File "/usr/li
On Thu, Nov 3, 2011 at 10:27 AM, Terry Brown wrote:
> Probably not relevant to Leo import export, but javascript often
> contains things not valid in HTML, notably < and &
Yikes.
>
> Which raises the question of
> CDATA http://www.w3schools.com/xml/xml_cdata.asp
> strictly speaking Leo should no
On Thu, Nov 3, 2011 at 10:49 AM, Josef wrote:
> Warning, I am still using plain old Leo-4.9
>
> when I try to run the rst3 command on a line like: @rst foo.pdf I
> get:
Happens with the present code as well. I'll investigate soon.
Edward
--
You received this message because you are subscribe
On Thu, Nov 3, 2011 at 10:45 AM, Terry Brown wrote:
> More generally, why do I not think the tree is all we'll ever need?
> Well, why is a tree better than a list of text-nodes? All it does is
> make it easier to see the structure, it doesn't let you do anything you
> couldn't do with a list. M
On Nov 3, 10:27 am, Terry Brown wrote:
> strictly speaking Leo should not parse anything in a CDATA block.
I *think* the html scanner can treat cdata as a kind of comment, for
purposes of verification. The html parser, that is,
xmlScanner.startshelper, should also know about cdata. Neither sho
Hi, mdb,
Thanks a lot. Today finally tested your suggestion with my friedn and it
worked like a charm.
Offray
On 10/26/11 07:16, mdb wrote:
Try this
Create a batch file, named "leo.bat "in c:\ root
that is simply
C:\Python27\pythonw.exe "C:\Leo-4.9-final\launchLeo.py" %1
or to run in
>> Amazing. I'll put this into Leo's home page tonight, on an
>> experimental basis...
>
> Hah! I just came here from the rss feed on Leo's home page!!
hey, that's a nice simple added touch of life.
>Files, including home page-->@file html/front.html
I just tried to look at that file, the node
>> It looks like all potential editors of the wiki will have to be approved.
>
> Simon will probably agree to set this up. Let me know if you would
> like write access.
yes please.
-matt
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post t
Howdy,
Leo is recognizing urls and rendering them in a large font, underlined.
I prefer they be the same size as other text.
I checked
@setting
@font url
but it seems something else is making the change.
Plugin?
Thanks,
Kent
--
You received this message because you are subscribed to the Googl
On Thu, Nov 3, 2011 at 3:18 PM, Matt Wilkie wrote:
>>Files, including home page-->@file html/front.html
>
> I just tried to look at that file, the node is there but front.html
> doesn't exist. I just did a "bzr pull --overwrite" a few minutes ago.
front.html and index.html are exactly the same f
On Thu, Nov 3, 2011 at 12:08 PM, Edward K. Ream wrote:
> On Thu, Nov 3, 2011 at 10:49 AM, Josef wrote:
>> when I try to run the rst3 command on a line like: @rst foo.pdf I get:
> Happens with the present code as well. I'll investigate soon.
Fixed on the trunk at rev 4720. I had forgotten I
On Thu, Nov 3, 2011 at 4:13 PM, Kent Tenney wrote:
> Leo is recognizing urls and rendering them in a large font, underlined.
> I prefer they be the same size as other text.
For questions like this, do print-settings. Doing so shows something like::
urlcolor = purple
urlfontfamily = Dej
On Thu, Nov 3, 2011 at 5:22 PM, Edward K. Ream wrote:
> On Thu, Nov 3, 2011 at 4:13 PM, Kent Tenney wrote:
>
>> Leo is recognizing urls and rendering them in a large font, underlined.
>> I prefer they be the same size as other text.
>
> For questions like this, do print-settings. Doing so shows
As of rev 4725, unit testing in leoPy.leo feels *completely*
weightless. The last change: running any unit test externally saves
the .leo file automatically first.
Thus, Alt-4 runs all desired unit tests immediately. To select/
deselect unit tests, just mark/unmark @test nodes.
The difference i
On Nov 3, 9:17 pm, "Edward K. Ream" wrote:
> As of rev 4725, unit testing in leoPy.leo feels *completely*
> weightless. The last change: running any unit test externally saves
> the .leo file automatically first.
I found that saving unitTest.leo automatically was off-putting, so
running local
On Thu, Nov 3, 2011 at 7:53 PM, Kent Tenney wrote:
> Right, I'd looked at that node and seen
> url_font_family = DejaVu Sans Mono
> url_font_size = 12
> Yet the font is very large, so I'm wondering where the large
> font size is coming from.
There seems to be a difference in how fonts are handl
On Sun, Oct 30, 2011 at 8:50 AM, Edward K. Ream wrote:
> It appears the problem is in g.os_path_finalize_join. I'll investigate.
g.os_path_join works; g.os_path_finalize doesn't. I'll have the fix shortly.
BTW, all investigations now take place in the context of a unit test.
This is just gre
28 matches
Mail list logo