Re: Advices for a leo cub - Want to turn Leo into basic Sphinx editor

Really ? g.es(c) ! :D I think I had a look at every c submodules... So stupid I am ! Thanks for that ! -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+

Re: Advices for a leo cub - Want to turn Leo into basic Sphinx editor

On Tue, Nov 11, 2014 at 7:56 PM, Davy Cottet wrote: > PS : a very practical question to finish : which Leo command return the > path of the currently opened .leo project ? It's very complicated: c :)From the scripting page : - c is the co

Re: Advices for a leo cub - Want to turn Leo into basic Sphinx editor

On Tue, 11 Nov 2014 19:56:24 -0800 (PST) Davy Cottet wrote: > - From Kent & Thierry exchanges, I deduce that converting a leo tree > structure to a folder/file structure is not as trivial as I > thought... If I understand well, active-path.py does only the other > way ? Are'nt @file & @auto able

Re: Advices for a leo cub - Want to turn Leo into basic Sphinx editor

Thanks every one for your contribution to this subject. I have to accept that I got a bit lost on the discussion about databases ;)... anyway, i got a lot of useful informations there. - @Edward : *"At present, Leo's core rst related code is, of course, based on reStructuredText, not sphinx.

rst3 indentation errors can override?

If the body has an indented line we can get this error on creating rst3 System Message: ERROR/3 (, line 1032) Unexpected indentation. is there a way to deal easily with these errors? probably an input language type? Thanks! -- You received this message because you are subscribed to the Google

Bug #66 re markdown fixed, but there are fragile edge cases

Rev da409c6 fixes bug #66: errors inhibited read @auto foo.md https://github.com/leo-editor/leo-editor/issues/66 Please test and report any problems. There are several edge cases involving the "perfect i

Re: Standarizing Leo outlines

On Tue, 11 Nov 2014 08:53:02 -0800 (PST) Fidel N wrote: > Thanks Edward for your last remark on this discussion > . > > Thinking on Leo versatility, often the "reason" given in the group > for Leo not to have useful / shared tools

Standarizing Leo outlines

Thanks Edward for your last remark on this discussion . Thinking on Leo versatility, often the "reason" given in the group for Leo not to have useful / shared tools is its great versatility, but the problem is we are confusing vers