unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Glenn Morris <rgm@gnu.org>
Cc: Noam Postavsky <npostavs@gmail.com>, 30937@debbugs.gnu.org
Subject: bug#30937: In `comment-region', C-g doesn't work.
Date: Thu, 10 Jan 2019 11:21:31 +0000	[thread overview]
Message-ID: <20190110112131.GB4376@ACM> (raw)
In-Reply-To: <9x1s5mhc5o.fsf@fencepost.gnu.org>

Hello, Glenn.

On Tue, Jan 08, 2019 at 20:06:59 -0500, Glenn Morris wrote:
> Noam Postavsky wrote:

> > I'm not able to reproduce this on a Linux tty (I assume that means the
> > virtual terminal you get when pressing Ctrl+Alt+F1).

> Me neither. I tried on two different systems.

> My suggestion is to close this report, since it has been months and
> it doesn't seem to be leading anywhere.

OK, I won't object to closing this bug report, since the bug doesn't
seem to be happening (on Emacs 26.1 and master) at the moment.  I would
object to labelling the closure "not a bug" or "won't fix".

I do, however, raise an eyebrow at the "doesn't seem to be leading
anywhere" justification.  Bugs, particularly difficult bugs (as this one
is) tend "not to be leading anywhere" for a lot of their life times.  It
would be bad just to close such bugs for such reasons, rather than deal
with them.

On a Linux tty, this problem of C-g being non-functional happens to me
relatively often (several times a year), resulting in me having to kill
Emacs and start it again.  Unfortunately I haven't logged these
occurrences at all.  I strongly believe there is a problem in the
keyboard handling area of Emacs, though pinning it down is difficult.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2019-01-10 11:21 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
2018-03-31 14:21     ` Noam Postavsky
2019-01-09  1:06       ` Glenn Morris
2019-01-10 11:21         ` Alan Mackenzie [this message]
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=20190110112131.GB4376@ACM \
    --to=acm@muc.de \
    --cc=30937@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=rgm@gnu.org \
    /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).