Re: gnx-based unls make the backlink and quickMove plugins obsolete

This is getting me to think there should be a new method, say c.getCrossfileUnl(p), that returns a tuple (file, gnx). The caller can then assemble the two components into a cross-outline UNL if desired, or just use the gnx part. There would be no need for a caller to root around to find the r

gnx-based unls make the backlink and quickMove plugins obsolete

These plugins create and manage links, including cross-outline links. But gnx-based unls can also refer to nodes in other outlines! Most users will have no need for either plugin. Both plugins save link data in uAs. That's an interesting approach! However, a script could easily create uAs b

Re: Enhancement - Dragging outline to desktop icon should open in same Leo session

\On Monday, July 3, 2023 at 12:38:38 PM UTC-5 Thomas wrote: Some people launch Leo from a desktop icon. If you have such an icon and drag'n'drop an outline on it, the outline will open in a new Leo session. Drag another outline, get yet another Leo session. Feel free to create an enhancemen

Enhancement - Dragging outline to desktop icon should open in same Leo session

Some people launch Leo from a desktop icon. If you have such an icon and drag'n'drop an outline on it, the outline will open in a new Leo session. Drag another outline, get yet another Leo session. Some programs (e.g., Notepad++ on Windows) will open dropped files in the same open session. I

Re: A new unit test pattern

On Mon, Jul 3, 2023 at 11:23 AM Edward K. Ream wrote: g.findAnyUnl assumes that @data unl-path-prefixes is functional. Setting up > this condition is more complicated than usual. > > > One new helper helps simulate the @data unl-path-prefixes setting. > > > The other new helper helps the helper :

A new unit test pattern

I have been adding new unit tests for some (not all) new functions/methods in the big PR. Some of these tests are more complicated than usual. For example, tests of *g.findAnyUnl* require that the *@data unl-path-prefixes* setting refers to actual files. The details are a bit messy, so I

Re: Debate: always save session data?

On Monday, July 3, 2023 at 10:24:39 AM UTC-5 Thoma wrote: On Monday, July 3, 2023 at 10:57:02 AM UTC-4 Edward K. Ream wrote: I'm going to shorten *--always-write-session-data* to *--write-session*. Remember to change *-a* to *-w *(it's the kind of thing I would forget :-) ). The new name

Re: Debate: always save session data?

On Monday, July 3, 2023 at 10:57:02 AM UTC-4 Edward K. Ream wrote: I'm going to shorten *--always-write-session-data* to *--write-session*. Remember to change *-a* to *-w *(it's the kind of thing I would forget :-) ). -- You received this message because you are subscribed to the Google Gro

Re: Debate: always save session data?

On Mon, Jul 3, 2023 at 8:32 AM Thomas Passin wrote: > I just tested the new code for *--always-write-session-data*, and it > worked as expected: > > 1. Open Leo and load several outlines; > 2. Close Leo and re-open with *.leo\workbook.leo* on the command line; > 3. Close and re-open Leo without a

Re: Debate: always save session data?

I just tested the new code for *--always-write-session-data*, and it worked as expected: 1. Open Leo and load several outlines; 2. Close Leo and re-open with *.leo\workbook.leo* on the command line; 3. Close and re-open Leo without an outline on the command line. 4. Observe that the several outli

Re: Debate: always save session data?

On Monday, July 3, 2023 at 6:34:16 AM UTC-5 Edward K. Ream wrote: > A command line is out of the question. ... > So we must choose *now* how Leo will work for *everyone.* It's time to resolve this question! It's funny how writing changes my mind. *Aha!* The only way to resolve this question i

Debate: always save session data?

We disagree about when to write *session data *(a list outlines). Some say, "Always." Others say, "Only if the command line had no outlines." I see no way to allow all Leonistas to make Leo work as they like. A command line is out of the question. My bright idea failed spectacularly :-) So

Re: ENB: About session preferences

On Monday, July 3, 2023 at 5:34:42 AM UTC-5 Edward K. Ream wrote: > Drat. My scheme is in ruins. The only way to enable this plugin would be with a per-outline setting (@enabled-plugins). I'm stuck. My plan, for now: - Leo will always write session data. Sorry Thomas. - A new command-line arg

Re: ENB: About session preferences

On Monday, July 3, 2023 at 4:52:17 AM UTC-5 Edward K. Ream wrote: > I'll modify PR #3215 so that Leo always writes session data. > Those who prefer otherwise can enable the modify_session plugin. Drat. My scheme is in ruins. The only way to

ENB: About session preferences

Thomas has convinced me not to change Leo's session-handling code significantly. I have closed #3417 and its related PR: Leo will retain its session-* commands and related documentation. However, Leonistas disagree about *when *to write

Re: Discuss: Remove all session commands?

On Mon, Jul 3, 2023 at 12:28 AM Robert-Felix wrote: > I have not done the sessions related code yet, (i didnt even know what > they were 5 minutes ago) and I do not intend if i dont have to ! haha! In > fact, I intended to use the same system as in leointeg: It reopens the last > Leo files you ha