An update:
1) to partially confirm Thomas' earlier observation: I can edit a new-style
UNL to include the full path, and this it works.
Note that the form has to be slightly different under Linux (three forward
slashes ... I lose track of the 'scheme' etc. me4aning of the fields here)
unl:gnx:///home/jkn/Seafile/at_files/@leo/jknprojects.leo#jkn.20250729113758.1
# will open file even if not already open
2) I am trying to confirm this, since it seems to be different on different
machines; but on one, currently, if I edit the shortcut to *not* use
environment variables, it works:
# myLeoSettings.leo
@data unl-path-prefixes
jknprojects.leo: ${SEAFILE}/at-files/@leo # does not work,
but used to. SEAFILE=/home/jkn/Seafile
jknprojects.leo: /home/jkn/Seafile/at_files/@leo # seems to work on
at least one machine; I think it does not work on one machine, I am checking
FWIW I am next to certain that the use of '@' in my directory path is not
the issue, I have played with this...
J^n
On Tuesday, July 29, 2025 at 12:11:49 PM UTC+1 jkn wrote:
> No, I already only have the directories. I must have had to play with this
> part previously(and successfully),
> since I have my own explanatory comment in myLeoSettings.leo:
>
> # map short filenames to full paths -
> # may depend on the platform...
>
> #y.leo: <full path to the directory containing y.leo>
> #z.leo: <full path to the directory containing z.leo>
>
> # $(ENVIRONMENT_VARIABLE} seems to work here ;-)
>
> Note the comment about ${ENVIRONMENT_VARIABLE} - my entries use this for
> cross-platform working.
> However (as mentioned above) I tried re-writing the path without an
> environment variable, and still nothing.
> I am a bit surprised there is nothing in the log. FWIW I experimented with
> 'mangling' the filename in the unl:gnx link, and still got no error message
>
> I am running:
>
> Leo Log Window
> Leo 6.8.5-devel, devel branch, build dc00194614
> 2025-06-22 06:06:45 -0500
> Python 3.12.3, PyQt version 6.9.1
> linux
>
>
> On Monday, July 28, 2025 at 6:01:43 PM UTC+1 Edward K. Ream wrote:
>
>> On Thu, Jul 17, 2025 at 9:07 AM jkn <[email protected]> wrote:
>>
>> I had a link of the form
>>>
>>> unl:gnx://myfilename.leo#jkn.20240604101758.1
>>>
>>>
>>> (and an entry in @data unl-path-prefixes to point to the location of
>>> myfilename.leo)
>>>
>>>
>>> Ctrl-click successfully navigates to the location if myfilename.leo is
>>> already open, but not otherwise.
>>>
>>
>> Everything works for me as expected. The example in LeoDocs.leo is a bit
>> misleading. The body of @data unl-path-prefixes says:
>>
>> # lines have the form:
>> # x.leo: <absolute path to x.leo>
>>
>> # test.leo: c:/Repos/leo-editor/leo/test
>> # LeoDocs.leo: c:/Repos/leo-editor/leo/doc
>>
>> But the example shows that the lines should be paths to the *directory*
>> containing
>> your .leo file. Does that 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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/leo-editor/ce3385e0-a71b-41d5-a949-5e8e35d032b4n%40googlegroups.com.
