Closed doctorpangloss closed 1 year ago
The switching of terminal keyboard entry modes in the lower right should be a clue as to what is going on.
Please try the latest prerelease.
There have been some changes to how Ctrl-C is handled. In this case less
no longer responds to Ctrl-C so it can't shut down unexpectedly and leave the terminal in a weird state.
I should add, it wasn't my intention to prevent less
from handling Ctrl-C, it just seems to have happened as a side effect.
The issue still occurs. This time, I press Ctrl-C multiple times to trigger it.
OK, there's another new prerelease which might help.
Things I've noticed:
git
and less
started by xargs
aren't being shut down when Ctrl-C is pressed.bash
) and Linux the command has the same problem, though it's less severe in these cases because the surplus git
and less
shut down after a while when they notice the pipeline is broken.xargs
shut down its child processes when it receives the interrupt.git
configuration or if Windows' more
is specified as the pager. With busybox-w32 or Git for Windows less
explicitly configured the Ctrl-C doesn't interrupt them.
[core]
#pager = c:\\\\windows\\\\system32\\\\more.com
#pager = c:/users/rmy/busybox.exe less
#pager = c:/Program\\ Files/Git/usr/bin/less.exe
Okay, now hitting Ctrl+C no longer quits less
(i.e. git for Windows less) and I must hit q to exit. This matches expectations with POSIX less
.
Reproduction
git
repo.End
.pkill less
to kill less.Reproducing on this repository:
Then hit
End
. Then, good luck :)