Re: @clean/@auto files are not always written

[gar]

Edward, I also want to note, that I switched away from @auto to @clean
files (I was hoping  that bug will go away).
And now not totally sure that the things I told you above happen with @auto.
But they definitely do with @clean.

сб, 7 дек. 2019 г. в 01:28, Edward K. Ream :

>
>
> On Fri, Dec 6, 2019 at 3:17 PM gar  wrote:
>
>> пт, 6 дек. 2019 г. в 22:35, Edward K. Ream :
>>
>>> You saw "color:white" in the log??
>>>
>> No, it's a mistype. I sometimes dont see standart 'wrote: filename.auto'
>> message
>>
>
> It looks like some file-caching code may be involved.  If so, I'm going to
> ban file caching :-) The benefits don't begin to outweigh the pain when
> things go wrong.
>
> Edward
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/CAMF8tS2p6RnD4CikQirtCOfAiLfc%3DmDhCD7nBZb-Hbw5shH1bA%40mail.gmail.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVz8Z5ig%3DmCC0d68_RoHAXtxvUP0T9nHWz_O8%2Bu22x1Org%40mail.gmail.com.

Re: @clean/@auto files are not always written

[Edward K. Ream]

On Fri, Dec 6, 2019 at 3:17 PM gar  wrote:

> пт, 6 дек. 2019 г. в 22:35, Edward K. Ream :
>
>> You saw "color:white" in the log??
>>
> No, it's a mistype. I sometimes dont see standart 'wrote: filename.auto'
> message
>

It looks like some file-caching code may be involved.  If so, I'm going to
ban file caching :-) The benefits don't begin to outweigh the pain when
things go wrong.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2p6RnD4CikQirtCOfAiLfc%3DmDhCD7nBZb-Hbw5shH1bA%40mail.gmail.com.

Re: @clean/@auto files are not always written

[gar]

пт, 6 дек. 2019 г. в 22:35, Edward K. Ream :

> You saw "color:white" in the log??
>
No, it's a mistype. I sometimes dont see standart 'wrote: filename.auto'
message

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVyNbx161z%3DXBossPGTsYv6Xvk2kZ4b1Jmt8MmqrLLopSg%40mail.gmail.com.

Re: the autosave plugin: doc bug? how to enable and configure

[Edward K. Ream]

On Fri, Dec 6, 2019 at 2:43 PM 'Terrence Brannon' via leo-editor <
leo-editor@googlegroups.com> wrote:

The autosave plugin says that it saves every 300 seconds by default. But
> the .getInt() call in the code does not have a default value. So I doubt
> that it really saves every 300 seconds by default.
>

leoSettings.leo contains @int mod-autosave-interval = 300, so the default
is indeed 300.

To customize, make sure @bool mod-autosave-active = True (in your
myLeoSettings.leo) and set the interval as you like, again in your
myLeoSettings.leo.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS12PxXSgje2Fpu-KZn0Zf0fxBw80uHm88vHMMFGxUeeLw%40mail.gmail.com.

the autosave plugin: doc bug? how to enable and configure

['Terrence Brannon' via leo-editor]

The autosave plugin says that it saves every 300 seconds by default. But 
the .getInt() call in the code does not have a default value. So I doubt 
that it really saves every 300 seconds by default.

Next, I'm not sure where to put the settings for this plugin versus where 
to put the @enabled-plugins node. I am pasting my Leo graph which has both 
the settings and @enabled-plugins node and request someone to RSVP as to 
whether I have done it correctly:



http://leoeditor.com/namespaces/leo-python-editor/1.1; 
>





@settings
@enabled-plugins

ConnectorRegistry
base connector
model classes
class 
BaseDatasource(AuditMixinNullable, ImportMixin)
class BaseColumn(AuditMixinNullable, 
ImportMixin)
class BaseMetric(AuditMixinNullable, 
ImportMixin)

view classes
class 
DatasourceModelView(SupersetModelView)




