From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Philipp Stephani <p.stephani2@gmail.com>,
70519@debbugs.gnu.org, eller.helmut@gmail.com
Subject: bug#70519: 30.0.50; Device for Emacs terminal I/O
Date: Sat, 4 May 2024 10:39:20 -0700 [thread overview]
Message-ID: <447da592-a8c0-4fcb-9d5d-1768dc3bc7be@cs.ucla.edu> (raw)
In-Reply-To: <868r0pfqad.fsf@gnu.org>
On 2024-05-04 10:19, Eli Zaretskii wrote:
> So you are saying that the handling of --terminal in emacs.c is
> incomplete, in that it doesn't call that ioctl on the new stdin?
Sounds like that may be so, if that's what Helmut needs.
> In any case, is the result Helmut reports after typing Ctrl-C
> expected, or does it mean we have a bug when using --terminal?
I don't know. I don't use --terminal. Perhaps others who use it could
weigh in.
> emacs_spawn is about starting a sub-process, which is something
> different from what I'm talking about. Here, the issue is the Emacs's
> own terminal.
This stuff used to be in different and somewhat-duplicated sections of
code, but Philipp refactored and coalesced this in 2020. Perhaps a bit
of the controlling terminal business got lost in the shuffle? I'll cc
this to Philipp to see whether he has insight on the issue. Philipp, the
details are here:
https://bugs.gnu.org/70519
next prev parent reply other threads:[~2024-05-04 17:39 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 [this message]
2024-05-04 18:19 ` Andreas Schwab
2024-05-04 18:27 ` Helmut Eller
2024-05-04 18:40 ` Andreas Schwab
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=447da592-a8c0-4fcb-9d5d-1768dc3bc7be@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=70519@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=p.stephani2@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.