From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: me@eshelyaron.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: master 431f8ff1e38: * lisp/imenu.el: Support more values for imenu-flatten (bug#70846)
Date: Fri, 17 May 2024 09:48:42 +0300 [thread overview]
Message-ID: <86le49ymsl.fsf@mail.linkov.net> (raw)
In-Reply-To: <864jayjd8u.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 May 2024 12:51:45 +0300")
>> > Note that when minibuffer-allow-text-properties is non-nil, you can
>> > already get the same original text properties from completing-read if
>> > you "select" your candidate by cycling, since that doesn't go through
>> > choose-completion which strips text properties. It feels a bit
>> > surprising to have this separate variable that affects one kind of
>> > selection ("choosing") and not other kinds ("cycling", "expanding").
>> > IMO, it'd be better, if possible, to just cease stripping text
>> > properties in choose-completion altogether. Note that choose-completion
>> > calls completion--replace to do the actual insertion, and that function
>> > already respects minibuffer-allow-text-properties.
>>
>> I agree that a new variable is unnecessary, so it would be better just
>> to preserve text properties in choose-completion unconditionally.
>> Unless there are objections this looks like the right thing to do.
>
> Does that mean completion candidates will always appear with their
> original text properties? If so, I don't think it's TRT in all cases.
> Whether it's TRT depends on the use case, so a variable definitely
> seems like the way to go.
Like Eshel noted, the text properties are already discarded from the completion
candidate by default since the default value of minibuffer-allow-text-properties
is nil.
> However, AFAIU Eshel didn't mean to say we should always preserve text
> properties, he said we already have a variable to indicate whether
> properties are to be preserved. So the issue, AFAIU, is whether we
> need _another_ variable, or should use a single one in both cases.
Indeed, the existing variable minibuffer-allow-text-properties
can be used for both cases. So when choose-completion will preserve
text properties, then completion--replace will decide whether to
discard them based on the value of minibuffer-allow-text-properties.
But there is another separate problem: Eshel asked to replace
let-bindings around completing-read with the minibuffer-local value
of minibuffer-allow-text-properties. However, this is impossible to do
because read-from-minibuffer called from completing-read can't use
a minibuffer-local value of minibuffer-allow-text-properties.
next prev parent reply other threads:[~2024-05-17 6:48 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 [this message]
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 ` master 431f8ff1e38: * lisp/imenu.el: Support more values for imenu-flatten (bug#70846) Stefan Monnier
2024-08-20 17:51 ` 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=86le49ymsl.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@eshelyaron.com \
--cc=monnier@iro.umontreal.ca \
/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).