@int mod_autosave_interval = 30

bool mod_autosave_active = True
class ConnectorRegistry(object):
""" Central Registry for all available datasource engines"""







mod_autosave.py



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/df6df04a-0960-4447-95e7-002d312f577f%40googlegroups.com.

Re: @clean/@auto files are not always written

[Edward K. Ream]

On Thu, Dec 5, 2019 at 12:58 AM gar  wrote:

> After some days of observations I made a conclusion that the most
> probability to silently skip saving have files with small changes
> introduced since last save.
> If I change 5-10 LOCs - then file is generally written normally.
> If I say change a propertie's value in the css - it can be ignore with a
> chance of 15-20%.
> For now I track changed files by their icons with my eyes and carefully
> read what leo writes to log pane - and if line with `written:
> file_with_small_changes.css` is missing then I start to play around with
> doing useless changes until file is saved.
> Well it's kinda not the thing I expect to use in the 21st century :-)
>

My apologies for these troubles. There is indeed some logic concerning
"small changes".  It's supposed to be involved in the @auto logic somehow,
I don't remember the details. Perhaps the logic is being used
inappropriately.  This is an important clue.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0oEggcn5KVLZ3VLwz2D%3DyXwaOPisymH%2BmXaKyZ%3Dz%2Bb6w%40mail.gmail.com.

Re: @clean/@auto files are not always written

[Edward K. Ream]

On Thursday, December 5, 2019 at 1:48:51 PM UTC-6, gar wrote:
>
> Tonight when I changed my @clean html file with a single line ending and 
> saved the .leo I saw the following line in the log: color:white
>

You saw "color:white" in the log??

So this is definitely something's wrong with the code responsible for 
> discovering dirty nodes.
>

I agree. I'll get to it next.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c4e0f402-6ed8-40af-ae02-9ce579d0c099%40googlegroups.com.

Re: leointeg status report

[Edward K. Ream]

On Fri, Dec 6, 2019 at 1:03 PM Félix  wrote:

> In case some of you are curious about this project :
>
> I was stuck on a silly bug for more than a week while trying to implement
> complete outline tree editing and manipulation.
>
> I got unstuck last night. I'll try to finish outline editing along with
> keyboard shortcuts/keybindings for leo commands this weekend.
>
> ( I've been pushing to my dev branch instead of master for 2 months now -
> i'll try to make a new 'release' for you guys to try "soon" !! )
>
> Ah! the joys of programming! - Thanks for your patience and uplifting
> comments!
>

Yes.  You have to love it ;-)

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS3P0_KbPerD45CPHT1Pbv5VV8ToPFKoxjSnNtBOvRW85g%40mail.gmail.com.

leointeg status report

[Félix]

In case some of you are curious about this project : 

I was stuck on a silly bug for more than a week while trying to implement 
complete outline tree editing and manipulation.

I got unstuck last night. I'll try to finish outline editing along with 
keyboard shortcuts/keybindings for leo commands this weekend. 

