Re: Discuss: remove support (later) for old unls in g.findUnl?

I've never used g.findUnl() with patterns at all. So as long as the newer one picks up legacy-style unls I'd be OK with it. On Friday, July 7, 2023 at 7:36:26 PM UTC-4 Edward K. Ream wrote: > g.findUnl is the handler for path-based unls. It contains two regex > patterns: > > #

The big PR did remove some gui-related code

There was some discussion (I don't remember where) about a weird edge case: changing a clickable link and then undoing the change *without* saving the file caused Leo not to find the clickable link. I dismissed this nit as likely unrelated to the big PR. However, I now see that the

Discuss: remove support (later) for old unls in g.findUnl?

g.findUnl is the handler for path-based unls. It contains two regex patterns: # (file_name):(comma-separated list of node indices) old_pat = re.compile(r'^(.*):(\d+),?(\d+)?,?([-\d]+)?,?(\d+)?$') # (file_name)::(line_number). new_pat = re.compile(r'^(.*?)(::)([-\d]+)?$') Leo's present unit

Re: Leo 6.7.4 on schedule for Friday, July 14

On Friday, July 7, 2023 at 9:43:38 AM UTC-5 Edward K. Ream wrote: > I still expect to release 6.7.4 one week from today. Leo 6.7.4 should suffice as the foundation of leoJS. I plan to release 6.7.5 in December of this year or earlier if Félix requests doing so. Edward -- You received this

Re: Aha: no need for a new paste command

On Friday, July 7, 2023 at 9:35:51 AM UTC-5 Edward K. Ream wrote: > I'm not going to do this...I've closed this PR and am not likely to reopen it. As always, you can write a plugin that makes Leo work exactly as you want. You do not need my permission :-) Note the preread code in the PR. It

Re: Leo 6.7.4 on schedule for Friday, July 14

On Tuesday, July 4, 2023 at 9:11:18 AM UTC-5 Edward K. Ream wrote: We have 10 days to test the big PR. I expect no significant problems. I still expect to release 6.7.4 one week from today. A lot has happened in the last three days, but the tweaks PR

Re: Aha: no need for a new paste command

On Friday, July 7, 2023 at 7:55:29 AM UTC-5 Thomas wrote: I got some more clarity about this, and I commented the following on the proposed PR: I can now see that the concept of operation is simple. Within an outline, for a parent-and-subtree: - Ask for a move, get a move; gnxs do not

The tweaks PR is coming soon

PR #3424 now contains the following changes: 1. The default settings in leoSettings.leo are: @string unl-status-kind = gnx @bool full-unl-paths = False 2. *g.openUNLFile* fully supports absolute paths and resolves relative paths more

Re: Aha: no need for a new paste command

I got some more clarity about this, and I commented the following on the proposed PR: I can now see that the concept of operation is simple. Within an outline, for a parent-and-subtree: - Ask for a move, get a move; gnxs do not change; - Cut-paste is the same as a move; - Ask for a

Re: Aha: no need for a new paste command

On Friday, July 7, 2023 at 3:59:49 AM UTC-5 Edward K. Ream wrote: > I'll leave #3429 open while we continue our discussion. I have assigned this issue to Leo 6.7.5. No way will this issue be part of 6.7.4. Edward -- You received this

Re: Aha: no need for a new paste command

On Fri, Jul 7, 2023 at 5:42 AM jkn wrote: > I currently only see command paste-retaining-clones. Is this the command > you are referring to (not paste-node-retaining-clones)? > Yes. I misspelled the name of the command. Edward -- You received this message because you are subscribed to the

Re: Aha: no need for a new paste command

I currently only see command paste-retaining-clones. Is this the command you are referring to (not paste-node-retaining-clones)? I presume this is an older command (that I have not knowingly used). I guess I am still ... nervous is not exactly the right word ... about having variants for what

Aha: no need for a new paste command

#3429 suggests that Leo's paste-node command should retain gnxs if doing so would create no gnx clashes in the pasted node. Thomas, Félix and I have been debating what *anyGnxClashes *should check. Should it check the entire pasted