On Thu, Feb 12, 2015 at 7:49 PM, Kent Tenney wrote:
> On Thu, Feb 12, 2015 at 6:19 PM, Edward K. Ream
> wrote:
> > I can think of not the slightest reason to keep @auto or @shadow. Can
> you?
>
> Yes, if @nosent continues to require 'import file', otherwise no.
>
Let's keep the startup issues
On Thu, Feb 12, 2015 at 6:19 PM, Edward K. Ream wrote:
> I can think of not the slightest reason to keep @auto or @shadow. Can you?
Yes, if @nosent continues to require 'import file', otherwise no.
>
> In the next few days I will write code, enabled by an g.only_nosent switch,
> that will mak
I can think of not the slightest reason to keep @auto or @shadow. Can you?
In the next few days I will write code, enabled by an g.only_nosent switch,
that will make @auto and @shadow synonyms for @nosent. I want @auto and
@shadow gone yesterday.
Assuming all goes smoothly, expect 5.1 b1 in
This is the first step in making @shadow and @auto be synonyms for @nosent,
something that I want to do in the next few days.
Imo, it is unlikely that any bugs will be reported against the new code.
Unit tests more than adequately cover all the code cases.
Please report any problems immediatel
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 9:45 AM, Zoom.Quiet wrote:
> just today, i can not running Leo5.0-final through old scrip:
>
I suggest asking for help from the Apple brew people, or possibly the PyQt
people. The problems you are having arise from pyqt not being available.
Any other Leo users have any
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
Rev 0533a97 was intended to support @nosent, but it is broken in various
fairly serious ways. I plan to fix this later today.
The revised code will support a new 'kind' keyword argument to
c.recursiveImport, the method that all modern recursive import scripts are
assumed to use. The values of
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
just today, i can not running Leo5.0-final through old scrip:
$ python /opt/bin/leo/launchLeo.py
leoQt.py: can not import either PyQt4 or PyQt5.
Traceback (most recent call last):
File "/opt/bin/leo/launchLeo.py", line 7, in
import leo.core.runLeo
File "/opt/bin/Leo5.0-final/leo/core/runL
12 matches
Mail list logo
