Re: Help with script.

[Chris George]

The @button saved the .leo file, triggering the save of the text file as 
well. Fossil picked up both changes.

Is it possible to write the @clean node to disk without saving the .leo 
file? That would let me give unique commit messages for each @clean file 
and also for the .leo file at the end of the session.

Chris
>
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Help with script.

[Chris George]

To be clear, I switched to fossil a day or two ago from git, so there may 
well be things I don't quite get about it yet.

Chris

On Saturday, February 10, 2018 at 6:30:39 PM UTC-8, Edward K. Ream wrote:
>
> On Sat, Feb 10, 2018 at 3:09 PM, Chris George  > wrote:
>
> I use Leo to write my weekly column using @clean nodes created using an 
>> abbreviation. 
>>
>  
>
>> [I want an @button script to do the following]:
>>
>> 1) Save the @clean file to disk.
>>
>
> ​c.save() will do this.
> ​
>  
>
>> 2) Run a system command in the folder specified in the @clean file path: 
>>
> ​​
>> ​​
>> ​​
>> fossil commit -m "".
>>
>
> ​See below.
>  
>
>> 3) Clear a child node of the commit message to prepare for next time.
>>
>
> ​See below.​
>
>
> The child node with the commit message shouldn't be written to the @clean 
>> file.
>>
>
> ​I would put the commit message in a "standard place" known to the @button 
> script.  Your script can find this node using:
>
> p = g.findNodeAnywhere(c, "fossil commit message")
>
> Putting this all together we get:
>
> if c.isChanged():
> c.save()
> p = g.findNodeAnywhere(c, "commit node") 
> message = p.b.replace('"', "'")
> command = 
> ​'fossil commit -m "%s"' % message
>
> c.controlCommands.executeSubprocess(
> event=None,
> command=command,
> )
>
> In my prototype, the command was "ls" and all output went to Leo's log 
> pane and the console.
>
> Give it a whirl.  Please report your experiences.
>
> 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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Help with script.

[Chris George]

It worked great.

Interestingly, firing the commit found ALL the changes in the entire 
repository, including the Leo files, irrespective of file path.

So I dug a bit more.

Adding the commit to the end of the batch file I use to run Leo also picks 
up ALL changes from ALL folders and commits them and kicks a prompt for a 
commit message.

So no matter where I try to do the commit, I only get one message for all 
of the changes. And there can be quite a lot of them in one session.

Chris

On Saturday, February 10, 2018 at 6:39:25 PM UTC-8, Terry Brown wrote:
>
> I think the key issue is getting the command to execute with the right 
> current directory. I wonder, would c.selectPosition() on the @file node do 
> that? I have a script fragment (not on my phone :) I use for that, but it 
> always seems it should just be p.cd_for_node() or something, and that 
> should consider all relevant @file and @path ancestor nodes. 
> p.cd_for_node() returning a string.
>
> Cheers - Terry 
>
> On February 10, 2018 8:30:37 PM CST, "Edward K. Ream"  > wrote:
>>
>> On Sat, Feb 10, 2018 at 3:09 PM, Chris George > > wrote:
>>
>> I use Leo to write my weekly column using @clean nodes created using an 
>>> abbreviation. 
>>>
>>  
>>
>>> [I want an @button script to do the following]:
>>>
>>> 1) Save the @clean file to disk.
>>>
>>
>> ​c.save() will do this.
>> ​
>>  
>>
>>> 2) Run a system command in the folder specified in the @clean file path: 
>>>
>> ​​
>>> ​​
>>> ​​
>>> fossil commit -m "".
>>>
>>
>> ​See below.
>>  
>>
>>> 3) Clear a child node of the commit message to prepare for next time.
>>>
>>
>> ​See below.​
>>
>>
>> The child node with the commit message shouldn't be written to the @clean 
>>> file.
>>>
>>
>> ​I would put the commit message in a "standard place" known to the 
>> @button script.  Your script can find this node using:
>>
>> p = g.findNodeAnywhere(c, "fossil commit message")
>>
>> Putting this all together we get:
>>
>> if c.isChanged():
>> c.save()
>> p = g.findNodeAnywhere(c, "commit node") 
>> message = p.b.replace('"', "'")
>> command = 
>> ​'fossil commit -m "%s"' % message
>>
>> c.controlCommands.executeSubprocess(
>> event=None,
>> command=command,
>> )
>>
>> In my prototype, the command was "ls" and all output went to Leo's log 
>> pane and the console.
>>
>> Give it a whirl.  Please report your experiences.
>>
>> Edward 
>>
>>
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Help with script.

