Re: Zettelkasten - Notes Jim but not as we know them.

There is something *very* much like the Zettelkasten addressing scheme in Ted Nelson's Xanadu project. Tumblers. If ZK used numbers only and not alpha, and made the scope the entire 'docuverse' ... https://en.wikipedia.org/wiki/Tumbler_%28Project_Xanadu%29 On Tuesday, February 25, 2020 at 8:3

Re: Discuss: don't use Qt docks by default?

No-docks as default is the safest route to a better experience for most people in my opinion. It's just too easy to get things messed up when using docks and getting back to reasonable restart place is very hacky. I suppose it's too complicated to be able to switch dock modes via a menu item or

Re: 2019 retrospective. Plans for 2020

Thank you for the retrospective summary. I was more or less present for all of it, yet it still read like news to me. ;-) -matt -- 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, sen

Re: Discuss: don't use Qt docks by default?

On Tuesday, February 25, 2020 at 2:44:43 PM UTC-5, Edward K. Ream wrote: > When using --no-docks, users can choose the layout using @string > initial-split-orientation = horizontal. > We have got to get a handle on documentation so that things like this surface more easily. If I install a ne

Re: history tracer plugin

Confirmed working now on Linux (yay!) but still not on Win10. I added some info to the issue. I have to leave now but will resume investigating later today. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: 2019 retrospective. Plans for 2020

On Tuesday, February 25, 2020 at 8:43:57 AM UTC-6, Edward K. Ream wrote: > After [6.2] I'll focus on continual incremental improvements to Leo. I forgot to mention one more topic. Leo 6.1 removed emacs-like macro commands, and various expand/contract commands related to windows. Both decisions

Re: clone one node as a child of current position

​On Tue, Feb 25, 2020 at 12:42 PM Xu Wang wrote: > Dear Leo Developer, > > If I know the GNX of one node, how shall I clone it to the position under > current node(as a child of current position)? > ​Good question. gnx's belong to vnodes, not positions. Your question is equivalent to asking,

Re: Discuss: don't use Qt docks by default?

On Tue, Feb 25, 2020 at 12:22 PM Yaakov Belch wrote: > Regarding body-right vs. body-down: > >> If Leo goes this route. I'd like to see the default layout have the body >> pane on the right and the tabs pane on the left under the outline pane. I >> strongly prefer it that way because I think it'

Re: 2019 retrospective. Plans for 2020

On Tue, Feb 25, 2020 at 11:31 AM Thomas Passin wrote: Orange is the new Black?? > Right. It was a joke name. I had intended that the code in leoAst.py would become a stand-alone alternative to black. But I've abandoned that plan, for several reasons. First, and most importantly, I see no reason

Re: Comments re the ZettleKasten work

On Tue, Feb 25, 2020 at 10:53 AM Thomas Passin wrote: I agree with just about everything. > Oh good :-) > You mention @box and @note. Are those directives that already exist in > Leo, or were you contemplating new ones? > They would be new. And they need not be formal directives. They are jus

clone one node as a child of current position

Dear Leo Developer, If I know the GNX of one node, how shall I clone it to the position under current node(as a child of current position)? BR,Austin -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receivi

Re: Discuss: don't use Qt docks by default?

Regarding body-right vs. body-down: > If Leo goes this route. I'd like to see the default layout have the body > pane on the right and the tabs pane on the left under the outline pane. I > strongly prefer it that way because I think it's important to be able to > see more of the body text at once

Re: 2019 retrospective. Plans for 2020

On Tuesday, February 25, 2020 at 9:43:57 AM UTC-5, Edward K. Ream wrote: > > 2019 was supposedly going to be the year of playful prototypes. Instead, > it was consumed by the following ponderous projects :-) > > > There was a big surprise, however. Leo's beautify commands must needs be > comple

Re: Discuss: don't use Qt docks by default?

On Tuesday, February 25, 2020 at 10:37:00 AM UTC-5, Edward K. Ream wrote: > > Imo, reverting to Leo's legacy operation (not using Qt docks) would > simplify life for newcomers. > > This would entail adding a new command-line arguments, say --use-docks. > Those who now *do* use Qt docks would ha

