Re: @auto-md: multiple vnodes with gnx

Oh, you mean that the headline indent level should translate into the right number of "###" characters? You are right that an @clean file wouldn't do that. What would be just right is the rst3 command, except adapted for MD instead of RsT. I've been thinking there ought to be such a command.

Re: @auto-md: multiple vnodes with gnx

One possibility is to import an MD file as an @auto-md. This way you will get the sections set up as you expect. Then change it to be an @clean file, then save the outline. After this, the external file will always track what is in your outline (and if you edit the external file with some

Re: Leointeg - A beginner fumbles!

On Wednesday, August 23, 2023 at 9:01:46 PM UTC-4 Félix wrote: Also, i don't know what "-m" does after "py", but since it worked, then perhaps the python command you should put in is "py -m" . This is something that everyone should learn. The -m flag means to run the parameter as a module.

Re: Leointeg - A beginner fumbles!

On Wednesday, August 23, 2023 at 12:32:47 PM UTC-4 Israel Hands wrote: Hi tbp1 - thanks a lot for stopping by with help! Having restarted my machine, I ran the command you suggested and despite throwing up all the errors I listed above the server ran and I can connect from VSCode - hey hey!!

Re: Leointeg - A beginner fumbles!

I tried running leoserver directly and it worked. That is, LeoInteg in VSC was able to connect. I have Leo 6.7.4 installed. Here is the command I used (on Windows): py -m leo.core.leoserver What command did you use to start leoserver.py? On Tuesday, August 22, 2023 at 10:38:28 AM UTC-4

Re: divmod with negative Decimal values

On 8/18/2023 5:14 AM, Rob Cliffe via Python-list wrote: divmod(Decimal("-1"), 60) It's not divmod per se, but the modulus operation: from decimal import Decimal D1 = Decimal(-1) D1 % 60 # Decimal(-1) fmod() performs the same way: from math import fmod fmod(-1, 60) # -1.0 From the Python

Re: LeoInteg Log Pane Apps

On Tuesday, August 22, 2023 at 3:43:18 AM UTC-4 iamap...@gmail.com wrote: RPCalc Very interesting, Thomas. I'll try it later :D Btw, I found your gf4-project is also an interesting topic, but I haven't had time to play with

Re: LeoInteg Log Pane Apps

Here's the original announcement: RPCalc <https://groups.google.com/g/leo-editor/c/nXPgvH05ZvM/m/l7XBHl0vAQAJ> On Monday, August 21, 2023 at 10:13:37 PM UTC-4 Thomas Passin wrote: > It's a fairly new plugin I wrote, a reverse polish notation (RPN) > calculator - the type that HP

Re: LeoInteg Log Pane Apps

It's a fairly new plugin I wrote, a reverse polish notation (RPN) calculator - the type that HP made famous. It displays in the log pane. I adapted an existing stand-alone calculator. I add a button to all outlines to launch it. See that attached image. On Monday, August 21, 2023 at 9:00:53 

LeoInteg Log Pane Apps

I have posted here about several apps I've written that display in the log pane, including my browser bookmarks manager, the current version of the Viewrended3 plugin (which can optionally display in the log pane), and the RPCalc plugin. Most of them interact with with Leo's tree. They are

Re: LeoInteg 1.0.14 released

I had the same situation. I found I had to update vsc, then restart vsc. I had automatic updates for extensions enabled, and after the restart, Leointeg's version had been updated to 1.0.14. Félix should probably put a note about this into the install docs. On Monday, August 21, 2023 at

Re: Leo 6.7.4 released

17, 2023 at 5:11 PM Thomas Passin wrote: > > I upgraded my Windows 6.7.3 installation to 6.7.4 using pip: >> >> py -m pip install --user --upgrade leo >> >> It installed correctly but I got this deprecation warning: >> >> C:\Users\tom>py -m pip install

Re: Leo 6.7.4 released

I upgraded my Windows 6.7.3 installation to 6.7.4 using pip: py -m pip install --user --upgrade leo It installed correctly but I got this deprecation warning: C:\Users\tom>py -m pip install --upgrade --user leo DEPRECATION: Loading egg at

Re: Discuss: Remove read-outline-only command?

I suppose this command exists in case something goes wrong with an external file such that Leo can't open the outline. I don't know if that is possible or not. Suppose it's possible. I would open a new outline, and try to import that external file in the hopes that I could figure out the

Re: ENB: Ahas re paste-retaining-clones

Best wishes on your birthday from this quarter, too! On Sunday, August 13, 2023 at 1:13:18 PM UTC-4 Edward K. Ream wrote: On Sunday, August 13, 2023 at 12:00:43 PM UTC-5 David Szent-Györgyi wrote: > Thank you for working on your birthday and giving a gift to us all. -- You received this

Re: Press ⌘ then click node

It also works with two slashes: file://. On Thursday, July 27, 2023 at 6:12:27 AM UTC-4 jkn wrote: > Yes, three slashes works for me as well, and is 'correct' as a URI. > > I am not quite sure why I thought it was four slashes. I think I worked > with some app at one point which needed the

Re: Press ⌘ then click node

Not just the first line - any line with a recognizable URL should show that URL to be highlighted, and a CTRL-Click (or the Apple equivalent) on the highlighted URL will navigate you to it in the browser. CTRL-Clicking can navigate you to: - A URL, as above; - a node within a Leo outline (by

Interesting Post on The Old New Thing - Do Nothing At First

Before you try to do something, make sure you can do nothing -- 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,

Re: Leo 6.7.4: status report

On Monday, July 24, 2023 at 2:08:34 PM UTC-4 Edward K. Ream wrote: The PR will complete #3452 , a paste-based undo scheme. I'll write a new unit test for the new code. *Note*: the two new unit tests perform three cycles of undo/redo, so

Re: Search for node by GNX with g.findGnx

> >> I didn't word that right. I meant that the string returned by the dialog >> isn't a gnx string that can be found. In my test case, the gnx in the >> clipboard started with "*gnx:*" When I manually removed the "*gnx:*" >> prefix, @Lewis's script r

More on LLM-Assisted Programming

Elevating the Conversation with LLM Assistants -- 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

Re: Search for node by GNX with g.findGnx

I think that findGnx() should work whether or not the string starts with the "gnx:" prefix. On Tuesday, July 18, 2023 at 4:16:31 PM UTC-4 Edward K. Ream wrote: > On Tue, Jul 18, 2023 at 3:07 PM Thomas Passin wrote: > >> I didn't word that right. I meant that the string

Re: Search for node by GNX with g.findGnx

, 2023 at 3:58:56 PM UTC-4 Thomas Passin wrote: > The problem here is not with findGnx() or es_clickable_link(). The > problem is that g.app.gui.runAskOkCancelStringDialog(c,'SEARCH Node by > GNX',"Enter search GNX: ") is failing to find an existing gnx*.* &g

Re: Search for node by GNX with g.findGnx

The problem here is not with findGnx() or es_clickable_link(). The problem is that g.app.gui.runAskOkCancelStringDialog(c,'SEARCH Node by GNX',"Enter search GNX: ") is failing to find an existing gnx*.* Checking to see if it has returned None or not will prevent a exception, but the failure

Re: Discuss: load-leo.html should refer visitors to vscode.dev

As we have discussed in the PR conversation, I think *leoad-leo.html* needs to go away, one way or another. It's way too feeble even if we got it working again. It wouldn't either give visitors a feel for what Leo can do or even a feel that it is well designed. OTOH, who knows when

Re: ENB: About immutable positions

On Saturday, July 15, 2023 at 5:49:29 PM UTC-4 Edward K. Ream wrote: My initial post in this thread showed how Leo could support Imps (Immutable Positions) without changing Leo's Position or VNode classes. I concluded that Imps were not a good idea :-) Vitalije not-so-subtly implies that

Re: Leo 6.7.4 is code complete. Please test

Are these changes merged into the 6.7.4 branch yet? IOW, should we be trying out devel or 6.7.4 On Saturday, July 15, 2023 at 5:12:14 PM UTC-4 Edward K. Ream wrote: > On Saturday, July 15, 2023 at 7:22:47 AM UTC-5 Edward K. Ream wrote: > > > 6.7.4 is code complete. Please test the devel

Re: About undoing commands, especially tree operations

On Saturday, July 15, 2023 at 8:13:11 AM UTC-4 Edward K. Ream wrote: On Sat, Jul 15, 2023 at 7:02 AM Thomas Passin wrote: >> A new data module must be completely compatible will all existing scripts, plugins and Leo's core. I don't believe such a compatible data model is possible. &g

Re: About undoing commands, especially tree operations

On Saturday, July 15, 2023 at 6:11:59 AM UTC-4 Edward K. Ream wrote: A new data module must be completely compatible will all existing scripts, plugins and Leo's core. I don't believe such a compatible data model is possible. I think this is the key here. Using a completely new data model

Re: About undoing commands, especially tree operations

On Friday, July 14, 2023 at 12:14:03 PM UTC-4 Edward K. Ream wrote: I *understated *the performance advantages of VNodes. Leo forms clones in constant time. In comparison, MORE took O(N**2) time to make clones. MORE could be much worse than 100x slower than Leo. Also, MORE made clones by

Re: Leo 6.7.4 on schedule for Friday, July 14

On Friday, July 14, 2023 at 11:52:58 AM UTC-4 Edward K. Ream wrote: Thanks for your testing :-) Have you had to make any changes to your zettelkasten plugin? I actually have two, the one I use all the time and the one I prepared as a stand-alone outline for other people to use. Same for

Re: Leo 6.7.4 on schedule for Friday, July 14

I've been using the 6.7.4 branch for several days and have not hit any problems so far. Leo 6.7.4-devel, 6.7.4 branch, build a20d3abd77 2023-07-11 09:48:21 -0500 Python 3.11.4, PyQt version 6.4.3 Windows 10 AMD64 (build 10.0.19045) SP0 On Tuesday, July 11, 2023 at 10:12:45 AM UTC-4 Edward K.

Re: About undoing commands, especially tree operations

On Friday, July 14, 2023 at 9:23:50 AM UTC-4 Edward K. Ream wrote: Leo's VNode class is the heart of Leo. It has a long history. It handles clones two orders of magnitude faster than the MORE outliner. All of its complications exist for a purpose. Of course they do. The situation is

Re: About undoing commands, especially tree operations

On Friday, July 14, 2023 at 8:24:17 AM UTC-4 Edward K. Ream wrote: On Fri, Jul 14 vitalije wrote: > I just wished to illustrate how dangerous and tricky things can get when we have mutable state buried so deep down in the foundations of Leo's code. I agree. That's what PR #3438

Re: About undoing commands, especially tree operations

After reading this, I looked at the VNode class definition for the first time. Ouch! I think this must be an example of serious technical debt. No doubt it seemed reasonable or even necessary but as I look at it without knowing the history or even much about how it's used, it's not how I try

Re: Aha: no need for a new paste command

, at least to me. I better write some clarifying text about these commands in the new user guide I'm slowly working on, I suppose. On Saturday, July 8, 2023 at 8:50:14 AM UTC-4 Edward K. Ream wrote: > On Sat, Jul 8, 2023 at 6:53 AM Thomas Passin wrote: > >> No, I haven't tried it

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

On Saturday, July 8, 2023 at 8:28:09 AM UTC-4 Edward K. Ream wrote: On Sat, Jul 8, 2023 at 6:47 AM Thomas Passin wrote: Using the ekr-tweak-unls branch breaks both the bookmarks and zettel tabbed apps. I will look into what isn't working, but in the zettel browser, I see it's looking

Re: Aha: no need for a new paste command

No, I haven't tried it. I'm not even sure I would want to. Think about how the Windows file explorer works. If you copy a file and paste it, it gives the pasted file a name that includes "copy" if there is another file with that name in the same directory. If there isn't another file in

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

wrote: > On Fri, Jul 7, 2023 at 9:09 PM Thomas Passin wrote: > >> 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. >> > > Hmm. Your plugins might be using g.findUnl indirectly. > >

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: > > #

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: Why gnx-based unls are important

I asked about the duplicate somewhere else (can't find it just now). Edward said the extra node wasn't harmful and would be a reminder for him which he would remove later. On Thursday, July 6, 2023 at 8:37:03 PM UTC-4 iamap...@gmail.com wrote: > I noticed myLeoSettings.leo file has node

Re: Heh. I changed a gnx in the big PR by mistake

: ) On Thursday, July 6, 2023 at 1:44:36 PM UTC-4 Edward K. Ream wrote: > On Thu, Jul 6, 2023 at 11:58 AM Thomas Passin wrote: > > Say you (Edward, I imagine) move a subtree that contains Terry's nodes to >> the Attic. If you forget and just do a cut-and-paste, suddenly they

Re: Heh. I changed a gnx in the big PR by mistake

On Thursday, July 6, 2023 at 12:31:55 PM UTC-4 Edward K. Ream wrote: On Thursday, July 6, 2023 at 11:11:51 AM UTC-5 Thomas wrote: Reminding people (including devs) to "be careful" isn't enough. It's not about being careful. It's about not needlessly cutting/pasting nodes. Devs must not

Re: Heh. I changed a gnx in the big PR by mistake

See, it even happens to Edward. Let's make things so that it won't happen to anyone. Reminding people (including devs) to "be careful" isn't enough. On Thursday, July 6, 2023 at 12:04:18 PM UTC-4 Edward K. Ream wrote: > I'm glad we've had the conversation about cut-node/paste-node. It

Re: "Unbreakable UNLs" Can Break Under A Common Scenario

On Thursday, July 6, 2023 at 11:36:41 AM UTC-4 Edward K. Ream wrote: On Thu, Jul 6, 2023 at 9:28 AM jkn wrote: > So, "once you have learned about gnx's, Cut- and paste- nodes is lost to you"? Not at all. Only Leo's *devs *need to take care. To repeat: a Leo dev is someone who changes Leo's

Re: Why gnx-based unls are important

My computer is a Dell Windows-10 laptop. The status bar display seems to be working as intended. On Thursday, July 6, 2023 at 9:57:16 AM UTC-4 lewis wrote: > On laptop build 947ea935f5 works correctly. > However on PC 947ea935f5 does not show gnx-style format. > > Here is log from PC updating

Re: "Unbreakable UNLs" Can Break Under A Common Scenario

Hmm, we have a real disagreement here. I think that cut-paste within an outline should be equivalent to a move. And anyway, some fundamental property like node identity should not have to depend on whether someone happens to remember a subtle point - if they even had learned about it - when

Re: Why gnx-based unls are important

I have *@string unl-status-kind = legacy *set in myLeoSettings.leo, and the status bar does show the path-based UNL. I added a setting *@string unl-status-kind = gnx* to my workbook, restarted Leo, and for that outline, I see gnx-style addresses in the status bar. Leo 6.7.4-devel, devel

Re: Why gnx-based unls are important

On Thursday, July 6, 2023 at 8:56:59 AM UTC-4 Edward K. Ream wrote: On Wed, Jul 5, 2023 at 10:53 PM Thomas Passin wrote: This is why I am sticking with the legacy format for the status bar. What do you mean by "This"? What @iamap wrote: "Btw, I do believe gnx-based un

Re: "Unbreakable UNLs" Can Break Under A Common Scenario

ike CTRL-D) and moving it by cut-paste. I would say that a user who has not thought about, or maybe not even learned about, gnx's would not expect a unl to break when he did a cut-paste on a node. On Thursday, July 6, 2023 at 8:49:11 AM UTC-4 Edward K. Ream wrote: > On Thu, Jul 6, 2023 at 7

