From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Shmakov <ivan@siamics.net>
Cc: 30937@debbugs.gnu.org
Subject: bug#30937: In `comment-region', C-g doesn't work
Date: Sun, 25 Mar 2018 21:11:44 +0300 [thread overview]
Message-ID: <83sh8of2jj.fsf@gnu.org> (raw)
In-Reply-To: <87bmfc5a8e.fsf_-_@violet.siamics.net> (message from Ivan Shmakov on Sun, 25 Mar 2018 17:35:45 +0000)
> From: Ivan Shmakov <ivan@siamics.net>
> Date: Sun, 25 Mar 2018 17:35:45 +0000
>
> > ??? How come it works in "emacs -nw" but not on a "Linux tty" (which
> > is what, btw? the raw Linux console?). In both cases, C-g should
> > trigger a SIGINT, so Emacs should be even more responsive to C-g than
> > on X. What am I missing?
>
> I’d think that it means “works with -nw under xterm [or some
> such] but not on a virtual terminal [like /dev/tty2]”.
>
> Personally, I’d look at (and compare) the stty(1) settings for
> the respective tty devices first; like:
>
> $ stty -a -F /dev/tty2
>
> $ stty -a -F /dev/pts/5
If a SIGINT is disabled, then I'd expect Emacs on a TTY to become
completely broken wrt to C-g, because AFAIK there's no other mechanism
on a TTY for Emacs to treat C-g differently from any other key.
But it doesn't do any harm to check the stty settings.
next prev parent reply other threads:[~2018-03-25 18:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 14:28 bug#30937: In `comment-region', C-g doesn't work Alan Mackenzie
2018-03-25 15:32 ` Eli Zaretskii
2018-03-25 15:39 ` Alan Mackenzie
2018-03-25 16:48 ` Eli Zaretskii
2018-03-25 17:15 ` Alan Mackenzie
2018-03-25 18:08 ` Eli Zaretskii
2018-03-25 18:43 ` Andreas Schwab
2018-03-25 19:14 ` Eli Zaretskii
2018-03-25 21:08 ` Andreas Schwab
2018-03-25 17:35 ` Ivan Shmakov
2018-03-25 18:11 ` Eli Zaretskii [this message]
2018-03-31 14:21 ` Noam Postavsky
2019-01-09 1:06 ` Glenn Morris
2019-01-10 11:21 ` Alan Mackenzie
2019-11-02 0:53 ` Stefan Kangas
2018-03-25 16:07 ` Andreas Schwab
2018-03-25 16:01 ` Alan Mackenzie
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sh8of2jj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30937@debbugs.gnu.org \
--cc=ivan@siamics.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).