On Fri, Feb 13, 2015 at 11:56 AM, Kent Tenney wrote:
>
> >> '@nosent now parses known file types' (and persists)
> >
> >
> > False.
>
> Different implementation, but does it look different to the user?
>
I did a few comparisons between
> import -> @nosent
> and
> @auto rclick -> refresh
>
> The
On Fri, Feb 13, 2015 at 11:25 AM, Edward K. Ream wrote:
>
>
> On Fri, Feb 13, 2015 at 10:02 AM, Kent Tenney wrote:
>>
>> I think of the current changes in terms
>> '@auto is now persistent' (and is called @nosent)
>
>
> True.
>
>>
>> '@nosent now parses known file types' (and persists)
>
>
> Fals
On Fri, Feb 13, 2015 at 10:02 AM, Kent Tenney wrote:
> I think of the current changes in terms
> '@auto is now persistent' (and is called @nosent)
>
True.
> '@nosent now parses known file types' (and persists)
>
False.
@nosent uses diff + the @shadow update algorithm. @nosent does *not*
I think of the current changes in terms
'@auto is now persistent' (and is called @nosent)
or
'@nosent now parses known file types' (and persists)
On Fri, Feb 13, 2015 at 9:52 AM, Edward K. Ream wrote:
> On Fri, Feb 13, 2015 at 7:37 AM, Edward K. Ream wrote:
>
>> 1. It is not always clear which
On Fri, Feb 13, 2015 at 7:37 AM, Edward K. Ream
wrote:
1. It is not always clear which importer to use. That's why we have
> @auto-rst, @auto-vo, @auto-otl. I shall be *so* happy when these wretched
> hacks sail off into the sunset. Otoh, we shall soon need the corresponding
> flavors of the
On Fri, Feb 13, 2015 at 7:59 AM, Kent Tenney wrote:
> >the question is what should happen if the user has *not* already
> populated the @nosent tree >before exiting Leo.
>
> I'd expect things to be the same as when the user exited:
> an unpopulated @nosent node, waiting to be populated. Or not.
>
>the question is what should happen if the user has *not* already populated the
>@nosent tree >before exiting Leo.
I'd expect things to be the same as when the user exited:
an unpopulated @nosent node, waiting to be populated. Or not.
On Fri, Feb 13, 2015 at 7:37 AM, Edward K. Ream wrote:
> On
On Thu, Feb 12, 2015 at 3:47 PM, Kent Tenney wrote:
> > Perhaps the proper @auto importer could be used
>
> if that would mean a new @nosent got brought in
> with the simple elegance of @auto:
> +1
>
> I'm not fond of menu->import file->browse->click
> ... file appearing parented by
>
Another +1 from me :)
-->Jake
On Feb 12, 2015, at 4:47 PM, Kent Tenney wrote:
>> Perhaps the proper @auto importer could be used
>
> if that would mean a new @nosent got brought in
> with the simple elegance of @auto:
> +1
>
> I'm not fond of menu->import file->browse->click
> ... file app
> Perhaps the proper @auto importer could be used
if that would mean a new @nosent got brought in
with the simple elegance of @auto:
+1
I'm not fond of menu->import file->browse->click
... file appearing parented by an 'imported files' node
Thanks,
Kent
On Thu, Feb 12, 2015 at 10:40 AM, Edward
On Thu, Feb 12, 2015 at 10:24 AM, Kent Tenney wrote:
> When I create a node like
> @nosent myfile.py
>
> and rclick->Refresh from disk
>
> I get the entire file in the body ala @edit,
> not parsed into a node tree like @auto
>
Use import-file to create the original outline. After that, refresh
When I create a node like
@nosent myfile.py
and rclick->Refresh from disk
I get the entire file in the body ala @edit,
not parsed into a node tree like @auto
Is that just me?
The docs seem to indicate known file types get parsed.
On Thu, Feb 12, 2015 at 9:59 AM, Edward K. Ream wrote:
> Here a
Here are the new docs, hot off the presses.
http://leoeditor.com/tutorial-programming.html#using-nosent-nodes
All suggestions welcome. I'll be updating other parts of the docs soon.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsu
13 matches
Mail list logo