Re: "Unbreakable UNLs" Can Break Under A Common Scenario

is attached. On Thursday, July 6, 2023 at 8:31:07 AM UTC-4 Edward K. Ream wrote: > On Thu, Jul 6, 2023 at 6:40 AM Thomas Passin wrote: > > Maybe a paste of a node should always maintain the gnx unless it would >> create a clone. >> > > Hmm. Under what circumstance woul

Re: Proposal: abandon support for .json files and jupyter notebooks.

I might be more receptive to this idea if we can come up with a way for a user to change in and out of the stay-on-top property and the opacity. It won't work as one-size-fits-all, in my experience. On Thursday, July 6, 2023 at 1:20:46 AM UTC-4 iamap...@gmail.com wrote: > Btw, I believe

Re: "Unbreakable UNLs" Can Break Under A Common Scenario

Maybe a paste of a node should always maintain the gnx unless it would create a clone. On Thursday, July 6, 2023 at 12:21:12 AM UTC-4 Thomas Passin wrote: > I think it's not uncommon to cut a node and paste it somewhere else in the > outline. For example, if I want to move a node fro

"Unbreakable UNLs" Can Break Under A Common Scenario

I think it's not uncommon to cut a node and paste it somewhere else in the outline. For example, if I want to move a node from near the top to near the bottom of a long outline, it would be impractical to move it down node by node or to drag it. I simply cut and paste it. Trouble is, when

