From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Juanma Barranquero' <lekktu@gmail.com>, 4718@emacsbugs.donarmstrong.com
Subject: bug#4718: 23.1; C-h f gives doc for the wrong function
Date: Wed, 14 Oct 2009 09:40:50 -0400 [thread overview]
Message-ID: <jwvk4yy6qxw.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <662D8A34F24B4D73ABAD8A7BE21766CC@us.oracle.com> (Drew Adams's message of "Tue, 13 Oct 2009 21:24:08 -0700")
> But we should not impose a regimental `ask' for this in general.
> The problem does not exist for prefix completion. We should show you
> the sole completion and ask for confirmation only when it does not
> correspond to prefix completion. Non-basic completion is the only
> case where there is really an element of surprise, confusion, and lack
> of understanding.
I disagree, the same problem exists for prefix completion. Maybe it's
less frequent, but it exists nevertheless. Which brings us to the
reason why we don't currently ask: choosing the wrong name is harmless
because C-h f does not perform any dangerous operation that might lose
you some work.
>> For what it's worth I have a local patch that indirectly changes this
>> behavior: it accepts any function name (even non-existing ones),
>> requires confirmation for non-existing ones, and then tries to guess
>> which file to load to find the function.
> The problem is not non-existing functions. In that case, the current
> code would still say `No match'. The problem is (a) treating
> additional patterns as matches when combined with (b) RET.
Reread what I wrote: I said "indirectly".
It's related not for its functionality but because if we want to be able
to accept non-existing functions, then RET can't perform completion
any more.
> I don't even think this is specific to `C-h f'. We should probably do
> the same thing most of the time: make RET confirm when the completion
> is not an obvious one (i.e. a suffix).
That's almost already the case: it's fairly rare for Emacs completion to
use this kind of strong `require-match'.
Stefan
next prev parent reply other threads:[~2009-10-14 13:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 23:49 bug#4718: 23.1; C-h f gives doc for the wrong function Drew Adams
2009-10-14 0:28 ` Juanma Barranquero
2009-10-14 1:49 ` Drew Adams
2009-10-14 3:11 ` Stefan Monnier
2009-10-14 4:24 ` Drew Adams
2009-10-14 13:40 ` Stefan Monnier [this message]
2009-10-14 15:59 ` Drew Adams
2009-10-15 3:14 ` Stefan Monnier
2009-10-14 3:32 ` Juanma Barranquero
2009-10-14 4:24 ` Drew Adams
2009-10-14 4:51 ` Juanma Barranquero
2009-10-14 6:25 ` Drew Adams
2009-10-14 13:31 ` Stefan Monnier
2009-10-14 15:50 ` Drew Adams
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=jwvk4yy6qxw.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=4718@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
--cc=lekktu@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.