From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Wanrong Lin <wrglin@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
39484@debbugs.gnu.org
Subject: bug#39484: 26.3; try-completion bug
Date: Sat, 23 Apr 2022 15:17:10 +0200 [thread overview]
Message-ID: <877d7gszvt.fsf@gnus.org> (raw)
In-Reply-To: <jwvo8kmh18t.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 28 Oct 2020 10:45:07 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The current design is trying to be conservative, in the sense that it
> tries to avoid returning a poor result, at the cost of sometimes failing
> to return a better result. It does it by refraining from mix-and-match:
> either the whole result comes from the user input or the whole result
> comes from *one* of the candidates.
I've now mentioned something like this in the doc string of the function
in Emacs 29.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-04-23 13:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 15:44 bug#39484: 26.3; try-completion bug Wanrong Lin
2020-10-27 18:42 ` Lars Ingebrigtsen
2020-10-27 19:08 ` Andreas Schwab
2020-10-27 19:17 ` Lars Ingebrigtsen
2020-10-27 20:17 ` Wanrong Lin
2020-10-27 20:28 ` Andreas Schwab
2020-10-27 20:44 ` Wanrong Lin
2020-10-27 21:21 ` Andreas Schwab
2020-10-28 0:44 ` Wanrong Lin
2020-10-28 0:47 ` Wanrong Lin
2020-10-28 0:57 ` Wanrong Lin
2020-10-28 7:51 ` Andreas Schwab
2020-10-28 9:35 ` Lars Ingebrigtsen
2020-10-28 9:42 ` Andreas Schwab
2020-10-28 9:50 ` Lars Ingebrigtsen
2020-10-28 9:56 ` Andreas Schwab
2020-10-28 11:16 ` Lars Ingebrigtsen
2020-10-28 11:44 ` Andreas Schwab
2020-10-28 12:59 ` Wanrong Lin
2020-10-28 14:45 ` Stefan Monnier
2020-10-28 15:47 ` Wanrong Lin
2020-10-28 16:34 ` Stefan Monnier
2022-04-23 13:17 ` Lars Ingebrigtsen [this message]
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=877d7gszvt.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39484@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
--cc=wrglin@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).