Re: Proposal: abandon support for .json files and jupyter notebooks.

On Wednesday, July 5, 2023 at 11:45:48 PM UTC-4 iamap...@gmail.com wrote: Thank you for providing a detailed explanation. By the way, I discovered the `add-editor` command, although it is not as versatile as the FW. I always had trouble using an added editor. I was forever switching one to

Re: Why gnx-based unls are important

This is why I am sticking with the legacy format for the status bar. On Wednesday, July 5, 2023 at 11:27:18 PM UTC-4 iamap...@gmail.com wrote: > Everything will work provided you define *@data unl-path-prefixes* in > your *myLeoSettings.leo* file *on each platform*. These data should > define

Re: Custom Menus Can Be Very Useful - An Example

. On Wednesday, July 5, 2023 at 10:58:50 PM UTC-4 iamap...@gmail.com wrote: > On Thu, Jul 6, 2023 at 10:51 AM Thomas Passin wrote: > >> Just so. I like some custom buttons, but you can only have so many. >> > > I have a small trick where I can place the iconbar vertically on the side

Re: Proposal: abandon support for .json files and jupyter notebooks.

On Wednesday, July 5, 2023 at 10:30:39 PM UTC-4 iamap...@gmail.com wrote: There's a large difference between Edward's work flow and mine - not that either of us has a single "work flow", I'm sure. He likes to use clones extensively - often extracting them with the cff command, I think. I

