From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@linkov.net>
Cc: Eshel Yaron <me@eshelyaron.com>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: master 431f8ff1e38: * lisp/imenu.el: Support more values for imenu-flatten (bug#70846)
Date: Tue, 13 Aug 2024 21:41:14 -0400 [thread overview]
Message-ID: <jwvle0zriiz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86msmj9adm.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 14 Jul 2024 20:00:37 +0300")
>> What I would suggest is to ensure completion candidates are unambiguous
>> as strings rather than relying on text properties. Namely:
> Unfortunately, that'd be a step back. Maybe at least we could document
> limitations that annotations work only by selection.
How about we make them unambiguous by adding text *at the end* (and
only if there's ambiguity)?
The completion code assumes in all kinds of places that the same text
means the same thing, so using the same text to mean different
completion choices will get you in trouble in all kinds of corner (and
not so corner) cases.
Stefan
next prev parent reply other threads:[~2024-08-14 1:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171558357066.26019.9766615061719600757@vcs2.savannah.gnu.org>
[not found] ` <20240513065931.0D83AC12C31@vcs2.savannah.gnu.org>
2024-05-13 9:22 ` master 431f8ff1e38: * lisp/imenu.el: Support more values for imenu-flatten (bug#70846) Eshel Yaron
2024-05-13 16:30 ` Juri Linkov
2024-05-14 6:08 ` Juri Linkov
2024-05-14 6:38 ` Eli Zaretskii
2024-05-14 13:10 ` Stefan Monnier
2024-05-14 16:46 ` Juri Linkov
2024-05-14 20:58 ` Daniel Mendler via Emacs development discussions.
2024-05-14 23:26 ` FW: [External] : " Drew Adams
2024-05-15 16:51 ` Juri Linkov
2024-05-15 18:03 ` Eli Zaretskii
2024-05-15 18:30 ` Eshel Yaron
2024-05-16 6:08 ` Juri Linkov
2024-05-16 9:51 ` Eli Zaretskii
2024-05-17 6:48 ` Juri Linkov
2024-05-17 15:36 ` Stefan Monnier
2024-05-17 16:43 ` Juri Linkov
2024-05-18 15:12 ` Stefan Monnier
2024-05-20 6:46 ` Juri Linkov
2024-05-27 18:18 ` Juri Linkov
2024-07-14 6:28 ` Eshel Yaron
2024-07-14 6:53 ` Juri Linkov
2024-07-14 10:55 ` Eshel Yaron
2024-07-14 17:00 ` Juri Linkov
2024-07-16 6:57 ` Eshel Yaron
2024-08-07 6:51 ` Juri Linkov
2024-08-07 8:33 ` Eshel Yaron
2024-08-07 16:46 ` Juri Linkov
2024-08-09 6:59 ` Juri Linkov
2024-08-09 7:11 ` Eli Zaretskii
2024-08-09 16:10 ` Juri Linkov
2024-08-09 17:43 ` Eli Zaretskii
2024-08-07 6:56 ` Completions group metadata [was: master 431f8ff1e38: * lisp/imenu.el: Support more values for imenu-flatten (bug#70846)] Juri Linkov
2024-08-09 16:16 ` Completions group metadata [ Juri Linkov
2024-08-14 1:41 ` Stefan Monnier [this message]
2024-08-20 17:51 ` master 431f8ff1e38: * lisp/imenu.el: Support more values for imenu-flatten (bug#70846) Juri Linkov
2024-05-14 15:26 ` [External] : " 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
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=jwvle0zriiz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=me@eshelyaron.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).