[Terry Brown]

I think the key issue is getting the command to execute with the right current 
directory. I wonder, would c.selectPosition() on the @file node do that? I have 
a script fragment (not on my phone :) I use for that, but it always seems it 
should just be p.cd_for_node() or something, and that should consider all 
relevant @file and @path ancestor nodes. p.cd_for_node() returning a string.

Cheers - Terry 

On February 10, 2018 8:30:37 PM CST, "Edward K. Ream"  
wrote:
>On Sat, Feb 10, 2018 at 3:09 PM, Chris George 
>wrote:
>
>I use Leo to write my weekly column using @clean nodes created using an
>> abbreviation.
>>
>
>
>> [I want an @button script to do the following]:
>>
>> 1) Save the @clean file to disk.
>>
>
>​c.save() will do this.
>​
>
>
>> 2) Run a system command in the folder specified in the @clean file
>path:
>>
>​​
>> ​​
>> ​​
>> fossil commit -m "".
>>
>
>​See below.
>
>
>> 3) Clear a child node of the commit message to prepare for next time.
>>
>
>​See below.​
>
>
>The child node with the commit message shouldn't be written to the
>@clean
>> file.
>>
>
>​I would put the commit message in a "standard place" known to the
>@button
>script.  Your script can find this node using:
>
>p = g.findNodeAnywhere(c, "fossil commit message")
>
>Putting this all together we get:
>
>if c.isChanged():
>c.save()
>p = g.findNodeAnywhere(c, "commit node")
>message = p.b.replace('"', "'")
>command =
>​'fossil commit -m "%s"' % message
>
>c.controlCommands.executeSubprocess(
>event=None,
>command=command,
>)
>
>In my prototype, the command was "ls" and all output went to Leo's log
>pane
>and the console.
>
>Give it a whirl.  Please report your experiences.
>
>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 post to this group, send email to leo-editor@googlegroups.com.
>Visit this group at https://groups.google.com/group/leo-editor.
>For more options, visit https://groups.google.com/d/optout.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Help with script.

[Edward K. Ream]

On Sat, Feb 10, 2018 at 3:09 PM, Chris George  wrote:

I use Leo to write my weekly column using @clean nodes created using an
> abbreviation.
>


> [I want an @button script to do the following]:
>
> 1) Save the @clean file to disk.
>

​c.save() will do this.
​


> 2) Run a system command in the folder specified in the @clean file path:
>
​​
> ​​
> ​​
> fossil commit -m "".
>

​See below.


> 3) Clear a child node of the commit message to prepare for next time.
>

​See below.​


The child node with the commit message shouldn't be written to the @clean
> file.
>

​I would put the commit message in a "standard place" known to the @button
script.  Your script can find this node using:

p = g.findNodeAnywhere(c, "fossil commit message")

Putting this all together we get:

if c.isChanged():
c.save()
p = g.findNodeAnywhere(c, "commit node")
message = p.b.replace('"', "'")
command =
​'fossil commit -m "%s"' % message

c.controlCommands.executeSubprocess(
event=None,
command=command,
)

In my prototype, the command was "ls" and all output went to Leo's log pane
and the console.

Give it a whirl.  Please report your experiences.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Help with script.

[Chris George]

I started by looking at run_nodes.py but couldn't make it work for me.