Re: Custom Menus Can Be Very Useful - An Example

Just so. I like some custom buttons, but you can only have so many. On Wednesday, July 5, 2023 at 10:50:21 PM UTC-4 iamap...@gmail.com wrote: > > I create a custom menu for Leo that is located just before the *Help* > menu. > > Thanks for sharing. > It just like grouped buttons. If I really

Re: Why gnx-based unls are important

On Wednesday, July 5, 2023 at 12:57:33 PM UTC-4 jkn wrote: Apologies for not fully following all of the recent good work here. I meant to mention this earlier but just wanted to check this 'platform independent' part. On my Linux box, I get something in the lower 'status bar' like(*)

Re: Proposal: abandon support for .json files and jupyter notebooks.

On Wednesday, July 5, 2023 at 12:15:59 PM UTC-4 iamap...@gmail.com wrote: As you re-organize a file like this, remember that the *extract* minibuffer command makes the process much easier. Add a line to the top of a block you want to extract, select the whole block, and the *extract* command

Re: Proposal: abandon support for .json files and jupyter notebooks.

On Wednesday, July 5, 2023 at 8:00:47 AM UTC-4 iamap...@gmail.com wrote: In most cases reading a .json file into a single file is a good enough *start*. You can then convert the node to @clean and reorganize as you like. OK, it seems like a reasonable solution. Thanks Edward As you

