Why does leo asks to restart when a .leo file modification is detected? (instead of asking to reload the file?)

[Félix]

Exactly as per the subject line, I'm wondering why does Leo asks to restart 
when a .leo file modification is detected? Instead of asking to reload the 
file?

I feel like I asked this question in the past and I cant remember the 
reason, ...but I searched this google-group for 'restart' and I couldn't 
find anything... so i just posted this

Thanks for anyone who can enlighten me about this :)

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/45396e60-a3d7-44e1-b75f-76ce7ecb4bb0n%40googlegroups.com.

Re: Heads Up - My Workbook Is Getting Destroyed

[Edward K. Ream]

On Wed, Jun 28, 2023 at 3:15 PM Thomas Passin  wrote:

one defensive code change to make is for Leo never to replace the workbook
> - whether or not it can find it - without asking the user.  On first use,
> when the Leo user gets created, that wouldn't apply.


Good idea.

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/CAMF8tS3FAnKL1hX_bUMuyx9r%2B7G9ukUNFA3ukCHVsB2_3Bb%2BKQ%40mail.gmail.com.

Re: Heads Up - My Workbook Is Getting Destroyed

[Thomas Passin]

I agree, but with a non-reproducible report it's hard to make any 
progress.  In this case I wanted to be able to file a more definite issue, 
but also alert people as soon as possible to back up their workbooks until 
the thing gets resolved.  

I do think that one defensive code change to make is for Leo never to 
replace the workbook - whether or not it can find it - without asking the 
user.  On first use, when the Leo user gets created, that wouldn't apply.

On Wednesday, June 28, 2023 at 3:48:14 PM UTC-4 gates...@gmail.com wrote:

> I'd like to propose that *any* data corruption issue at all in Leo should 
> be reported, regardless of whether the steps to replicate are known.  The 
> last thing an editor should ever do is destroy data.
>
> Jake
>
> On Wed, Jun 28, 2023 at 1:49 PM Thomas Passin  wrote:
>
>>
>> On Wednesday, June 28, 2023 at 11:42:37 AM UTC-4 Edward K. Ream wrote:
>>
>> On Wed, Jun 28, 2023 at 10:27 AM Thomas Passin  wrote:
>>
>> I've done more testing, and the pattern is definitely repeatable.  If I 
>> check out the  ekr-3181-mypy-links branch, the first time I launch Leo 
>> the workbook may not be affected but every time after that it is destroyed 
>> and replaced by the default CheatSheet.  When I change back to the devel 
>> branch, the first launch after that also replaces the workbook, but after 
>> that the workbook is opened without replacement.  Remember, in these trials 
>> after each time the workbook gets replaced, I restore it from backup for 
>> the next launch.
>>
>> The replacement does not happen if I specify the workbook on the command 
>> line.  Clearing the recent files list had no effect on the behavior.  
>> Nether did deleting the .leo\db directory.
>>
>>
>> Thanks for this report.  Please file an issue, if you haven't done so. 
>> This issue will have high priority.
>>
>>
>> Done: #3404 
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/leo-editor/e337e8c2-ba2f-46c3-9780-0154dc9e5e9en%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/765c1c72-a22e-44e6-a0e4-3cdc35bd7b5en%40googlegroups.com.

Re: Heads Up - My Workbook Is Getting Destroyed

[Jacob Peck]

I'd like to propose that *any* data corruption issue at all in Leo should
be reported, regardless of whether the steps to replicate are known.  The
last thing an editor should ever do is destroy data.

Jake

On Wed, Jun 28, 2023 at 1:49 PM Thomas Passin  wrote:

>
> On Wednesday, June 28, 2023 at 11:42:37 AM UTC-4 Edward K. Ream wrote:
>
> On Wed, Jun 28, 2023 at 10:27 AM Thomas Passin  wrote:
>
> I've done more testing, and the pattern is definitely repeatable.  If I
> check out the  ekr-3181-mypy-links branch, the first time I launch Leo
> the workbook may not be affected but every time after that it is destroyed
> and replaced by the default CheatSheet.  When I change back to the devel
> branch, the first launch after that also replaces the workbook, but after
> that the workbook is opened without replacement.  Remember, in these trials
> after each time the workbook gets replaced, I restore it from backup for
> the next launch.
>
> The replacement does not happen if I specify the workbook on the command
> line.  Clearing the recent files list had no effect on the behavior.
> Nether did deleting the .leo\db directory.
>
>
> Thanks for this report.  Please file an issue, if you haven't done so.
> This issue will have high priority.
>
>
> Done: #3404 
>
> --
> 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/e337e8c2-ba2f-46c3-9780-0154dc9e5e9en%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/CAJ1i%2BSbJ20_Jsk0KheiybBpzifF5XCe-WGYFgWbJoofxHwPxXw%40mail.gmail.com.

Re: Heads Up - My Workbook Is Getting Destroyed

[Thomas Passin]

On Wednesday, June 28, 2023 at 11:42:37 AM UTC-4 Edward K. Ream wrote:

On Wed, Jun 28, 2023 at 10:27 AM Thomas Passin  wrote:

I've done more testing, and the pattern is definitely repeatable.  If I 
check out the  ekr-3181-mypy-links branch, the first time I launch Leo the 
workbook may not be affected but every time after that it is destroyed and 
replaced by the default CheatSheet.  When I change back to the devel 
branch, the first launch after that also replaces the workbook, but after 
that the workbook is opened without replacement.  Remember, in these trials 
after each time the workbook gets replaced, I restore it from backup for 
the next launch.

The replacement does not happen if I specify the workbook on the command 
line.  Clearing the recent files list had no effect on the behavior.  
Nether did deleting the .leo\db directory.


Thanks for this report.  Please file an issue, if you haven't done so. This 
issue will have high priority.


Done: #3404 

-- 
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/e337e8c2-ba2f-46c3-9780-0154dc9e5e9en%40googlegroups.com.

Re: Heads Up - My Workbook Is Getting Destroyed

[Thomas Passin]

On Wednesday, June 28, 2023 at 12:52:42 PM UTC-4 jkn wrote:

FWIW, I have a vague feeling that something like this happened to me a few 
months ago. It only occurred the once, and I am not 100% sure what 
happened, but it definitely involved the CheatSheet 'appearing'.

Only mentioning it because this would have been before the recent work.


I did too, but it didn't repeat and I couldn't find a way to induce it.

-- 
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/404dc8c2-ef21-4843-8a31-532df94c3b62n%40googlegroups.com.

Re: Heads Up - My Workbook Is Getting Destroyed

[jkn]

FWIW, I have a vague feeling that something like this happened to me a few 
months ago. It only occurred the once, and I am not 100% sure what 
happened, but it definitely involved the CheatSheet 'appearing'.

Only mentioning it because this would have been before the recent work.

J^n

On Wednesday, June 28, 2023 at 4:42:37 PM UTC+1 Edward K. Ream wrote:

> On Wed, Jun 28, 2023 at 10:27 AM Thomas Passin  wrote:
>
>> I've done more testing, and the pattern is definitely repeatable.  If I 
>> check out the  ekr-3181-mypy-links branch, the first time I launch Leo 
>> the workbook may not be affected but every time after that it is destroyed 
>> and replaced by the default CheatSheet.  When I change back to the devel 
>> branch, the first launch after that also replaces the workbook, but after 
>> that the workbook is opened without replacement.  Remember, in these trials 
>> after each time the workbook gets replaced, I restore it from backup for 
>> the next launch.
>>
>> The replacement does not happen if I specify the workbook on the command 
>> line.  Clearing the recent files list had no effect on the behavior.  
>> Nether did deleting the .leo\db directory.
>>
>
> Thanks for this report.  Please file an issue, if you haven't done so. 
> This issue will have high priority.
>
> 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/816faed6-426b-415b-976c-8988282e14edn%40googlegroups.com.

Re: New Ultra-fast replacement for pylint/flake8

[Edward K. Ream]

