> On 17 Oct 2024, at 12:00, Lennart Poettering wrote:
>
> That does not answer the question. Is it the inner or the outer pty
> you are issuing that stty command on?
1. Start konsole
2. stty intr ^g
3. run0
Is that what you need?
Barry
--
___
dev
> On 16 Oct 2024, at 16:26, Lennart Poettering wrote:
>
> You didn't mention which terminal precisely your are doing this weird
> config on though: before you invoke run0 (i.e on your terminal app's
> pty) or while you are inside of run0 (i.e. on run0's pty). This
> matters a lot and makes a ma
On Do, 17.10.24 11:35, Barry Scott (ba...@barrys-emacs.org) wrote:
> > You didn't mention which terminal precisely your are doing this weird
> > config on though: before you invoke run0 (i.e on your terminal app's
> > pty) or while you are inside of run0 (i.e. on run0's pty). This
> > matters a lo
> On 16 Oct 2024, at 16:26, Lennart Poettering wrote:
>
> ^G is BEL btw, i.e. you are redefining what happens if something
> generates an event that shall ring the terminal bell, and turn it into
> SIGINT. Which is really really weird.
As output the Ctrl-G will cause the BEL actions of the ter
On Mi, 16.10.24 15:37, Barry Scott (ba...@barrys-emacs.org) wrote:
[I am aware you reported this issue on
https://github.com/systemd/systemd/issues/34604 before. Some more
comments below.]
> I'm tracking down an issue with then run0 command in f41.
>
> In a KDE konsole terminal run0 fails to work
I'm tracking down an issue with then run0 command in f41.
In a KDE konsole terminal run0 fails to work after
stty intr ^g
It just exits without an error message, exit code 130.
Running run0 via gdb or strace makes things work.
Which leaves me with fprintf debugging.
I have been adding fprintf t