Re: Discuss: retire two of the three new gnx-related settings?

On Wednesday, July 5, 2023 at 10:50:36 AM UTC-4 Edward K. Ream wrote: On Wed, Jul 5, 2023 at 8:48 AM Thomas Passin wrote: As for your expression paths = list(reversed([z.h for z in p.self_and_parents()])), there is no need to cast it to a list. This is the second time you have made

Re: Custom Menus Can Be Very Useful - An Example

thub.io/leo-editor/customizing.html#menus>. On Wednesday, July 5, 2023 at 6:05:59 AM UTC-4 Edward K. Ream wrote: > On Tue, Jul 4, 2023 at 10:31 PM Thomas Passin wrote: > >> I create a custom menu for Leo that is located just before the *Help* menu. >> It's been so useful th

Re: New PRs related to gnx-based unls

As you have probably read by now in my reply to the other post, I don't agree at all. On Wednesday, July 5, 2023 at 8:02:53 AM UTC-4 Edward K. Ream wrote: > PR #3424 contains > *small* tweaks to Leo's code. > > Retiring the two settings

Re: Discuss: retire two of the three new gnx-related settings?

I disagree about removing the *@string unl-status-kind* setting. I get the most value from the status bar when I can see the path of a node. A gnx-based unl tells me nothing useful. If I want to see if the node is in the outline I think it is, I can look at its tab or the title bar of the

