From: Andreas Schwab <schwab@linux-m68k.org>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 70519@debbugs.gnu.org
Subject: bug#70519: 30.0.50; Device for Emacs terminal I/O
Date: Sat, 04 May 2024 20:40:54 +0200 [thread overview]
Message-ID: <874jbd4dzd.fsf@igel.home> (raw)
In-Reply-To: <87seyx8map.fsf@gmail.com> (Helmut Eller's message of "Sat, 04 May 2024 20:27:42 +0200")
On Mai 04 2024, Helmut Eller wrote:
>> On Mai 04 2024, Helmut Eller wrote:
>>
>>> 3) Now when I press C-c in terminal B, I see ^C. This is not what I
>>> expect. I would expect that Emacs is interrupted and exits the same
>>> way a GUI Emacs exits when pressing C-c.
>>
>> Why do you expect that? You have told Emacs to use a different
>> terminal, and a process can only have a single controlling terminal. It
>> is unusual for GUI processes to have controlling terminals.
>
> I expect that so that I can press C-c in terminal B to interrupt and
> exit Emacs like in GUI mode.
Why do you expect that? You have told Emacs to use a different
terminal, and a process can only have a single controlling terminal. It
is unusual for GUI processes to have controlling terminals.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2024-05-04 18:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 20:09 bug#70519: 30.0.50; Device for Emacs terminal I/O Helmut Eller
2024-04-23 5:32 ` Eli Zaretskii
2024-04-23 6:09 ` Helmut Eller
2024-05-04 10:34 ` Eli Zaretskii
2024-05-04 15:47 ` Helmut Eller
2024-05-04 16:19 ` Eli Zaretskii
2024-05-04 16:25 ` Helmut Eller
2024-05-04 17:03 ` Eli Zaretskii
2024-05-04 16:36 ` Paul Eggert
2024-05-04 17:19 ` Eli Zaretskii
2024-05-04 17:39 ` Paul Eggert
2024-05-04 18:19 ` Andreas Schwab
2024-05-04 18:27 ` Helmut Eller
2024-05-04 18:40 ` Andreas Schwab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jbd4dzd.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=70519@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.