As an experiment, I'm attempting to import my entire hard drive into a
leo doc. If everything goes well, I may get to the point where I use
Leo for the majority of interactions with my computer.
I stuck my latest effort in a new branch:
https://code.launchpad.net/~jessealdridge/leo-editor/leo-ha
Hello,
I've run into a situation where a cloned @shadow node under two
different @path headings is "lost" and no longer updated (only one of
the external derived files is up to date). Bug report including the
.leo and the derived files at
https://bugs.launchpad.net/leo-editor/+bug/370601
cheers,
first there is an exception thrown:
"NameError: global name LiteralProxyClass is not defined
in the class ProxyType (qtproxies.py) Line No: 133
def __getattribute__(cls, name):
try:
return type.__getattribute__(cls, name)
->except AttributeError:
retur
On Fri, May 1, 2009 at 4:10 PM, Kent Tenney wrote:
>
> I think true round-tripping would be great, but it is not
> expected. A post on the docutils list called it 'nearly impossible'.
>
> If Leo can import, edit and write, with an initial normalization,
> it would be great. The round-trip challen
On Fri, May 1, 2009 at 1:55 PM, Ville M. Vainio wrote:
>
> On Fri, May 1, 2009 at 9:29 PM, Edward K. Ream wrote:
>
>> There is a question of whether the importer should import the rST file
>> into an @rst tree, in such a way that writing that tree (with Leo's
>> write command, or with the rst pl
On Fri, May 1, 2009 at 3:12 PM, Ville M. Vainio wrote:
>
> I just tweaked conf.py a bit to enable pdf generation.
Thanks, Ville. Today's hacks to the FAQ broke some links. I'll fix this
soon.
Edward
--~--~-~--~~~---~--~~
You received this message because you
> I just tweaked conf.py a bit to enable pdf generation.
...
> http://vvtools.googlecode.com/files/Leodocumentation.pdf
Many thanks Ville!
--matt
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
> Edward K. Ream wrote:
> > I like to listen to classical music while I program. A great way to
> > do this is by setting up classical music stations on Pandora:
> > http://www.pandora.com/
> >
> > Just select a classical composer or piece of music. My favorite at
> > present is based on a piano
I just tweaked conf.py a bit to enable pdf generation.
Howto:
QQQ
4. To create pdf (probably easiest on Linux, with necessary latex
packages installed):
- make latex
- cd _build/latex
- make all-pdf
QQQ
There were several errors in the pdf generation process. Notably,
there are probably lots
On May 1, 2:19 pm, "Edward K. Ream" wrote:
A section a level 5 could follow a
> section at level 2. The rst3 plugin presently has no way of
> representing this situation. In particular, @rst-no-head does not
> increase the section level of child sections. Obviously, the the
> solution is to
On May 1, 2:26 pm, "Ville M. Vainio" wrote:
> It seems you are thinking of precedessor of rst, StructuredText, that
> actually used indentation to represent chapter "depth". rst does not
> do nor support such a thing. Normal chapter text in rst document is at
> column zero, regardless of the "de
On May 1, 2:15 pm, "Ville M. Vainio" wrote:
> But full chapters should never be indented at all. If there is
> indentation in "normal" rst source (and it's not block quote, list
> item or some such), it should be consider bad rst and not be supported
> at all.
This may turn out to be mostly a n
On Fri, May 1, 2009 at 10:19 PM, Edward K. Ream wrote:
> representing this situation. In particular, @rst-no-head does not
> increase the section level of child sections. Obviously, the the
> solution is to add something like @rst-indent that *does* increase the
> indentation level of descenda
On May 1, 2:03 pm, "Edward K. Ream" wrote:
> 4. We can imagine anomalous situations in which indentation in the original
> file does not correspond to the underlining characters.
In contrast with other importers, for which underindented code causes
problems, with the rST importer there is pro
On Fri, May 1, 2009 at 10:03 PM, Edward K. Ream wrote:
> 4. We can imagine anomalous situations in which indentation in the original
> file does not correspond to the underlining characters. Perhaps, as Ville
But full chapters should never be indented at all. If there is
indentation in "normal"
On Fri, May 1, 2009 at 1:55 PM, Ville M. Vainio wrote:
>
> On Fri, May 1, 2009 at 9:29 PM, Edward K. Ream
> wrote:
>
> > There is a question of whether the importer should import the rST file
> > into an @rst tree, in such a way that writing that tree (with Leo's
> > write command, or with the r
On Fri, May 1, 2009 at 1:29 PM, Edward K. Ream wrote:
>
> Rev 1775 contains a start on the grand rst round-tripping project.
> This "start" serves mostly to show the problems that remain.
After a short break, it seems that most of the problems can be resolved
fairly easily. In this "reply" I'd
On Fri, May 1, 2009 at 9:29 PM, Edward K. Ream wrote:
> There is a question of whether the importer should import the rST file
> into an @rst tree, in such a way that writing that tree (with Leo's
> write command, or with the rst plugin) would faithfully recreate the
> original file. The proble
On Fri, May 1, 2009 at 1:47 PM, Ville M. Vainio wrote:
>
> On Fri, May 1, 2009 at 9:29 PM, Edward K. Ream
> wrote:
>
> > - At present there are no other mechanisms that would allow Leo to
> > remember the underlining in effect in the original rst file, or the
> > indentation in effect in the ori
On Fri, May 1, 2009 at 9:29 PM, Edward K. Ream wrote:
> - At present there are no other mechanisms that would allow Leo to
> remember the underlining in effect in the original rst file, or the
> indentation in effect in the original.
I'm not sure indentation should remain in effect in the first
Rev 1775 contains a start on the grand rst round-tripping project.
This "start" serves mostly to show the problems that remain.
What I did:
- Added rstScanner class and related machinery to leoImport.py.
- Added a script in test.leo that calls this scanner.
- Made Leo aware that .rst and .rest
On May 1, 5:08 pm, "Edward K. Ream" wrote:
> Note that p.level() does exist, so you can perform calculations relative to
> root.level().
Great, this is an important hint for me. Thank you.
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On May 1, 9:13 am, "Edward K. Ream" wrote:
> I may just rewrite the FAQ slightly so only the top-level stuff gets put
> into the sidebar. It's a good enough work-around for now...
The new FAQ is on Leo's web site. It avoids generating html sections,
so the toc is short enough to be useful.
On Thu, Apr 30, 2009 at 11:48 AM, Edward K. Ream wrote:
>
>>
>> You may find Doug Hellmann's article on his use of Sphinx interesting,
>> it was one of the inspirations for my own trials:
>>
>>
>> http://blog.doughellmann.com/2009/02/writing-technical-documentation-with.html
>
>
> Thanks for this.
On Thu, Apr 30, 2009 at 3:20 PM, Kent Tenney wrote:
>
> Howdy,
>
> Today I wanted to write rst from Leo using @rst file.name
> Rst3 shows in Menu => Plugins but no "Write-Restructured-Text" under
> Menu => Edit,
> no write-restructured-text
This is another instance of Leo's flexibility causing
On Fri, May 1, 2009 at 5:47 AM, zpcspm wrote:
>
> Let's assume there is a subtree in a leo outline.
> I define the level of a certain node in that subtree (relative to the
> root of that subtree), as the amount of nodes up to the root of the
> subtree.
> For example:
>
> - the root node of the su
Let's assume there is a subtree in a leo outline.
I define the level of a certain node in that subtree (relative to the
root of that subtree), as the amount of nodes up to the root of the
subtree.
For example:
- the root node of the subtree has level 0 (relative to itself)
- any child of the root
27 matches
Mail list logo