Custom Menus Can Be Very Useful - An Example

I create a custom menu for Leo that is located just before the *Help* menu. It's been so useful that I want to encourage others to create their own. You create one in *myLeoSettings.leo* if you want the menu to be available to all outlines, otherwise create in the outline's @settings tree if

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

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.

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

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

Re: Discuss: Remove all session commands?

I'm not sure we are disagreeing here, and maybe I don't understand the state of the code. I'm saying that if the other commands are in there and working, might as well leave them in. That wouldn't be featuritis since no features would be added. I suppose you could call it "conservation of

Re: Discuss: Remove all session commands?

On Sunday, July 2, 2023 at 10:09:56 AM UTC-4 Edward K. Ream wrote: Leo's now requires only two methods from leoSessions.py: *SM.save_snapshot* and *SM.load_snapshot*. These two methods read and write json data to *~/.leo/session.leo*. Issue #3409

Re: PR3215 UNL Not Found By CTRL-Click

All right, let's put it on the back burner for after the next release. I'll create a reminder issue for it. On Saturday, July 1, 2023 at 5:22:42 AM UTC-4 Edward K. Ream wrote: > On Fri, Jun 30, 2023 at 9:08 PM Thomas Passin wrote: > > Just one thing ... when a CTRL-Click on a UNL

Re: how to get all the content of the body?

On Friday, June 30, 2023 at 10:17:35 PM UTC-4 Thomas Passin wrote: I tested the script with the latest revision of the PR3215 branch that has all the UNL/GNX changes. It still works, Glory Hallelujah! On Wednesday, June 28, 2023 at 10:14:50 AM UTC-4 Edward K. Ream wrote: On Wed, Jun 28, 2023

Re: how to get all the content of the body?

I tested the script with the latest revision of the PR3215 branch that has all the UNL/GNX changes. It still works, Glory Hallelujah! On Wednesday, June 28, 2023 at 10:14:50 AM UTC-4 Edward K. Ream wrote: > On Wed, Jun 28, 2023 at 8:09 AM HaveF HaveF wrote: > > > Super useful function! It

