> On 16 Oct 2024, at 16:26, Lennart Poettering <mzerq...@0pointer.de> 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 terminal.
But as input it will depend on the app that is running.
In the case of stty intr ^g that means the kernel TTY handling willecho ^g and 
turn the Ctrl-g into a SIGINT.

> 
> I mean, there might be some bug lurking somewhere, but this definitely
> *is* a really really weird thing to do.

It's only run0 that has an issue with this.

> 
> 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 major difference.

As I said this is under Plasma KDE Konsole.

> 
> note that when run0 operates it will temporarily turn off any handling
> of keypresses on the terminal app's pty (let's call it the "outer"
> one), by putting the pty into raw mode (via cfmakeraw()). This should
> mean that ^G should be deliverd to run0 as ^G, which it then forwards
> to the other pty (the "inner" one). Which won't handle it, because we
> do not redefine keycodes on the inner one. So the app on the other end
> (likely your shell?) will receive ^G. Most shells will respond to that
> via echoing it back, which should generate a bell event.

We never get that far as the run0 code exits with 130 as its exit code.

Regardless typing Ctrl-g when the terminal is set to stty intr ^c just sees the 
Ctrl-G echo as ^g.

I think I need to see what signal handling the process has setup.
I cannot think of anything else that would cause the process to exit.
While the ppoll() call is running.

Barry


-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to