What I am trying to do is automate versioning in my writing repository 
using fossil.

I use Leo to write my weekly column using @clean nodes created using an 
abbreviation. What I would like to be able to do is to click a button to do 
a couple of things:

1) Save the @clean file to disk.
2) Run a system command in the folder specified in the @clean file path: 
fossil commit -m "".
3) Clear a child node of the commit message to prepare for next time.


The child node with the commit message shouldn't be written to the @clean 
file.

I am used to doing this manually, but now I am writing for another 
publication on a monthly basis. And I naturally keep forgetting to run 
commits in the various and sundry folders where my new files land after 
making changes as I have to do it outside Leo (and outside of my 
work'writing flow).


Can anyone point me in the right direction?


Chris


-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Leo 5.7b2 coming this week

[Edward K. Ream]

I expect to release Leo 5.7b2 in a day or two, or by Friday, February 16 at 
the very latest.

The master branch is still open, but please hold all but essential commits.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: @file repo for leo4sqlite

[Edward K. Ream]

On Sat, Feb 10, 2018 at 12:46 PM, tscv11  wrote:

> I've created a new repository for the @file version of leo4sqlite because
> I prefer it to @auto when developing (so far).
>
> https://github.com/tscv11/leo4sqlite-file
>

​Thanks for this work.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: ENB: Completing the default spell checker

[Edward K. Ream]

On Saturday, February 10, 2018 at 5:03:54 AM UTC-6, Edward K. Ream wrote:

> What, and when, to tell the user when the main spelling dict does not 
exit? 

Rev 0d17787 shows the Spell Tab only if a main dict exists in 
~/.leo/main_spelling_dict.txt. The main dict always exists (in a different 
location) when pyenchant has been installed. 

The show-spell-info command works even if the main dict does not exist.  In 
that case, the command explains in detail why there is no Spell Tab.  Imo, 
this is more than a good enough solution.

*To do*

- Document the new behavior in the release notes.

- Add a FAQ entry about the default spell checker. It will mention @string 
main_spelling_dictionary.

- Add an *empty *@string main_spelling_dictionary.to leoSettings.leo.  It's 
pointless to give a default.

- Improve the main dict before 5.7 final. This project will not delay 5.7b2.

*Summary*

Leo now works much like Leo 5.6 when ~/.leo/main_spelling_dict.txt does not 
exist. This is plenty good enough even for 5.7 final.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

@file repo for leo4sqlite

[tscv11]

I've created a new repository for the @file version of leo4sqlite because I 
prefer it to @auto when developing (so far).

https://github.com/tscv11/leo4sqlite-file

tscv11

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rev 713d565ba: c.backup_helper

[Edward K. Ream]

On Saturday, February 10, 2018 at 10:50:29 AM UTC-6, Edward K. Ream wrote:

The signature of c.backup_helper is:
>
> def backup_helper(self, base_dir=None, env_key='LEO_BACKUP', sub_dir=None
> ):
>
> c.backup_helper uses the LEO_BACKUP environment variable as the base of 
> the save if it exists.  Otherwise it uses the given base_dir directory. 
>

I forgot to mention that this method saves to the base_dir/sub_dir 
directory if sub_dir is given.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Rev 713d565ba: c.backup_helper

[Edward K. Ream]

The signature of c.backup_helper is:

def backup_helper(self, base_dir=None, env_key='LEO_BACKUP', sub_dir=None):

c.backup_helper uses the LEO_BACKUP environment variable as the base of the 
save if it exists.  Otherwise it uses the given base_dir directory.  It 
does careful error checking and reporting. The body text of the following 
four @button backup nodes are all just one line:

c.backup_helper(sub_dir='leoPy') # In leoPy.leo
c.backup_helper(sub_dir='leoPlugins') # In leoPlugins.leo
c.backup_helper(sub_dir='ekr-projects') # In ekr-projects.leo
c.backup_helper(sub_dir='ekr') # In ekr.leo

Yes, these scripts are simpler, and safer than before. More importantly 
changing LEO_BACKUP value will redirect all of them.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Electron, not for web apps.?

[vitalije]

Also, for building clojurescript version one must have installed java and 
leiningen. Command for building development version is (IIRC)
lein figwheel

For the coffeescript version one must have installed node version 8 + and 
yarn package manager. Command for installing dependencies is
yarn

 And then for starting development version:
yarn dev

Both projects contain a reference Leo file. You should copy 
leo-el-vue-ref.leo to leo-el-vue.leo. Demo application expects to find 
leo-el-vue.leo in root project folder. It will automatically open that Leo 
file and display it. 

Vitalije

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Electron, not for web apps.?

[vitalije]

>
>
> Leo in Clojurescript:
> https://repo.computingart.net/leocljs/vinfo?name=284258273ec5c6a5
>
> Leo in Coffeescript:
> https://leoelvue.computingart.net//vinfo?name=961ffef69d171c52
>
> Edward
>

The other alternative would be to use fossil executable. It is a single 
file, just put it in PATH. Fossil for Linux, Windows and Mac are here 
.

With fossil in the path type the following command in shell:
fossil clone https://leoelvue.computingart.net/ leoelvue.fossil

fossil clone https://repo.computingart.net/leocljs/ leocljs.fossil

These command each, will make single repository file. Then you enter an 
empty folder and run:

fossil open 

and you would have all files in their latest version.

Vitalije

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Electron, not for web apps.?

[Edward K. Ream]

On Sat, Feb 10, 2018 at 6:26 AM, vitalije  wrote:

> Here are two versions:
>
>- Leo in ClojureScript  (using
>Electron, and Om/React)
>- Leo in CoffeScript  (using
>Electron, Vue)
>
> ​To download the files, click one of the links above, then click the
"files" link, and then click on the link:

"Files of check-in [hash]"

at the top of the page.  That will take you to a page that gives you the
option of downloading a .zip file or a tarball.

The actual download pages are:

Leo in Clojurescript:
https://repo.computingart.net/leocljs/vinfo?name=284258273ec5c6a5

Leo in Coffeescript:
https://leoelvue.computingart.net//vinfo?name=961ffef69d171c52

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Electron, not for web apps.?

[Edward K. Ream]

On Sat, Feb 10, 2018 at 6:26 AM, vitalije  wrote:

​>> ​
Of course it is of interest! It would also give a boost to #574: Create
clojurescript importer 
​.
​​

> Here are two versions:
>
>- Leo in ClojureScript  (using
>Electron, and Om/React)
>- Leo in CoffeScript  (using
>Electron, Vue)
>
> ​Many thanks for these.  I'll look at them today.

I find that most difficult part is publishing and sharing project
> experiments.
>

​Have you tried pushing to
​​ 
​Leo's snippets repo ? ​
​ You, and anyone else, is also welcome to add to leo/scripts/scripts.leo.​

​> ​
PS: It seems that I am going to be very occupied with other duties in the
following few months and I don't know when I will be able to continue
development on the Leo-Electron-Vue. It is totally different story than
what Terry and Edward are doing on implementing Web front for python Leo
back-end, but it may happen that these two stories find something in common
and share some development. After all, Leo users may wish all kinds of Leo
apps.

​Exploring the contrast between the two approaches will be valuable,
regardless of what we end up doing. And it's time I learned clojurescript
and its way of thinking.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Electron, not for web apps.?

[vitalije]

Looking in the timelines of both projects, I am surprised how little time 
it took to develop both implementations (5 days for the first and 3 days 
for the second). However, publishing those two projects took two days.

Vitalije

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Electron, not for web apps.?

[vitalije]

>
>
> ​Of course it is of interest! It would also give a boost to #574: Create 
> clojurescript importer 
> ​.
>
> Edward
>

Here are two versions:

   - Leo in ClojureScript  (using 
   Electron, and Om/React)
   - Leo in CoffeScript  (using 
   Electron, Vue)


I am sorry for the delay. I find that most difficult part is publishing and 
sharing project experiments. It took me day or two to publish two 
experimental projects. First one is the one I wrote about in previous post. 
It is implementation of Leo as desktop application using Electron and 
written in clojurescript. I haven't test it lately, and it may be dated 
because all the libraries used are in high pace development. I hope it is 
still possible to build without errors.

Inspired by LeoVue, I was thinking about replacing Om/React with Vue. 
Finally I have restarted the whole experiment using new set of libraries 
and using CoffeeScript instead of ClojureScript.

HTH Vitalije

PS: It seems that I am going to be very occupied with other duties in the 
following few months and I don't know when I will be able to continue 
development on the Leo-Electron-Vue. It is totally different story than 
what Terry and Edward are doing on implementing Web front for python Leo 
back-end, but it may happen that these two stories find something in common 
and share some development. After all, Leo users may wish all kinds of Leo 
apps.

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

ENB: Completing the default spell checker

[Edward K. Ream]

Several tricky issues remain.  I am also fixing some bugs as I write ;-)  
This will be pre-writing for documentation for the default spell checker.