Re: PR3215 UNL Not Found By CTRL-Click

All right, after merging the latest rev, the outlines open correctly on restart, and there is no message about the missing set-rep-dir.cmd file. I went back and checked that problematic UNL and it still is handled correctly. Just one thing ... when a CTRL-Click on a UNL navigates to its

Re: PR3215 UNL Not Found By CTRL-Click

UTC-4 Edward K. Ream wrote: > On Fri, Jun 30, 2023 at 1:25 PM Thomas Passin wrote: > >> Testing the PR3215 branch, I stumbled onto this path-based UNL that Leo >> cannot find using a CTRL-click in a different outline. I copied this UNL >> right from the status bar: >

Re: Transliterate mypy into rust? Using ChatGPT??

I'd try for Julia, myself. It's much more like Python, and reputedly very fast. I think the program is too large to be easy to find all the things the ChatGPT would get plausible but wrong ... On Friday, June 30, 2023 at 3:12:08 PM UTC-4 Edward K. Ream wrote: > I've just asked this question

PR3215 UNL Not Found By CTRL-Click

Testing the PR3215 branch, I stumbled onto this path-based UNL that Leo cannot find using a CTRL-click in a different outline. I copied this UNL right from the status bar: unl://C:/Tom/git/leo-editor/leo/core/LeoPyRef.leo#Code-->Gui base classes-->@file leoFind.py-->class LeoFind

Re: Heads up: The SessionManager class will go away

On Friday, June 30, 2023 at 10:01:24 AM UTC-4 Edward K. Ream wrote: The idea, n*ow fully realized* in PR #3215 , is this: 1. On exit, Leo *always* saves a list of open outlines (automatic session-snapshot-save). 2. When you open Leo without

Re: Heads up: The SessionManager class will go away

Sorry, posted by mistake before I was finished. On Friday, June 30, 2023 at 9:17:54 AM UTC-4 Thomas Passin wrote: On Friday, June 30, 2023 at 9:00:13 AM UTC-4 Edward K. Ream wrote: On Friday, June 30, 2023 at 7:54:48 AM UTC-5 Thomas wrote: I think this is exactly what is wanted most

Re: Heads up: The SessionManager class will go away

On Friday, June 30, 2023 at 9:00:13 AM UTC-4 Edward K. Ream wrote: On Friday, June 30, 2023 at 7:54:48 AM UTC-5 Thomas wrote: I think this is exactly what is wanted most of the time, especially if each of the session-loaded outlines gets navigated to the focus when Leo was last closed. The

Re: Heads up: The SessionManager class will go away

On Friday, June 30, 2023 at 8:41:08 AM UTC-4 Edward K. Ream wrote: 1. On exit, Leo *always* saves a list of open outlines (automatic session-snapshot-save). 2. When you open Leo without specifying any files Leo opens the saved list of outlines (automatic session-snapshot-load). I think this

Re: Heads up: The SessionManager class will go away

I will second this desire. I really like being able to restart Leo and pick up right where I left off. I think that has been a very positive trait of Leo. In fact, it gives the user - or at least me - a sense that Leo is especially well engineered and that user needs have been carefully

Re: Heads Up - My Workbook Is Getting Destroyed

Even though I dislike PRs that are very complicated and try to do too many things, I have to agree in this case. On Thursday, June 29, 2023 at 5:37:32 PM UTC-4 Edward K. Ream wrote: > On Thursday, June 29, 2023 at 3:43:22 AM UTC-5 Edward K. Ream wrote: > > > See #3404

Re: Why does leo asks to restart when a .leo file modification is detected? (instead of asking to reload the file?)

I've wondered about this, too. It seems obvious to me that if LeoPyRef has been changed outside of the Leo session that Leo should restart. This could happen, e.g., if the user checks out a different branch of leo-editor or updates the current branch. For other outlines, maybe the thinking

Re: Heads Up - My Workbook Is Getting Destroyed

