Re: About PR #3215: unbreakable unls!

On Sunday, June 25, 2023 at 10:36:32 PM UTC-4 Edward K. Ream wrote: On Sun, Jun 25, 2023 at 4:48 PM Thomas Passin wrote: So now my bookmarks manager will not work, something I use every day and depend on. I suppose I will have to pull out code from the attic and put it into my own module.

Re: About PR #3215: unbreakable unls!

On Sun, Jun 25, 2023 at 4:48 PM Thomas Passin wrote: I'm unclear as to whether the gnx string for a given node - that is, p.gnx > - will now be in a different format. p.gnx can never ever change. But p.get_GNX() now returns f"unl:gnx:{self.gnx}". Yes, this is confusing, but it shouldn't

Re: About PR #3215: unbreakable unls!

On Sun, Jun 25, 2023 at 4:48 PM Thomas Passin wrote: > So now my bookmarks manager will not work, something I use every day and > depend on. I suppose I will have to pull out code from the attic and put > it into my own module. Or recreate the pathlike part of the functionality, > anyway.

Re: About PR #3215: unbreakable unls!

So now my bookmarks manager will not work, something I use every day and depend on. I suppose I will have to pull out code from the attic and put it into my own module. Or recreate the pathlike part of the functionality, anyway. I'm unclear as to whether the gnx string for a given node -

Re: About PR #3215: unbreakable unls!

On Sun, Jun 25, 2023 at 1:44 PM Robert-Felix wrote: > Thanks for this simplification! supporting Leo's unl links is on my todo > list for leojs (and leointeg!) > You're welcome. I'm glad you like the new scheme. I think you'll like the simpler code. Edward -- You received this message

Re: About PR #3215: unbreakable unls!

On Sun, Jun 25, 2023 at 11:49 AM Thomas Passin wrote: > I would rather have created a new gnx:// type and left existing unls alone. I understand your desire for compatibility, but the old url/gnx code was unbearably complicated. I have spent the last week wrestling with the issues. I don't

Re: leojs alpha

Thanks Arjan!! Simple encouragements and feedback means a lot to me! Félix On Sunday, June 25, 2023 at 9:03:39 AM UTC-4 Arjan wrote: > > After coding for a few years > > Awesome perseverance. I've just continued using regular Leo because I'm > used to the workflow, but I hope to find some

Re: About PR #3215: unbreakable unls!

Thanks for this simplification! supporting Leo's unl links is on my todo list for leojs (and leointeg!) Félix On Sun, Jun 25, 2023 at 2:38 PM jkn wrote: > Yes, I was a bit surprised this wasn't your approach as well. Looking > forward to the results regardless... > > > On Sunday, June 25, 2023

Re: About PR #3215: unbreakable unls!

Yes, I was a bit surprised this wasn't your approach as well. Looking forward to the results regardless... On Sunday, June 25, 2023 at 5:49:36 PM UTC+1 tbp1...@gmail.com wrote: > I would rather have created a new gnx:// type and left existing unls > alone. Will existing UNL syntax and

Re: About PR #3215: unbreakable unls!

I would rather have created a new gnx:// type and left existing unls alone. Will existing UNL syntax and methods still work? On Sunday, June 25, 2023 at 12:00:26 PM UTC-4 Edward K. Ream wrote: > PR #3215 changes > many files in complex

Re: Leo active file bug and how to get the content of unl

> > Probably a good place is leo-editor-contrib. > Interesting resources! Thanks, and have a nice day :D -- -- 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,

About PR #3215: unbreakable unls!

PR #3215 changes many files in complex ways. See detailed comments in the first comment of the PR. This PR started as a fix for a minor bug , but work expanded in unexpected directions.

Re: Leo active file bug and how to get the content of unl

On Sunday, June 25, 2023 at 10:20:28 AM UTC-4 iamap...@gmail.com wrote: c0, p0 = c, c.p c2 = g.handleUnl(unl, c) content = c2.p.b # < here is the content of the UNL's body c0.selectPosition(p) Oops, typo! The last line should read c0.selectPosition(p0) Hi, Thomas, It works, thank you!

Re: Leo active file bug and how to get the content of unl

> > c0, p0 = c, c.p > c2 = g.handleUnl(unl, c) > content = c2.p.b # < here is the content of the UNL's body > c0.selectPosition(p) > > Oops, typo! The last line should read > > c0.selectPosition(p0) > Hi, Thomas, It works, thank you! It's a useful snippet, we should write it down. But where

