I set myLeoSettings file to: @string unl-status-kind = legacy I then created a *new* leo file and created a new node: Test UNLs for Thomas - legacy
You are correct the new version UNLs don't have the full path to the file: unl://Test_UNLs.leo#Test UNLs for Thomas - legacy Ctrl-click on a node with that new version UNL does not open the file. Nor does it move to file if already open *Leo Log WindowLeo 6.7.6-devel, devel branch, build ec97534c2d2023-12-09 16:30:04 -0600Python 3.12.0, PyQt version 6.6.1Windows 10 AMD64 (build 10.0.19045) SP0* On Sunday, December 10, 2023 at 3:18:56 PM UTC+11 [email protected] wrote: > What version or changeset are you running? It's been broken for me in > devel for a while, and also in 6.7.5. I get UNLs from nodes, and they look > like this: > > unl:gnx://LeoPyRef.leo#ekr.20230630132340.1 (New style) > unl://workbook.leo#get unl body ("Legacy" style) > > Neither form works for me with a CTRL-click for a file outside the current > outline, because - > > The new version UNLs do not include the full path to a file, whereas your > example does. Without the full path, the navigation method has to try a > series of heuristics to work out the path, and that's what the current > method doesn't get right. I get the UNLs to test using p.get_UNL() or > p.get_legacy_UNL(). If your example UNL string came from an older > version of Leo, well, that's not what you would get with current versions. > On Saturday, December 9, 2023 at 9:33:13 PM UTC-5 lewis wrote: > >> Ctrl-click on UNL is not broken for me :) >> > -- 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 on the web visit https://groups.google.com/d/msgid/leo-editor/81fb47ca-da1b-4e7d-bff7-a5c9c256a4ban%40googlegroups.com.