sue at all in Leo should > be reported, regardless of whether the steps to replicate are known. The > last thing an editor should ever do is destroy data. > > Jake > > On Wed, Jun 28, 2023 at 1:49 PM Thomas Passin wrote: > >> >> On Wednesday, June 28, 2023 at 11

Re: Heads Up - My Workbook Is Getting Destroyed

On Wednesday, June 28, 2023 at 11:42:37 AM UTC-4 Edward K. Ream wrote: On Wed, Jun 28, 2023 at 10:27 AM Thomas Passin wrote: I've done more testing, and the pattern is definitely repeatable. If I check out the ekr-3181-mypy-links branch, the first time I launch Leo the workbook may

Re: Heads Up - My Workbook Is Getting Destroyed

On Wednesday, June 28, 2023 at 12:52:42 PM UTC-4 jkn wrote: FWIW, I have a vague feeling that something like this happened to me a few months ago. It only occurred the once, and I am not 100% sure what happened, but it definitely involved the CheatSheet 'appearing'. Only mentioning it because

Re: Heads Up - My Workbook Is Getting Destroyed

on the command line. Clearing the recent files list had no effect on the behavior. Nether did deleting the .leo\db directory. On Tuesday, June 27, 2023 at 5:55:37 PM UTC-4 Thomas Passin wrote: > I haven't filed an issue on this yet because I haven't got all the > conditions naile

New Ultra-fast replacement for pylint/flake8

Ruff is a new-ish linter program that does the job of pylint or flake8 but is 100 times or more faster because it is written in Rust. It might be worth looking at for Leo. Here's one of the testimonials: Nick Schrock, founder of Elementl, co-creator of

Re: how to get all the content of the body?

I think you want the method g.getScript(). Look at its docstring in LeoPyRef.leo to see how to use it. BTW, here is how I found it. I remembered that Leo scripts get run by writing a file called *ScriptFile.py*. So I searched for that using the Nav tab. The first thing that came up was in

Heads Up - My Workbook Is Getting Destroyed

I haven't filed an issue on this yet because I haven't got all the conditions nailed down. But Leo has been replacing my workbook with the default CheatSheet ... sometimes. *Please* make sure you have a backup copy until this gets resolved. I noticed this behavior while I was testing code

Re: Discuss: option for short file names in unls?

I have several immediate reactions: 1. It was not long ago that we had a long discussion about whether to keep using functions in @path headlines. The outcome was no, don't include them. Why should it be different here? 2. Existing code in plugins and application-style scripts will break,

Re: About PR #3215: unbreakable unls!

On Monday, June 26, 2023 at 2:26:36 PM UTC-4 Edward K. Ream wrote: On Mon, Jun 26, 2023 at 12:50 PM Thomas Passin wrote: 2. Both the bookmark manager and the zettelkasten apps partially work but not completely. I will look at using these new "legacy" methods next. Let me kno

Status bar behavior, especially with PR 3215

In the status bar, a right-click brings up a two-item context menu: *Select All* and *Copy*. I have always found this a little confusing. *Copy* implies that it will copy the contents (usually the UNL), but actually you have to select it first before *Copy* will do anything. It's possible to

Re: Execute-script in leojs

Lovely! Felix, I have to applaud all this hard and creative work you've been doing! On Monday, June 26, 2023 at 10:26:09 PM UTC-4 Félix wrote: > People have asked about live scripting in leojs in the past (cant remember > who exactly, perhaps Thomas, but I'm not sure) > > That person inquired

Re: Code Review, Requirements, and Community Particiation

On Monday, June 26, 2023 at 5:15:45 PM UTC-4 mys...@gmail.com wrote: On Mon, Jun 26, 2023, 13:34 Thomas Passin wrote: In the announcement about the proposed PR 3215 that massively affects UNLs, @Edward wrote "I won't wait for a code review. The code involved is too tricky to under

<    1   2   3   4   5   6   7   8   9   10   >