*User interface*

What, and when, to tell the user when the main spelling dict does not exit? 
Imo, the spell checker should not pollute the startup log warnings, nor 
would users notice such warnings.  Otoh, silently ignoring the absence of 
the main spelling dict means that users will take awhile to notice that the 
spell checker doesn't know any words!

There at least two possibilities:

1. Disable the default spell checker if the main spelling dict can not be 
found.  This is kinda a return to the status quo ante, except that the user 
only needs to install the main spelling dict to have a fully functional 
spell checker.

2. Warn the user that the main spelling dict can not be found just the 
first time the user clicks the "spell" button.  This is more informative, 
but the spell checker is still essentially useless.



The default check looks for the main spelling dict in one of two places:

- The path specified by @string main_spelling_dictionary
- In ~/.leo/main_spelling_dict.txt

Note that this issue does not exist for the pyenchant checker because the 
pyenchant module knows where its main dictionary is without being told.

Neither spell checker ever creates this file automatically, nor should 
they.  



*A better main dictionary*

When I awoke this morning I saw that bugs might prevent some words that are 
actually in the main dictionary from being recognized.  I'll double check 
the code today.

However, I strongly suspect that the hunspell dict that has been uploaded 
to SourceForge is inadequate.  That's not terribly surprising.  I generated 
the .txt file from a script.  Heh.  Not sure where just now.