On Wednesday, June 28, 2023 at 9:17:50 AM UTC-5 tbp1...@gmail.com wrote:

> Ruff ...is 100 times or more faster 
because it is written in Rust.  

Wow. ruff does the flake8 tests instantly. Here is the output of a script 
that checks leo/core and leo/commands with a line length (given in 
pyproject.toml) of 120.

ruff leo/core
leo\core\leoCommands.py:601:23: E741 Ambiguous variable name: `l`
leo\core\leoFileCommands.py:2161:15: E741 Ambiguous variable name: `l`
leo\core\leoserver.py:5487:121: E501 Line too long (132 > 120 characters)
Found 3 errors.
ruff leo/commands

I'm not sure whether ruff is doing pylint checks.

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/5e8510bd-0905-43a0-8e8b-87d787090bdbn%40googlegroups.com.

Re: Heads Up - My Workbook Is Getting Destroyed

[Edward K. Ream]

On Wed, Jun 28, 2023 at 10:27 AM Thomas Passin  wrote:

> I've done more testing, and the pattern is definitely repeatable.  If I
> check out the  ekr-3181-mypy-links branch, the first time I launch Leo
> the workbook may not be affected but every time after that it is destroyed
> and replaced by the default CheatSheet.  When I change back to the devel
> branch, the first launch after that also replaces the workbook, but after
> that the workbook is opened without replacement.  Remember, in these trials
> after each time the workbook gets replaced, I restore it from backup for
> the next launch.
>
> The replacement does not happen if I specify the workbook on the command
> line.  Clearing the recent files list had no effect on the behavior.
> Nether did deleting the .leo\db directory.
>

Thanks for this report.  Please file an issue, if you haven't done so. This
issue will have high priority.

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/CAMF8tS36NgY7Sq7ZfQ3ba1EWpWHiBZ%2Bpn60c4fWxNn-USfBVLg%40mail.gmail.com.

Re: New Ultra-fast replacement for pylint/flake8

[Edward K. Ream]

On Wed, Jun 28, 2023 at 9:17 AM Thomas Passin  wrote:

> Ruff  is a new-ish linter program that
> does the job of pylint or flake8 but is 100 times or more faster because it
> is written in Rust.  It might be worth looking at for Leo.


Oh yeah!

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/CAMF8tS18wP577iQ0yg-7eNZPKs7Br%3DEK700J9uDdpt5zWs3orw%40mail.gmail.com.

Re: Heads Up - My Workbook Is Getting Destroyed

[Thomas Passin]

I've done more testing, and the pattern is definitely repeatable.  If I 
check out the  ekr-3181-mypy-links branch, the first time I launch Leo the 
workbook may not be affected but every time after that it is destroyed and 
replaced by the default CheatSheet.  When I change back to the devel 
branch, the first launch after that also replaces the workbook, but after 
that the workbook is opened without replacement.  Remember, in these trials 
after each time the workbook gets replaced, I restore it from backup for 
the next launch.

The replacement does not happen if I specify the workbook on the command 
line.  Clearing the recent files list had no effect on the behavior.  
Nether did deleting the .leo\db directory.

On Tuesday, June 27, 2023 at 5:55:37 PM UTC-4 Thomas Passin wrote:

> I haven't filed an issue on this yet because I haven't got all the 
> conditions nailed down.  But Leo has been replacing my workbook with the 
> default CheatSheet ... sometimes.  *Please* make sure you have a backup 
> copy until this gets resolved.
>
> I noticed this behavior while I was testing code with the branch 
>
> Leo 6.7.4-devel, ekr-3181-mypy-links branch, build b9a9205ae9
>
> This is the branch with with all the new unl code.  I'm not sure if it can 
> also occur on the devel branch.
>
> The problem is that this behavior seems to happen suddenly.  Once it 
> starts, every time I launch Leo with this command line, the workbook.leo 
> outline gets replaced:
>
> py -m leo.core.runLeo
>
> If I include the name of the outline the outline does not get replaced:
>
> py -m leo.core.runLeo .leo\workbook.leo
>
> When the outline gets replaced, I noticed that the other outlines that 
> were opened previously did not get opened.  This made me think that the 
> database was getting corrupted.  But I deleted the .leo\db directory and 
> the workbook still got deleted.
>
> I think that something the the experimental branch is corrupting some 
> string, maybe of the recent files list.  This prevents Leo from finding the 
> workbook.  So it creates a new one.  I have observed that changing back to 
> the devel branch does not stop this behavior on the first launch, but after 
> I run Leo once in devel and then restore the workbook from backup, after 
> that Leo behaves normally and does not replace the workbook.  When I switch 
> back to the experimental branch, that's when this problem starts happening 
> again.
>
> I suggest that if Leo cannot find the workbook when it wants to open it, 
> it should notify the user that it can't find it and ask if it should create 
> a default workbook.  The user will probably say "no!" since they will know 
> that they want to keep the existing one.
>
> Of course, the problem should be fixed, but this would prevent the loss of 
> the workbook in case of future bugs as well.  I don't know about you, but I 
> have a lot of work in my workbook that I really don't want to lose.
>
> I was saved by Leo's new automatic backup, so I had a workbook.leo.bak 
> file when I first realized realized the problem. (Yes, I do back up the 
> .leo directory, but not recently enough this time).
>

-- 
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/b9edd250-0a69-413c-b286-2254f0a1ed37n%40googlegroups.com.

New Ultra-fast replacement for pylint/flake8

[Thomas Passin]

Ruff  is a new-ish linter program that 
does the job of pylint or flake8 but is 100 times or more faster because it 
is written in Rust.  It might be worth looking at for Leo.  

Here's one of the testimonials:

Nick Schrock, founder of Elementl, co-creator of GraphQL:

Why is Ruff a gamechanger? Primarily because it is nearly 1000x faster. 
Literally. Not a typo. On our largest module (dagster itself, 250k LOC) 
pylint takes about 2.5 minutes, parallelized across 4 cores on my M1. 
Running ruff against our entire codebase takes .4 seconds.

It's pypi-installable so presumably usable without executing an external 
program.

-- 
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/01048dda-737f-45c8-9059-ea3700e0b5e0n%40googlegroups.com.

Re: Discuss: option for short file names in unls?

[Edward K. Ream]

On Tue, Jun 27, 2023 at 9:48 PM HaveF HaveF  wrote:

> I don't know the meaning of short url, is it just for easy look?
>

Yes. The new *@data unl-path-prefixes* setting resolves relative to
absolute paths. As a result, shorter (relative) paths are likely to be more
useful than long (absolute) paths.

But this is a preference :-)

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/CAMF8tS3T4EF10iK%2BnDs_95foFXStQOF1FMZ5P2R%2BjAQHkJZq4Q%40mail.gmail.com.

Re: how to get all the content of the body?

[Edward K. Ream]

On Wed, Jun 28, 2023 at 8:09 AM HaveF HaveF  wrote:

> Super useful function! It works! You save my day, Thomas!

Thanks, Thomas, for your help.

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/CAMF8tS3pHcpbV1zFg9houe3dDZ5qVxiZMmxzaLn1jObWcsMTmw%40mail.gmail.com.

Re: PR #3215 is ready for review

[Edward K. Ream]

On Wed, Jun 28, 2023 at 3:58 AM Edward K. Ream  wrote:

PR #3215  creates
> *optional* unls based on gnxs.
>

And now the PR is even more ready for review :-) Todays revs:

- Add two new helpers: *g.findAnyUnl* and *g.isValidUnl*.
- Using g.findAnyUnl in all plugins ensures that they support all forms of
unls.
- Use g.isValidUnl to simplify bc.handleURL. More work is likely needed.

I plan no further code changes except for bookmarks.py.

I'll continue testing for at least several more days.

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/CAMF8tS0ofdV7c4uGGLL%2BnA0vRPNaru7DyVc_VTH-47dvpB1H%2Bw%40mail.gmail.com.

Re: how to get all the content of the body?

[HaveF HaveF]

On Wed, Jun 28, 2023 at 8:26 PM Thomas Passin  wrote:

> I think you want the method g.getScript().  Look at its docstring in
> LeoPyRef.leo to see how to use it.

Super useful function! It works! You save my day, Thomas!
I finally don't have to use my crappy, buggy recursive expansion functions
that I wrote myself...



>
> BTW, here is how I found it.  I remembered that Leo scripts get run by
> writing a file called *ScriptFile.py*. So I searched for that using the
> Nav tab.  The first thing that came up was in *executeScriptHelper*, so I
> looked at that hit. Its parent is the command *execute-script*.  That
> seemed promising.  Looking in  *execute-script* , I noticed a line script
> = g.getScript(c, p or c.p, useSelectedText=useSelectedText).  So I
> searched for *getScript,* and that seems to be what you want.
>
> This is typically how I find relevant code in Leo's code base.  Others
> probably have their own ways, and mine is probably not the most "efficient"
> way to go about it.  The Nav tab makes it feasible and convenient. It's a
> brilliant feature.  The plugin's docstring says it was created by Ville M.
> Vainio, and I applaud him for it.
>
Thanks for your detailed way.
Maybe I need to take the time to get a general idea of what all these
functions are doing...


-- 
--
Sincerely,

HaveF

-- 
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/CA%2BUQrQytv-FSjkCehTVxyhR09jJPBpWzMN4gqymo1PV%2BF6fKpg%40mail.gmail.com.

Re: how to get all the content of the body?

[Thomas Passin]

I think you want the method g.getScript().  Look at its docstring in 
LeoPyRef.leo to see how to use it.

BTW, here is how I found it.  I remembered that Leo scripts get run by 
writing a file called *ScriptFile.py*. So I searched for that using the Nav 
tab.  The first thing that came up was in *executeScriptHelper*, so I 
looked at that hit. Its parent is the command *execute-script*.  That 
seemed promising.  Looking in  *execute-script* , I noticed a line script = 
g.getScript(c, p or c.p, useSelectedText=useSelectedText).  So I searched 
for *getScript,* and that seems to be what you want.

This is typically how I find relevant code in Leo's code base.  Others 
probably have their own ways, and mine is probably not the most "efficient" 
way to go about it.  The Nav tab makes it feasible and convenient. It's a 
brilliant feature.  The plugin's docstring says it was created by Ville M. 
Vainio, and I applaud him for it.
On Wednesday, June 28, 2023 at 1:29:23 AM UTC-4 iamap...@gmail.com wrote:

> Hi, Leo user,
>
> Who knows how to get all the contents of the body?
> What I want is to replace << xxx >> and @others in the body.
>
> I have created a simple function, but it has problems handling child nodes 
> or children of child nodes. I suspect there is a ready-made function, but I 
> can't find it anyway, can anyone tell me about it?
>
> Thanks!
>
> Best,
> HaveF
>

-- 
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/5167ebfd-2cb3-4ab3-b23e-c7bc98bd8d9an%40googlegroups.com.

Re: PR #3215 is ready for review

[Edward K. Ream]

On Wednesday, June 28, 2023 at 3:58:07 AM UTC-5 Edward K. Ream wrote:

> PR #3215  creates 
*optional* unls based on gnxs.

I'll wait at least a week before merging this PR. There is plenty of time 
for comments and corrections.

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/cb9c7412-d929-49ce-9471-c2c6f70115b6n%40googlegroups.com.

PR #3215 is ready for review

[Edward K. Ream]

PR #3215  creates 
*optional* unls based on gnxs.

I have been eating my own dog food for days without problems. 

Please test the *ekr-3181-mypy-links* branch and report any problems.

*Settings*

leoSettings.leo contains three new settings related to unls:

@string unl-status-kind = gnx  # use legacy for legacy unls.
@bool full-unl-paths = True
@data unl-path-prefixes 

This last setting eliminates hard-coded hacks. The setting gives the 
absolute paths (on your machine) to the files given in unls.

As usual, you should override these settings in 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/918e5e32-548e-44c5-b295-cf1326d81caen%40googlegroups.com.