Re: how to resize additional editors?

And also, is there any hotkey to navigate among those editors? -- 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 email to leo-editor+unsubscr...@googlegroups.com. To view

how to resize additional editors?

Recently I discovered a very useful option: add another editor pane to Leo. Now I can have multiple outlines open at the same moment. But. For 'no-docks' mode they are fixed sized and pretty narrow. I've found no way to resize it in a usual manner (I expect here to be a splitter but it's not).

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

I've begun to use it. And already I see that I could use a command to slap a UID into an already existing zettel that doesn't yet have one. I can do it (and have done it) by making a new zettel and copy-pasting the body of the old one to the new one, then delete the old, but that's a bit

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

On Sunday, March 1, 2020 at 7:13:31 PM UTC-5, andyjim wrote: > > On Sunday, March 1, 2020 at 11:36:00 AM UTC-5, Thomas Passin wrote: >> >> I changed the hot keys to Ctrl+F8. Ctrl+F7, Ctrl+F6. They don't seem to >> conflict with either the OS hot keys, or Leo key assignments. According to >>

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

On Sunday, March 1, 2020 at 11:36:00 AM UTC-5, Thomas Passin wrote: > > I changed the hot keys to Ctrl+F8. Ctrl+F7, Ctrl+F6. They don't seem to > conflict with either the OS hot keys, or Leo key assignments. According to > what @Austin(Xu)Wang wrote above, you might have to edit them to use

Re: best practice for test driven development leo script?

Maybe you overlooked it because it scrolled way off the screen, but the output of your test outline, when I ran it, contained this: File "D:\Tom\git\leo-editor\leo\core\leoNodes.py", line 1353, in copy return Position(self.v, self._childIndex, self.stack) RecursionError: maximum recursion

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

I changed the hot keys to Ctrl+F8. Ctrl+F7, Ctrl+F6. They don't seem to conflict with either the OS hot keys, or Leo key assignments. According to what @Austin(Xu)Wang wrote above, you might have to edit them to use "Meta" instead of "Ctrl". I also fixed a bug I hadn't known about for the

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

On Sunday, March 1, 2020 at 12:36:28 AM UTC-5, Thomas Passin wrote: > > > The commands work on linux (and I was able to remove some unnecessary > code). The problem seems to be that Linux intercepts Alt-F8 and Alt-F7 for > its own purposes (like resizing a window). Presumably it's more or less

Re: best practice for test driven development leo script?

> > > > Everything seems fine to me. Both tests pass, as I think they should. > > Within an @test node, p is the position of the @test node itself. > > What do you think the problem is? > > > I clicked "simple test cases collection" node first, so the p.h should be "simple test cases collection"

Re: best practice for test driven development leo script?

On Sun, Mar 1, 2020 at 7:20 AM Xu Wang wrote: > Strange...please find attached a mini outline file to reproduce. > Click node "simple test cases collection" and then "Do-@test" button. > > Below is the output on my console. > Everything seems fine to me. Both tests pass, as I think they

Re: best practice for test driven development leo script?

same result for minibuffer command: run-all-unit-tests-locally Xu Wang 于2020年3月1日周日 下午8:20写道： > Strange...please find attached a mini outline file to reproduce. > Click node "simple test cases collection" and then "Do-@test" button. > > Below is the output on my console. > > Start of Do @test

Re: best practice for test driven development leo script?

Strange...please find attached a mini outline file to reproduce. Click node "simple test cases collection" and then "Do-@test" button. Below is the output on my console. Start of Do @test .. -- Ran 2 tests in 0.013s OK End of

pygments as a syntax highligher

I tried to use pygments as a colorer for JS code. But encountered that when leo configured to use pygments - it colors any code as it was python code, no matter which @language is set atop of a node. I suspect that it was tested with python only, or no other languages have been supported. There

Re: Revised schedule and milestones

Here are the links to the various milestones: - Leo 6.2 . - Leo 6.3 . - Leo 6.4

Revised schedule and milestones

I have been dithering about what to put in Leo 6.2. At last the guiding principle is clear: *Better to live with bugs than live with dubious bug fixes* As a result, I am declaring that 6.2 is code complete. I have assigned #1516 to

Re: best practice for test driven development leo script?

On Sat, Feb 29, 2020 at 12:32 PM Xu Wang wrote: > I tried to use run-all-unit-tests-locally command to execute the two test cases, still got same result. The position read by the test case code is not the real current position. Are you sure? I've never had this kind of trouble. Please show the