Re: Comments re the ZettleKasten work

On Tuesday, February 25, 2020 at 10:10:18 AM UTC-5, Edward K. Ream wrote: > > The following are only suggestions, based only on my examination of > zettelkasten.leo. > > *Special node names* > > At present, the only "special" nodes (nodes starting with '@') in > zettelkasten.leo are @rst and @p

Re: Zettelkasten - Notes Jim but not as we know them.

On Tuesday, February 25, 2020 at 5:55:36 AM UTC-5, Marcel Franke wrote: > > > > Am Dienstag, 25. Februar 2020 02:37:13 UTC+1 schrieb Thomas Passin: > > Note: Luhmann was the inventer of the zettelkasten. >> > > Ok, just for clarification: No he was not. Zettelkasten is a german word > for a box

Discuss: don't use Qt docks by default?

Imo, reverting to Leo's legacy operation (not using Qt docks) would simplify life for newcomers. This would entail adding a new command-line arguments, say --use-docks. Those who now *do* use Qt docks would have to use this new argument. The --no-docks command-line argument would remain, so tho

Comments re the ZettleKasten work

The following are only suggestions, based only on my examination of zettelkasten.leo. *Special node names* At present, the only "special" nodes (nodes starting with '@') in zettelkasten.leo are @rst and @path nodes. Imo, this is a dubious design. I would have expected to see @box and @note nod

2019 retrospective. Plans for 2020

2019 was supposedly going to be the year of playful prototypes. Instead, it was consumed by the following ponderous projects :-) *1. Support for Qt docks* A ponderous success. Qt docks are not easy to use, but some people appreciate having them, despite the difficulties. *2. The pyzo_in_leo pl

Re: Zettelkasten - Notes Jim but not as we know them.

Am Dienstag, 25. Februar 2020 02:37:13 UTC+1 schrieb Thomas Passin: Note: Luhmann was the inventer of the zettelkasten. > Ok, just for clarification: No he was not. Zettelkasten is a german word for a box (=kasten) of paperslips (=zettel). It's pretty common tool. People before Luhmann used t

Re: Zettelkasten - Notes Jim but not as we know them.

Am Montag, 24. Februar 2020 20:28:05 UTC+1 schrieb andyjim: > I'm still wondering exactly how Luhmann's indexing played out. > He used manual maintained index-cards of keywords. Just big lists of keywords with reference-numbers which he used a startingpoint to dig into a topic. You can lo

Re: leo stopped to understand the outline it was working with before

On Tue, Feb 25, 2020 at 2:24 AM gar wrote: > I debugged a little and found there was a symbol with code 0x1 in the > outline. I removed it and now file can be loaded. > > But I think that this lighted some great problems with leo: > Thanks for your sleuthing. I have just created #1510

Re: How to start up Leo the dumb way

On Tue, Feb 25, 2020 at 4:04 AM Micah Joel wrote: > In Mac Terminal, you can also Cmd+T to open a new tab in the same window. > But if you spend any appreciable amount of time in the Mac command line, > you should go get iTerm2 https://iterm2.com/ > -m > Thanks for this comment. Edward -- You

Re: How to start up Leo the dumb way

In Mac Terminal, you can also Cmd+T to open a new tab in the same window. But if you spend any appreciable amount of time in the Mac command line, you should go get iTerm2 https://iterm2.com/ -m On Tuesday, February 4, 2020 at 3:47:20 PM UTC-8, stevelitt wrote: > > On Sat, 1 Feb 2020 14:51:34 -05

Re: history tracer plugin

I am sorry for being late. I see you have found the solution for connection errors yourself. On Saturday, February 22, 2020 at 7:51:23 AM UTC+1, Matt Wilkie wrote: > > Thanks Vitalije! > > installation went smoothly but the browser doesn't show anything and there > are connection errors in the

Re: leo stopped to understand the outline it was working with before

I debugged a little and found there was a symbol with code 0x1 in the outline. I removed it and now file can be loaded. But I think that this lighted some great problems with leo: 1. I didnt use any other editor or something for editing the outline. This means that bad symbol was entered via th