( I've been pushing to my dev branch instead of master for 2 months now - 
i'll try to make a new 'release' for you guys to try "soon" !! )

Ah! the joys of programming! - Thanks for your patience and uplifting 
comments!
--
Félix 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/45f940d3-677f-4db3-a638-d691c4ccdf0f%40googlegroups.com.

Re: book authoring: formatting, auto-save, auto-commit to git

[Terrence-Monroe: Brannon]

I found a good answer to git auto-committing:
https://stackoverflow.com/questions/420143/making-git-auto-commit

On Friday, December 6, 2019 at 9:07:34 AM UTC-8, Terrence-Monroe: Brannon 
wrote:
>
> Regarding book authoring: 
>
> What formatting (rst, asciidoc) works well to make a book with Leo?
>
> If I want my work to be automatically auto-saved how can this be achieved? 
> Google docs automatically saves as I type (so does Evernote).
>
> If I want my work to be auto-committed to a git repo, how can this be 
> achieved?
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/844f885d-0f88-4b05-b666-d02367529dc8%40googlegroups.com.

Re: book authoring: formatting, auto-save, auto-commit to git

[Chris George]

Hello,

Formatting depends on the type of book.

For fiction, any of the popular markup languages will do it for you as few
fiction writers need much beyond bold and italic. Leo is well integrated
with rst and I taught myself to use it while I was learning Leo.

For non-fiction, the more sophisticated options might be required.
rst/Sphinx, asciidoc, or latex would all look after most use cases.

The autosave plugin can be modified for a short interval, although I tend
to live with 300 seconds.

I use a directory watch utility in linux and commit every saved .leo file
(which I keep in one folder and sync with Mega cloud storage) to a fossil
repository (also synced).

HTH,

Chris

On Fri, Dec 6, 2019 at 9:07 AM Terrence-Monroe: Brannon <
thequietcen...@gmail.com> wrote:

> Regarding book authoring:
>
> What formatting (rst, asciidoc) works well to make a book with Leo?
>
> If I want my work to be automatically auto-saved how can this be achieved?
> Google docs automatically saves as I type (so does Evernote).
>
> If I want my work to be auto-committed to a git repo, how can this be
> achieved?
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/d79d86b6-98b7-4fd9-8179-bdf6b4ae7e7a%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CADWQas1p2Rs55tNxLiaezHXeP1X4%2Byw_Nq%2BJFG72VaWOcEvyNw%40mail.gmail.com.

book authoring: formatting, auto-save, auto-commit to git

[Terrence-Monroe: Brannon]

Regarding book authoring: 

What formatting (rst, asciidoc) works well to make a book with Leo?

If I want my work to be automatically auto-saved how can this be achieved? 
Google docs automatically saves as I type (so does Evernote).

If I want my work to be auto-committed to a git repo, how can this be 
achieved?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/d79d86b6-98b7-4fd9-8179-bdf6b4ae7e7a%40googlegroups.com.

Re: Enhancing color scheme

[gar]

Brian,
ok, I'll try to implement it.
For now I really miss js/es6/es7 keywords and would love to learn jEdit
colorer to highlight them.
But first I want to run pygments colorer and understand how it works.
Edward made a great amount of work on it and it must work good, I just
failed to understand how to run it.

пт, 6 дек. 2019 г. в 18:37, Brian Theado :

> gar,
>
> Previously, you wrote this:
>
> > I find color schemes supplied with the leo's distr poor for some
> languages (for example,
> >javascript still knows nothing about es6/es7, and markdown ignores back
> quotes) and want to
> > enhance them (and even introduce some more).
>
> > How should I use changed version? I should edit files in the git repo
> and then make a pull request?
>
> It sounds like you are making improvements which would benefit everyone.
> IMO, for those cases it would make sense to edit the files in the git repo
> and make a pull request.
>
> Brian
>
>
> On Fri, Dec 6, 2019 at 2:56 AM gar  wrote:
>
>> Fantastic, thanks a lot! I am very poor pythonista and learnt something
>> new from your code.
>> It creates a new dialect from nothing, and that's cool.
>> But... how can I patch existing dialect? Acquire it, re-define methods of
>> interest and hope that it would work?
>>
>> четверг, 5 декабря 2019 г., 21:53:38 UTC+3 пользователь btheado написал:
>>>
>>> This thread may interest you: "Defining colorizer modes in @script"
>>> https://groups.google.com/d/msg/leo-editor/X9tjxbOq6es/lxyaIooWQzsJ.
>>>
>>> I never followed through on avoiding the need for the monkey patch. I
>>> don't use this code anymore and when I tested it didn't work. I made a
>>> small change (highlighted in bold below) and now it is working again. To
>>> test it yourself, "Paste as node" the following xml. Then highlight "sol
>>> colorizing" node and hit ctrl-b to execute it. Then select "colorizing
>>> test" node and see the highlighted date string
>>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/leo-editor/b047dd9a-5d9e-4ee0-87e6-65a198ddefc6%40googlegroups.com
>> 
>> .
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/CAO5X8Cze2ma3fj2vB%3D6AiQpP-%2Ba-P-uYO8dQDQ%3DefBvQg%2Bk75g%40mail.gmail.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVyLZaLP6YVZwvLq2wEWjH9_X3FxCuZ0UBP_m1YaTnhBQg%40mail.gmail.com.

Re: Enhancing color scheme

[Brian Theado]

gar,

Previously, you wrote this:

> I find color schemes supplied with the leo's distr poor for some
languages (for example,
>javascript still knows nothing about es6/es7, and markdown ignores back
quotes) and want to
> enhance them (and even introduce some more).

> How should I use changed version? I should edit files in the git repo and
then make a pull request?

It sounds like you are making improvements which would benefit everyone.
IMO, for those cases it would make sense to edit the files in the git repo
and make a pull request.

Brian


On Fri, Dec 6, 2019 at 2:56 AM gar  wrote:

> Fantastic, thanks a lot! I am very poor pythonista and learnt something
> new from your code.
> It creates a new dialect from nothing, and that's cool.
> But... how can I patch existing dialect? Acquire it, re-define methods of
> interest and hope that it would work?
>
> четверг, 5 декабря 2019 г., 21:53:38 UTC+3 пользователь btheado написал:
>>
>> This thread may interest you: "Defining colorizer modes in @script"
>> https://groups.google.com/d/msg/leo-editor/X9tjxbOq6es/lxyaIooWQzsJ.
>>
>> I never followed through on avoiding the need for the monkey patch. I
>> don't use this code anymore and when I tested it didn't work. I made a
>> small change (highlighted in bold below) and now it is working again. To
>> test it yourself, "Paste as node" the following xml. Then highlight "sol
>> colorizing" node and hit ctrl-b to execute it. Then select "colorizing
>> test" node and see the highlighted date string
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/b047dd9a-5d9e-4ee0-87e6-65a198ddefc6%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAO5X8Cze2ma3fj2vB%3D6AiQpP-%2Ba-P-uYO8dQDQ%3DefBvQg%2Bk75g%40mail.gmail.com.

Thomas Passin, does rev 028f4b (in devel) fix #1444 or #1445?

[Edward K. Ream]

Rev 028f4b attempts a fix for #1444 
 (many errors during 
startup) without really knowing what is going on. 

The traceback indicates that line 607 in leoCache.py may be to blame.

The old code catches only KeyError; the new code catches all Exceptions. 
The traceback references PyQt4, so perhaps there is some 
installation-dependent problem/strangeness.

I am wondering whether this fix might just fix #1445 as well. Clearly, 
something unusual is going on, because very few people seem to be affected 
by either bug.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/849a07f0-608c-48a6-938d-be8bfc1b880f%40googlegroups.com.

How to scroll the body/render window while keeping the cursor in the Outline window?

['Terrence Brannon' via leo-editor]

Is it possible to maintain keyboard/mouse focus in the outline window yet 
issue a keyboard shortcut to scroll the current body/render window?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/3d10ab5f-da61-4645-be17-b20b34d699bd%40googlegroups.com.

Back with you :-)

[Edward K. Ream]

The fstrings project has reached a good stopping point:

- Completed a few loose ends in the code.
- Merged fstring branch into devel.
- Updated the Theory of Operation in LeoDocs.leo.

Reaching this stopping point means that I can fully shift my focus back to 
Leo.

My first priority is fixing the bugs assigned to Leo 6.1.1 
.
 
This might happen before I leave. If not, I'll be working on them on 
vacation. This is nothing new. Even on vacation I have always worked a few 
hours a day on Leo.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/0b0b3316-105b-4882-99bb-092562da954b%40googlegroups.com.