--- Original Message ---
On Wednesday, October 4th, 2023 at 18:59, Rob Landley wrote:
> On 10/4/23 13:51, enh via Toybox wrote:
>
> > (since it looks like there are folks actively working on vi atm...)
> >
> > looks like 'b' goes to the end of the previous word, rather than
> >
On Wed, Oct 4, 2023 at 4:59 PM Rob Landley wrote:
>
> On 10/4/23 13:51, enh via Toybox wrote:
> > (since it looks like there are folks actively working on vi atm...)
> >
> > looks like 'b' goes to the _end_ of the _previous_ word, rather than
> > the beginning of the current word?
>
> There's no
On 10/4/23 19:03, Rob Landley wrote:
> And I'm backing slowly away from this Thing That Needs Focus To Clean Up.
> Gotta
> close the open cans of worms first, thanks...
The if/else staircase on TT.vi_mode in vi_main() seems like an obvious potential
place to call ex/normal/insert functions to
On 10/4/23 13:51, enh via Toybox wrote:
> (since it looks like there are folks actively working on vi atm...)
>
> looks like 'b' goes to the _end_ of the _previous_ word, rather than
> the beginning of the current word?
There's no 'b' but there is a "b" (which is weird because all the
(since it looks like there are folks actively working on vi atm...)
looks like 'b' goes to the _end_ of the _previous_ word, rather than
the beginning of the current word?
___
Toybox mailing list
Toybox@lists.landley.net
I caught it running in strace. There's some differences in signal
setup in the forked child, the child exits with 126 in both the good
and bad cases, but the parent exits with 127 after wait4 returns
ECHILD in the bad case.
The good case, child exits with 126, parent exits with 126:
On 10/3/23 23:43, Colin Cross wrote:
> I caught it running in strace. There's some differences in signal
> setup in the forked child, the child exits with 126 in both the good
> and bad cases, but the parent exits with 127 after wait4 returns
> ECHILD in the bad case.
Beat me to it. (Serves me
On 10/3/23 20:18, enh wrote:
>> heh, no "cheetah" is the lunch target. pixel pro 7 was the marketing
>> name. "recent arm64 device running a hwasan build" was what i was
>> trying to say.
Bionic arm64 current android system with hwsan, reproduces in 2% of runs.
>> it's been running just that