But when I awoke I also saw that it might be possible to generate a default 
main dict (a text file) from pyenchant's main dict!  This file is 
compressed in the pyenchant folder, but it may be possible to iterate 
through all its contents using pyenchant's api. We shall see. If so, this 
would resolve #711: Create bigger default spelling dicts. 


*Distribution*

The default dict on SourceForge is a plain text file.  It should be 
compressed using a *standard *compression scheme, not some shell script as 
is apparently needed when using hunspell compressed folders.  The 
documentation will then have to explain how to unpack the file and where to 
put the result.

*Summary*

I closed #700  a bit 
prematurely.  Considerable work remains before the default spell checker is 
ready for prime time.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: mark/unmark-first-parents

[Edward K. Ream]

On Sat, Feb 10, 2018 at 4:23 AM, Edward K. Ream  wrote:

This is on the list of things before Leo 5.7b2.
>

​I've just created #714
 for this, with a
milestone of 5.7. This will ensure it remains on my radar for 5.7b2, coming
in a day or three.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: mark/unmark-first-parents

[Edward K. Ream]

On Sun, Feb 4, 2018 at 4:46 PM, tscv11  wrote:

> After consulting Edward and Terry, the finished (I think)
> 'unmark-first-parents' command now works as intended.
>

​Excellent.  Thanks for this work.  This is on the list of things before
Leo 5.7b2.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.