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

Btw, I believe making some FW windows always stay on the top and set opacity of windows are also useful. https://stackoverflow.com/questions/19097323/setwindowflagsqtwindowstaysontophint-hides-qt-window https://doc.qt.io/qt-6/qwidget.html#windowOpacity-prop -- -- Sincerely, HaveF -- You

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

> > I always had trouble using an added editor. I was forever switching one to > the wrong node because I didn't notice it was focused before navigating in > the tree. Then I'd be typing into the wrong node. IIRC, that was one of > the drivers for me to write the FW plugin. Also, the added

"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: Proposal: abandon support for .json files and jupyter notebooks.

> > Sometimes I think of a FW window as a kind of index card open next to the > work in progress. Also, a FW window is a basic editor that is live on line > with the underlying node. So even if you have selected some other node in > the tree, if you see something that you want to change (in the

Re: Why gnx-based unls are important

Everything will work provided you define *@data unl-path-prefixes* in your *myLeoSettings.leo* file *on each platform*. These data should define an absolute path (platform-specific) for various .leo files. Does that means I can set @data unl-path-prefixes in my current leo file @settings

Re: Custom Menus Can Be Very Useful - An Example

I tried that once and I don't know why I let it slip away. I'll go back and try it again. After all, I like to put the Windows task bar on the left hand side of the screen (Boo to Win11 where apparently you can't do that), and I like my browser tabs displayed in a vertical strip. On

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

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 of the leo so that I can fit a little more buttons. XD -- You received this message because

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: Custom Menus Can Be Very Useful - An Example

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 can't stand my numerous buttons I'll consider using menus. XD -- You received this message because you are subscribed to the Google Groups

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

> > 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 tend > to search using the Nav tab and mark nodes of interest - I have my

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

> > This FAQ entry > > describes in detail how I use clones. I don't understand why more Leonistas > don't follow my example :-) > Perhaps in some cases, words are still a little difficult to convey knowledge adequately :D

Re: Why gnx-based unls are important

On Wed, Jul 5, 2023 at 5:27 PM jkn wrote: > How does the current scheme address the situation of two identically-named > files in different directories? > No. Perhaps I should restore the code that allows full paths for new unls. Otoh, I think this is mostly a theoretical concern. Edward --

Re: Why gnx-based unls are important

How does the current scheme address the situation of two identically-named files in different directories? On Wednesday, July 5, 2023 at 7:41:12 PM UTC+1 Edward K. Ream wrote: > On Wed, Jul 5, 2023 at 12:14 PM Thomas Passin wrote: > > > I don't think the concept of operations for the new UNLs

Re: Ctrl-Click on gnx fails if the node is dirty?

On Wed, Jul 5, 2023 at 4:58 PM jkn wrote: > Whilst experimenting with the new gnx work just now...I came across the following strange behaviour. No idea if it is old or new. Thanks for your testing! This edge case is likely ancient. It is of no great importance. Edward -- You received this

Ctrl-Click on gnx fails if the node is dirty?

Whilst experimenting with the new gnx work just now (I will add a posting to the relevant thread soon, I hope) I came across the following strange behaviour. No idea if it is old or new. 1) pasted a unl:gnx reference into a node 2) Ctrl-LCclick on it: confirm you go to the right node(*) 3) go

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

On Wed, Jul 5, 2023 at 12:06 PM Thomas Passin 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. Correct. > Edward has done

Re: Why gnx-based unls are important

On Wed, Jul 5, 2023 at 12:14 PM Thomas Passin wrote: > I don't think the concept of operations for the new UNLs has been fully worked out yet. I know of no problems whatsoever with gxn-based unls. Leo's new link-resolution code significantly improves the operation of legacy (path-based)

Re: Why gnx-based unls are important

On Wed, Jul 5, 2023 at 11:57 AM jkn wrote: On my Linux box, I get something in the lower 'status bar' like(*) > > unl:///home/jkn/path/to/myfile.leo#node-->subnode-->subnode > > but when I run on my windows machine, the same file (shared via NextCloud) > will not be like this, shurely? What

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

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(*) unl:///home/jkn/path/to/myfile.leo#node-->subnode-->subnode but

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

> > 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 > will pull all those lines into a new node whose headline will be the

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

On Wednesday, July 5, 2023 at 6:29:35 AM UTC-5 Edward K. Ream wrote: If these settings must remain, their default values should change to: - *@string unl-status-kind = gnx* - *@bool full-unl-paths = False* Alright. These settings will remain with the new defaults shown above. It's time to

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: Discuss: retire two of the three new gnx-related settings?

On Wed, Jul 5, 2023 at 8:48 AM Thomas Passin wrote: > 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

Re: Custom Menus Can Be Very Useful - An Example

All right. I've located the part of Leo's docs that cover menu settings. It's in the LeoDocs outline, at (legacy style) unl://C:/Tom/git/leo-editor/leo/doc/LeoDocs.leo#Leo's Documentation-->Users Guide-->@rst html/customizing.html-->Using settings-->Complex settings nodes-->\@menuat or (new

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

Unbreakable unls have already changed my workflow

I am using unbreakable (gnx-based) unls (clickable links) as a lightweight alternative to clones. As you probably know, I use clones extensively while developing code. I create an organizer node for each issue/PR. This organizer node contains clones of all nodes related to my work. Once

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

On Wednesday, July 5, 2023 at 7:00:47 AM UTC-5 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 You're welcome.

New PRs related to gnx-based unls

PR #3424 contains *small* tweaks to Leo's code. Retiring the two settings discussed in this post would be a much bigger change. If Thomas agrees to the change I'll create

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

> > 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 -- -- Sincerely, HaveF -- You received this message because you are subscribed

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

Don't panic. I'm not going to do anything rash. Imo, there is no need for these two new settings: - *@string unl-status-kind = legacy* - *@bool full-unl-paths = True* If these settings must remain, their default values should change to: - *@string unl-status-kind = gnx* - *@bool

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

On Wed, Jul 5, 2023 at 5:07 AM HaveF HaveF wrote: > I don't recall a proposal to abandon .json files. Can you refresh my >> memory? >> > I read it in this thread > : > > > The present importer for (special-format!) .json files

Why gnx-based unls are important

This post explains why PR #3215 (gnx-based unls) is a milestone in Leo's history. gnx-based unls are a fundamental resource comparable in importance to @clean and cff: - Unls won't break if you rename or move a node. - Leo supports

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

> > I don't recall a proposal to abandon .json files. Can you refresh my > memory? > I read it in this thread : > The present importer for (special-format!) .json files is dangerously incorrect. It must either be rewritten or

Re: Custom Menus Can Be Very Useful - An Example

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 that I want to encourage others to create their own. Thanks for this post. Please create a developer info item. Edward -- You received

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

On Wed, Jul 5, 2023 at 3:40 AM HaveF HaveF wrote: > Of course, .ipynb files are not worth to support. > I don't recall a proposal to abandon .json files. Can you refresh my memory? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

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

Of course, .ipynb files are not worth to support. But it's bit sad to see that the JSON file is not supported, after all, json and yaml are two main configuration file formats. Sometimes, I have to read hundred lines of JSON file, often tortured by indentation. I wonder if there are any