From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: sdl.web@gmail.com, 16617@debbugs.gnu.org
Subject: bug#16617: 24.3.50; REGRESSION: `C-q ?' pops up annoying *Char Help* buffer
Date: Thu, 03 Apr 2014 12:32:02 -0700 [thread overview]
Message-ID: <533DB732.70704@dancol.org> (raw)
In-Reply-To: <83ppky9pyn.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Drew's right this time.
On 04/03/2014 12:24 PM, Eli Zaretskii wrote:
>> Date: Thu, 3 Apr 2014 11:38:15 -0700 (PDT)
>> From: Drew Adams <drew.adams@oracle.com>
>> Cc: drew.adams@oracle.com, 16617@debbugs.gnu.org
>>
>> What problem did I report? "`C-q ?' pops up an annoying
>> "*Char Help*" buffer." What part of that is not clear?
>
> It's clear, I just don't agree that it's a problem. It is intended
> behavior shared by many other Emacs commands.
>
>> Why should `C-q ?' show any "help"?
>
> Because '?' is a help character.
We should make an exception for C-q. Its purpose is explicitly to
*override* normal Emacs convention. I'd be happy echoing a help message
as soon as C-q is entered, and maybe popping up help on F1, but we
should certainly treat "?" like any other character.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-04-03 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<891cf052-6085-4ad4-b03b-83379a85ff0f@default>
[not found] ` <<7367bf77-7602-4a02-82ce-804c2f88bf25@default>
[not found] ` <<m3sipuv8og.fsf@gmail.com>
[not found] ` <<831txebg2x.fsf@gnu.org>
2014-04-03 18:38 ` bug#16617: 24.3.50; REGRESSION: `C-q ?' pops up annoying *Char Help* buffer Drew Adams
2014-04-03 19:24 ` Eli Zaretskii
2014-04-03 19:32 ` Daniel Colascione [this message]
2014-04-04 7:44 ` Eli Zaretskii
[not found] <<f842dbc1-09a3-4601-9f98-e580906762c7@default>
[not found] ` <<83r45c98yb.fsf@gnu.org>
2014-04-04 20:20 ` Drew Adams
[not found] <<f87a9a1b-9378-4755-bbac-c88209ed8297@default>
[not found] ` <<83ppky9pyn.fsf@gnu.org>
2014-04-03 20:58 ` Drew Adams
2014-04-04 8:02 ` Eli Zaretskii
[not found] ` <<533DB732.70704@dancol.org>
[not found] ` <<83k3b5a69r.fsf@gnu.org>
2014-04-04 16:25 ` Drew Adams
2014-04-04 19:43 ` Eli Zaretskii
2014-02-01 19:15 Drew Adams
2014-04-02 17:11 ` Drew Adams
2014-04-03 11:04 ` Dmitry Gutov
2014-04-03 14:32 ` Drew Adams
2014-04-03 15:16 ` Eli Zaretskii
2014-04-03 15:23 ` Dmitry Gutov
2014-04-03 13:34 ` Leo Liu
2014-04-03 15:14 ` Eli Zaretskii
2014-04-03 15:39 ` Leo Liu
2014-04-03 15:51 ` Eli Zaretskii
2014-06-19 15:43 ` Stefan Monnier
2014-06-20 0:16 ` Leo Liu
2014-04-03 16:24 ` Eli Zaretskii
2014-04-06 19:33 ` Stefan Monnier
2014-04-07 2:43 ` Eli Zaretskii
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=533DB732.70704@dancol.org \
--to=dancol@dancol.org \
--cc=16617@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=sdl.web@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 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).