Re: Leo active file bug and how to get the content of unl

Markdown won't know what to do with a UNL, so you can't expect navigation to work in the rendered page. Also, remember that if an outline's organization gets changed - i.e., you move a node - its UNL won't be correct any more. So you only want to use UNLs like that when you have high

Re: Leo active file bug and how to get the content of unl

Thanks Thomas, I'll try it later Another thought: is it a good idea to take UNL as a system level schema? I can record somewhere like markdown `[something](unl://xxx)` or even pass parameter to that schema if the unl is a script... `unl://x?para1=leo` On Sun, Jun 25, 2023 at 9:07 PM

Re: Leo active file bug and how to get the content of unl

On Sunday, June 25, 2023 at 9:05:20 AM UTC-4 Thomas Passin wrote: On Sunday, June 25, 2023 at 8:43:25 AM UTC-4 iamap...@gmail.com wrote: For now, my UNL points to a position of the current outline. Could we have a quick way to get it? Assuming that these commands will continue to work after

Re: Leo active file bug and how to get the content of unl

On Sunday, June 25, 2023 at 8:43:25 AM UTC-4 iamap...@gmail.com wrote: For now, my UNL points to a position of the current outline. Could we have a quick way to get it? Assuming that these commands will continue to work after the PR: c0, p0 = c, c.p c2 = g.handleUnl(unl, c) content = c2.p.b

Re: leojs alpha

> After coding for a few years Awesome perseverance. I've just continued using regular Leo because I'm used to the workflow, but I hope to find some time to play with the newer developments. Good luck! On Thursday, June 22, 2023 at 1:08:48 PM UTC+2 Edward K. Ream wrote: > > ...So anywhere

Re: Leo active file bug and how to get the content of unl

"Remove support for cross-file UNLs" - WTF??? This will break some of my scripts. How are we going to navigate to other outlines by UNL? Wasn't that half of the point of having UNLs in the first place? This looks like a situation where we should be adding a new API method, not changing how

Re: Leo active file bug and how to get the content of unl

> > > > Do you mean you want a method or function to return the text of the body > of the node addressed by the UNL? In general, the UNL could point to > another outline. Will you be looking only in the current outline, or any > outline? And if the latter, do you care if that other outline gets

Re: Leo active file bug and how to get the content of unl

On Sun, Jun 25, 2023 at 7:22 AM Thomas Passin wrote: > > On Sunday, June 25, 2023 at 7:59:09 AM UTC-4 iamap...@gmail.com wrote: > > > > Would you explain more fully what you mean by "access the content of..."? > One way is to CTRL-click on the UNL's string in a body node. This will > navigate

Re: Leo active file bug and how to get the content of unl

On Sunday, June 25, 2023 at 7:59:09 AM UTC-4 iamap...@gmail.com wrote: Would you explain more fully what you mean by "access the content of..."? One way is to CTRL-click on the UNL's string in a body node. This will navigate you to that location, opening the outline if necessary. It

Re: Leo active file bug and how to get the content of unl

> > > > Would you explain more fully what you mean by "access the content of..."? > One way is to CTRL-click on the UNL's string in a body node. This will > navigate you to that location, opening the outline if necessary. It should > also be easy enough to write a new command that navigates to a

Re: Leo active file bug and how to get the content of unl

On Sunday, June 25, 2023 at 3:27:38 AM UTC-4 iamap...@gmail.com wrote: [snip] 2. Is there a simple method to access the content of a specific `unl://` node? I found `core/LeoPyRef.leo#Code-->Core classes-->@file leoGlobals.py-->g.Urls & UNLs`, but it doesn't seem to provide the right

Re: Leo active file bug and how to get the content of unl

On Sunday, June 25, 2023 at 3:27:38 AM UTC-4 iamap...@gmail.com wrote: [snip] 2. Is there a simple method to access the content of a specific `unl://` node? I found `core/LeoPyRef.leo#Code-->Core classes-->@file leoGlobals.py-->g.Urls & UNLs`, but it doesn't seem to provide the right function

Leo active file bug and how to get the content of unl

Hi, there, I am delighted to see that the Leo editor is still under active development. The leojs has been a pleasant surprise as well. After a hiatus of several years, I have returned to using the Leo editor. To this day, I have yet to find any software on the market that rivals the advanced