unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuwesh@tutanota.com>
Cc: 49931@debbugs.gnu.org
Subject: bug#49931: 28.0.50; `choose-completion' submits incorrect string when minibuffer content changes after creation of the *Completions* buffer
Date: Sun, 08 Aug 2021 11:19:10 +0300	[thread overview]
Message-ID: <83mtpsgxhd.fsf@gnu.org> (raw)
In-Reply-To: <MgZf2ak--3-2@tutanota.com> (message from Visuwesh on Sun, 8 Aug 2021 09:31:12 +0200 (CEST))

> Date: Sun, 8 Aug 2021 09:31:12 +0200 (CEST)
> From: Visuwesh <visuwesh@tutanota.com>
> Cc: 49931 <49931@debbugs.gnu.org>
> 
> 8 Aug 2021, 12:44 by eliz@gnu.org:
> 
> > In particular, depending on the context of the completion, typing
> > more stuff after selecting a candidate is what is actually needed, so
> > ignoring that would break valid use cases.
> 
> Indeed, this makes sense when selecting a candidate that does not exit
> the minibuffer, like `find-file'.  I, for one, do not think that the
> current behaviour of `choose-completion' wherein it completely ignores
> whatever typed after the creation of the *Completions* buffer is
> unexpected when it comes to commands like `describe-function' which
> exits the minibuffer upon selecting the candidate.

Even though the command exits the minibuffer, the stuff you typed
before selection shouldn't necessarily be ignored, since you could be
completing on stuff that doesn't yield complete function names.

> > Therefore I think we will have to agree to disagree on this one. I
> > see no bug in the behavior you described. If it looks misleading to
> > you, you will have to get used to it.
> 
> If the above still does not convince you, then we will have to agree
> to disagree.

Yes.





  reply	other threads:[~2021-08-08  8:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-07 17:20 bug#49931: 28.0.50; `choose-completion' submits incorrect string when minibuffer content changes after creation of the *Completions* buffer Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-08  5:14 ` Eli Zaretskii
2021-08-08  7:02   ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-08  7:14     ` Eli Zaretskii
2021-08-08  7:31       ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-08  8:19         ` Eli Zaretskii [this message]
2021-08-10  7:07 ` Juri Linkov
2021-08-10  9:00   ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-12 18:49   ` Juri Linkov
2022-04-05 18:54     ` Juri Linkov

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=83mtpsgxhd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=49931@debbugs.gnu.org \
    --cc=visuwesh@tutanota.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).