Re: [error] under m1 chip's macOS 12.3.1 with homebrew

2022-05-06 Thread Zoom.Quiet
BTW: install steps is: 0: base ARM version Homebrew install Python@3.10 1: usage it create venv ༄ python3.10 -m venv .py310leo 2: activate it ༄ source .py310leo/bin/activate 3: base pip install Leo ༄ pip install leo Zoom.Quiet 于2022年5月6日周五 20:01写道: > > in the old MBP i install Leo flow > Inst

Re: Should execute-general-script Run On A Thread?

2022-05-06 Thread Edward K. Ream
On Wed, May 4, 2022 at 4:37 PM tbp1...@gmail.com wrote: here i want to open a discussion of whether the execute-general-script > should be made to be non-blocking. > Yes, that would be good. > if yes, there are some complications, such as where the output should go > when several instances of

Re: [error] under m1 chip's macOS 12.3.1 with homebrew

2022-05-06 Thread Edward K. Ream
On Fri, May 6, 2022 at 7:51 AM tbp1...@gmail.com wrote: > this looks like a problem with Qt or PyQt, not leo per se. possibilities: > > - try to install PyQt6 on its own (without the rest of leo); > - try to install an earlier version of PyQt6, if you can figure out which > ones are available; >

Re: Non-ASCII characters in a node body make edit operations produce unintended results

2022-05-06 Thread Edward K. Ream
On Thu, May 5, 2022 at 9:27 AM Arjan wrote: > It's not a new problem: > https://github.com/leo-editor/leo-editor/issues/1368 Yes. I have no idea how it could be fixed. Anyone have any suggestions? Edward -- You received this message because you are subscribed to the Google Groups "leo-edit

Re: Specific command behavior : goto-first/last-visible-node

2022-05-06 Thread Edward K. Ream
On Friday, May 6, 2022 at 12:03:55 AM UTC-5 Félix wrote: To me it feels counter intuitive to have those two operations change the > collapsed state of nodes using *expandOnlyAncestorsOfNode*(p), as i feel > they should use *treeSelectHelper(p)* which doesn't change the collapsed > states of nod

Re: Non-ASCII characters in a node body make edit operations produce unintended results

2022-05-06 Thread tbp1...@gmail.com
I'm in the dark too, but when i encountered the same problem several leo versions ago, i raised the issue and then after a few more merges the problem was gone. actually, that time it was more serious because every use of the ctrl key (iirc) inserted those symbols. it's always been those exac

Re: Non-ASCII characters in a node body make edit operations produce unintended results

2022-05-06 Thread Edward K. Ream
On Fri, May 6, 2022 at 12:02 PM tbp1...@gmail.com wrote: the symbols involved do not change with the font, so it's not a matter of > missing or wrong glyphs getting drawn. it might be something like utf8 > decoding getting shifted by a bit or a nibble, or getting an extra byte > inserted spuriou

Re: [error] under m1 chip's macOS 12.3.1 with homebrew

2022-05-06 Thread Zoom.Quiet
Edward K. Ream 于2022年5月6日周五 22:14写道: > > On Fri, May 6, 2022 at 7:51 AM tbp1...@gmail.com wrote: >> >> this looks like a problem with Qt or PyQt, not leo per se. possibilities: >> >> - try to install PyQt6 on its own (without the rest of leo); >> - try to install an earlier version of PyQt6, if y

Re: Specific command behavior : goto-first/last-visible-node

2022-05-06 Thread Félix
Thanks for those clarifications Edward, I totally see why, and agree, that the contraction performed is useful and mostly desired, when going from a find-match to the next, etc. and the other commands that are fine-tuned and handled by the boolean settings you mentioned also make total sense fo