From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
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, 3 Apr 2014 13:58:25 -0700 (PDT) [thread overview]
Message-ID: <a4b40679-7483-4181-90d9-6cfb619f1dba@default> (raw)
In-Reply-To: <<83ppky9pyn.fsf@gnu.org>>
> 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.
1. Not in most contexts, it is not. Did you type your reply message in
Emacs? When you typed `?', did Emacs pop up a help buffer? If not,
do you wish it had?
2. And `C-h' IS a help character in most contexts. And yet `C-q C-h'
inserts a Control-Q character - it does NOT pop up a help buffer.
So the argument that help characters must behave the way you claim
just does not hold water.
> > Why doesn't it just insert the character `?'? `C-q w' inserts the
> > character `w'. Why should `C-q ?' act differently?
>
> For the same reason "M-x ?" triggers a different response than "M-x w".
3. `?' is specifically bound to a help command, `minibuffer-completion-help',
in `minibuffer-local-must-match-map'. It is not bound to a help char
in the recipe I gave (e.g. in *scratch*).
4. And I specifically stated that THIS bug report is NOT for the cases
where `?' is bound to a help command. Even though the same arguments
hold for that rare case as well, I will not include it as part of this
bug report. I'm willing to limit THIS bug report to the vast majority
of cases: those in which `?' is NOT bound to a help character.
> You can say this till Kingdom Come, it won't change the basic facts:
> this is a very old feature,
It is still a regression wrt even older behavior.
> and I at least see no reason to remove it,
Too bad.
> since Emacs behaves like that in many other commands.
Name one. What is similar to this?
> End of story.
>
> > > I don't know why '?' should also be excluded
> >
> > It is an ordinary, printable, self-inserting character in the
> > context I reported.
>
> No, it isn't. It is a character that invokes help.
No, it is NOT. Not in the contexts that THIS bug report is about.
emacs -Q
In *scratch*: `C-q ?'
`?' is not a character that invokes help in *scratch*. Likewise
in most buffers/modes.
You try to distract us by giving an example of `?' in
`minibuffer-local-must-match-map', where it IS a help character.
That's a shame.
And even there, I would argue (but not for this bug report) that
`C-q ?' should just insert `?'.
> > `C-q' is SUPPOSED to insert ordinary, self-inserting characters.
>
> And "M-x" is supposed to echo the next word, but '?' still behaves
> differently there.
No, again a strawman. M-x does lots of things. And `?' is not a
word-constituent in the minibuffer for M-x. It is not even
self-inserting. It is 100% irrelevant to THIS bug.
(Oh and BTW, IMO `?' *should* be self-inserting in the minibuffer.)
> Just let go, Drew. You keep repeating the same arguments, and they
> didn't fly the first time.
Ditto. But I would suggest that you think a little more about this.
Do I really care? Not so much, except in so far as I care about
Emacs. I probably came across this bug by accidentally hitting
`C-q ?' instead of `C-q C-?' or something - I really don't recall.
As you point out, this has been broken for a long time. And I only
recently noticed it. It doesn't bother me if you leave this broken
forever. That would be too bad for Emacs (unclean), but I wouldn't
lose any sleep over it. Have a nice day.
next parent reply other threads:[~2014-04-03 20:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<f87a9a1b-9378-4755-bbac-c88209ed8297@default>
[not found] ` <<83ppky9pyn.fsf@gnu.org>
2014-04-03 20:58 ` Drew Adams [this message]
2014-04-04 8:02 ` bug#16617: 24.3.50; REGRESSION: `C-q ?' pops up annoying *Char Help* buffer 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
[not found] <<f842dbc1-09a3-4601-9f98-e580906762c7@default>
[not found] ` <<83r45c98yb.fsf@gnu.org>
2014-04-04 20:20 ` Drew Adams
[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 ` Drew Adams
2014-04-03 19:24 ` Eli Zaretskii
2014-04-03 19:32 ` Daniel Colascione
2014-04-04 7:44 ` 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=a4b40679-7483-4181-90d9-6cfb619f1dba@default \
--to=drew.adams@oracle.com \
--cc=16617@debbugs.gnu.org \
--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).