flow Installing Leo — Leo 5.0 documentation
http://leoeditor.com/installing.html
re-check all :
$ brew doctor
...
Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run
On Thu, Feb 12, 2015 at 3:47 PM, Kent Tenney kten...@gmail.com wrote:
Perhaps the proper @auto importer could be used
if that would mean a new @nosent file got brought in
with the simple elegance of @auto:
+1
I'm not fond of menu-import file-browse-click
... file appearing
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
On Fri, Feb 13, 2015 at 7:59 AM, Kent Tenney kten...@gmail.com 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
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 edream...@gmail.com wrote:
On Fri, Feb 13, 2015 at 7:37 AM, Edward K. Ream edream...@gmail.com wrote:
On Fri, Feb 13, 2015 at 6:33 AM, Kent Tenney kten...@gmail.com wrote:
import issues aside, I see @nosent as @auto which keeps a
copy of the external file in the Leo file, persisting gnx and ua.
Yes.
The only reason I can think of to prefer @auto is if the Leo
file was dealing with so
On Fri, Feb 13, 2015 at 7:37 AM, Edward K. Ream edream...@gmail.com
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
On Fri, Feb 13, 2015 at 11:25 AM, Edward K. Ream edream...@gmail.com wrote:
On Fri, Feb 13, 2015 at 10:02 AM, Kent Tenney kten...@gmail.com 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
On Fri, Feb 13, 2015 at 10:02 AM, Kent Tenney kten...@gmail.com 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.
On Fri, Feb 13, 2015 at 11:56 AM, Kent Tenney kten...@gmail.com 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 Thursday, February 12, 2015 at 10:34:21 AM UTC-6, Edward K. Ream wrote:
Rev 0533a97 was intended to support @nosent, but it is broken in various
fairly serious ways. I plan to fix this later today.
This turned into a major project, and a major mystery. I ended up
reverting *parts* of
On Fri, Feb 13, 2015 at 2:23 AM, Zoom.Quiet zoom.qu...@gmail.com wrote:
flow Installing Leo — Leo 5.0 documentation
http://leoeditor.com/installing.html
re-check all :
$ brew doctor
[snip]
so just
$ brew link pyqt
Wow dear Leo come back ;-)
thanx for all.
the off
i
import issues aside, I see @nosent as @auto which keeps a
copy of the external file in the Leo file, persisting gnx and ua.
The only reason I can think of to prefer @auto is if the Leo
file was dealing with so many external files that size became
an issue.
Would @edit be the choice for managing
13 matches
Mail list logo
