How To Add Your Own Top-Level Menu To Leo's Menu Bar

[tbp1...@gmail.com]

I had some commands that I use often, and I didn't want to add buttons for 
them because some of the outlines I work with have too many buttons 
already.  It turns out that it's easy to add your own menus.  Maybe this is 
already documented somewhere, but anyway here is the way.

1. Copy the entire *@menus* tree from LeoSettings.leo to myLeoSettings.leo.
2. After the last @menu node, add a new *@menu *node with the name you 
want.  I call mine *Local*.
3. Add a new *@item* node under your *@menu* node with a command you want 
to invoke. You  can insert a "&" if you want to designate an accelerator 
key.  Use the other *@menu* and *@item* nodes as a guide.
4. Restart Leo.  Your new menu will appear after the standard menus in the 
menu bar.

You don't really have to put it at the end;  the new menu can go anywhere 
in the tree you like.  I just think it's better to keep the order of the 
main menus as close as possible to Leo's standard arrangement.

The commands referred to in 3) are minibuffer commands.  Example: 
*z-open-freewin*.

-- 
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/1e74625a-a4a7-4ca0-812c-4da7f56a4801n%40googlegroups.com.

Re: #2220 fixed in devel and 6.4 branches. Pls test!!!

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 24. September 2021 um 13:46:52 UTC+2:

> I have just pushed the fix for #2220 
>  to the devel and 
> 6.4 branches. See PR # 
> .
>
> * The fixes were non-trivial. Please test the 6.4 today!!!* 
>
> In keeping with the new era in unit testing, I did most of the work in 
> devel using a strong new unit test. I then carefully merged the changed 
> code into the 6.4 branch, ran all the unit tests in unitTest.leo and did 
> some more hand tests.
>
> It's unpleasant to make such major changes just before 6.4, but i see no 
> good alternative. The new code is *much* better than the old. Not only 
> does the new code fix the reported problem, but for the first time (ever? 
> in years?) undo works in headlines. It's amazing that these bugs have been 
> around so long!
>
> *Summary*
>
> The 6.4 branch contains fixes to several *serious* bugs involving 
> headlines. I see no alternative but to include these fixes in the 6.4 
> release.
>
> Please test the 6.4 branch today.  Leo 6.4 is going out the door 
> tomorrow!!!
>

Works for me on both 'master' & 'devel' branch using a Fedora 33 VM on 
Qubes OS.

With kind regards,

Viktor

-- 
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/2b94b4d0-704a-4893-a7e1-aefb3afddaddn%40googlegroups.com.

Re: Import data structure for inspection

[tbp1...@gmail.com]

I'm not sure about your data, but if it can be exported as an indented 
list, then you can import it into Leo as a "Tabbed File".  This will turn 
every line in the indented file into a new node whose headline is the text 
on that line.  The nodes will be indented to match your exported data.

By "indented list", I mean a file that looks like this:

item 1
item 1a
item 1b
item 1b1
item 1b1a
item 1b2
item 1c
item 2

Also, I have written a set of Leo scripts that will take a node with such a 
list and turn it in to an SVG mind map to a maximum depth of two, if that 
would be of interest.
On Friday, September 24, 2021 at 9:15:47 AM UTC-4 Phil wrote:

> I would like to use Leo as a tool to inspect structured data from another 
> application. In my particular case, I have a large tree data structure 
> (perfect for Leo!), and it is possible to script the application to dump 
> the data to a file, formatted as I desire - an ASCII representation would 
> seem most sensible. I'd like to dump it into whatever format would be easy 
> to import into Leo. I certainly can roll my own on this, but I'm wondering 
> if there is a best approach for this, maybe even a "Leo standard" way.
>
> Thanks!
> Phil
>

-- 
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/1ffc101d-bc3a-4f12-993f-b85ad118d5a3n%40googlegroups.com.

Import data structure for inspection

[Phil]

I would like to use Leo as a tool to inspect structured data from another 
application. In my particular case, I have a large tree data structure 
(perfect for Leo!), and it is possible to script the application to dump 
the data to a file, formatted as I desire - an ASCII representation would 
seem most sensible. I'd like to dump it into whatever format would be easy 
to import into Leo. I certainly can roll my own on this, but I'm wondering 
if there is a best approach for this, maybe even a "Leo standard" way.

Thanks!
Phil

-- 
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/27343711-cd2f-424f-b5b9-20e148381b28n%40googlegroups.com.

Re: #2220 fixed in devel and 6.4 branches. Pls test!!!

[Edward K. Ream]

On Fri, Sep 24, 2021 at 7:54 AM tbp1...@gmail.com 
wrote:

> Quick test with [6.4] confirms the previous bug and the new fix.


Thanks for testing!

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/CAMF8tS3XYNh6V_mNrgUjuNd6rdd09RZd2-aUZQwV%2BAgTi0iK0Q%40mail.gmail.com.

Re: #2220 fixed in devel and 6.4 branches. Pls test!!!

[tbp1...@gmail.com]

Oops, I meant the 6.4 branch, of course.

On Friday, September 24, 2021 at 8:54:42 AM UTC-4 tbp1...@gmail.com wrote:

> Quick test with devel confirms the previous bug and the new fix.
>
> Leo 6.4, 6.4 branch, build 77c88ae1fe
> 2021-09-24 06:21:55 -0500
>
>
> On Friday, September 24, 2021 at 7:46:52 AM UTC-4 Edward K. Ream wrote:
>
>> I have just pushed the fix for #2220 
>>  to the devel and 
>> 6.4 branches. See PR # 
>> .
>>
>> * The fixes were non-trivial. Please test the 6.4 today!!!* 
>>
>> In keeping with the new era in unit testing, I did most of the work in 
>> devel using a strong new unit test. I then carefully merged the changed 
>> code into the 6.4 branch, ran all the unit tests in unitTest.leo and did 
>> some more hand tests.
>>
>> It's unpleasant to make such major changes just before 6.4, but i see no 
>> good alternative. The new code is *much* better than the old. Not only 
>> does the new code fix the reported problem, but for the first time (ever? 
>> in years?) undo works in headlines. It's amazing that these bugs have been 
>> around so long!
>>
>> *Summary*
>>
>> The 6.4 branch contains fixes to several *serious* bugs involving 
>> headlines. I see no alternative but to include these fixes in the 6.4 
>> release.
>>
>> Please test the 6.4 branch today.  Leo 6.4 is going out the door 
>> tomorrow!!!
>>
>> Many thanks to SegundoBob for reporting #2220.
>>
>> 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/9c152ee8-f1b6-4bca-94e0-7212cb548489n%40googlegroups.com.

Re: #2220 fixed in devel and 6.4 branches. Pls test!!!

[tbp1...@gmail.com]

Quick test with devel confirms the previous bug and the new fix.

Leo 6.4, 6.4 branch, build 77c88ae1fe
2021-09-24 06:21:55 -0500


On Friday, September 24, 2021 at 7:46:52 AM UTC-4 Edward K. Ream wrote:

> I have just pushed the fix for #2220 
>  to the devel and 
> 6.4 branches. See PR # 
> .
>
> * The fixes were non-trivial. Please test the 6.4 today!!!* 
>
> In keeping with the new era in unit testing, I did most of the work in 
> devel using a strong new unit test. I then carefully merged the changed 
> code into the 6.4 branch, ran all the unit tests in unitTest.leo and did 
> some more hand tests.
>
> It's unpleasant to make such major changes just before 6.4, but i see no 
> good alternative. The new code is *much* better than the old. Not only 
> does the new code fix the reported problem, but for the first time (ever? 
> in years?) undo works in headlines. It's amazing that these bugs have been 
> around so long!
>
> *Summary*
>
> The 6.4 branch contains fixes to several *serious* bugs involving 
> headlines. I see no alternative but to include these fixes in the 6.4 
> release.
>
> Please test the 6.4 branch today.  Leo 6.4 is going out the door 
> tomorrow!!!
>
> Many thanks to SegundoBob for reporting #2220.
>
> 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/7e8cc7bf-c5ea-4ad6-b8d4-04b71e04b5f1n%40googlegroups.com.

I have just deleted 6.4 releases on GitHub and pypi

[Edward K. Ream]

Imo, deleting the "published" versions of 6.4 should be safe enough and 
will reduce confusion in the long run. These deleted versions were not 
widely publicized.

I'll create a new 6.4 on GitHub late this afternoon, after we have all had 
at least some chance to test the code.

I'll create a new 6.4 on pypi tomorrow.

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/384b73fc-1ca8-4ead-8667-2443ee984946n%40googlegroups.com.

#2220 fixed in devel and 6.4 branches. Pls test!!!

[Edward K. Ream]

I have just pushed the fix for #2220 
 to the devel and 6.4 
branches. See PR # .

* The fixes were non-trivial. Please test the 6.4 today!!!* 

In keeping with the new era in unit testing, I did most of the work in 
devel using a strong new unit test. I then carefully merged the changed 
code into the 6.4 branch, ran all the unit tests in unitTest.leo and did 
some more hand tests.

It's unpleasant to make such major changes just before 6.4, but i see no 
good alternative. The new code is *much* better than the old. Not only does 
the new code fix the reported problem, but for the first time (ever? in 
years?) undo works in headlines. It's amazing that these bugs have been 
around so long!

*Summary*

The 6.4 branch contains fixes to several *serious* bugs involving 
headlines. I see no alternative but to include these fixes in the 6.4 
release.

Please test the 6.4 branch today.  Leo 6.4 is going out the door 
tomorrow!!!

Many thanks to SegundoBob for reporting #2220.

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/01a1b4b0-c60d-4856-a197-1217e89e0dbdn%40googlegroups.com.

Re: The first public release will be 6.4.1

[Edward K. Ream]

On Thu, Sep 23, 2021 at 6:26 PM Edward K. Ream  wrote:

> #2220  is a
> serious, last-minute, bug, arising from a botched one-line fix, per PR
> #2172 .
>
> Rather than trying to patch 6.4 I'll release 6.4.1.
>

Belay that. I am going to delete the 6.4 release on GitHub and create a new
6.4 release later today. Deleting a release turns out to be easy.

Imo, there is no reason to keep the previous 6.4 release. It hasn't been
widely announced. Creating a 6.4.1 release would complicate matters
unnecessarily.

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/CAMF8tS0YZnG2_qougLVV-SSRDzQFDaQudY_RWiCRS9c6Ao%3DO%3Dw%40mail.gmail.com.