From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: master 431f8ff1e38: * lisp/imenu.el: Support more values for imenu-flatten (bug#70846) Date: Mon, 20 May 2024 09:46:10 +0300 Organization: LINKOV.NET Message-ID: <865xv9ugjx.fsf@mail.linkov.net> References: <171558357066.26019.9766615061719600757@vcs2.savannah.gnu.org> <20240513065931.0D83AC12C31@vcs2.savannah.gnu.org> <86v83hwxjs.fsf@mail.linkov.net> <86ikzhq6ja.fsf@mail.linkov.net> <86o798x5hz.fsf@gnu.org> <86bk572e6a.fsf@mail.linkov.net> <861q62pb8y.fsf@mail.linkov.net> <864jayjd8u.fsf@gnu.org> <86le49ymsl.fsf@mail.linkov.net> <86msoo4cf3.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37792"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: Eli Zaretskii , me@eshelyaron.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 20 08:52:10 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1s8wsU-0009br-PB for ged-emacs-devel@m.gmane-mx.org; Mon, 20 May 2024 08:52:10 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s8wrr-0003az-F8; Mon, 20 May 2024 02:51:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s8wqf-0003M3-Fh for emacs-devel@gnu.org; Mon, 20 May 2024 02:50:17 -0400 Original-Received: from relay5-d.mail.gandi.net ([2001:4b98:dc4:8::225]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s8wqb-0008TL-Gh; Mon, 20 May 2024 02:50:16 -0400 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 8E18A1C0002; Mon, 20 May 2024 06:50:07 +0000 (UTC) In-Reply-To: (Stefan Monnier's message of "Sat, 18 May 2024 11:12:06 -0400") X-GND-Sasl: juri@linkov.net Received-SPF: pass client-ip=2001:4b98:dc4:8::225; envelope-from=juri@linkov.net; helo=relay5-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:319395 Archived-At: --=-=-= Content-Type: text/plain >> because when `completing-read-default` calls `read-from-minibuffer`, >> it uses the value of `minibuffer-allow-text-properties` from >> the original buffer: >> >> val = read_minibuf (keymap, initial_contents, prompt, >> !NILP (read), >> histvar, histpos, default_value, >> minibuffer_allow_text_properties, >> !NILP (inherit_input_method)); > > Damn! This is too bad: a buffer-local setting of > `minibuffer_allow_text_properties` can basically never be used then, > because it's read from the wrong buffer. > >> Then `read_minibuf` uses its argument `allow_props`: >> >> if (allow_props) >> val = Fminibuffer_contents (); >> else >> val = Fminibuffer_contents_no_properties (); >> >> Maybe it could use `minibuffer-allow-text-properties` directly here? > > Indeed: since a buffer-local setting can't work, we know that all > callers must use a plain let-binding so the binding will be active > during the whole minibuffer session, so we may as well read it at the > end (in the minibuffer) rather than at the beginning (in the > `minibuffer--original-buffer`). Ok, then here is a complete patch with documentation updates where many documentation changes are fixing the documentation to describe the current behavior existed even before applying these code changes. > PS: Git shows that `minibuffer-allow-text-properties` was introduced > eons ago (and basically never touched since then, even the docstring is > mostly unchanged). And Grep shows it's not used very often (and > several of those uses are around `completing-read`). > Funnily enough, one of the few uses in our tree binds it to nil, > I wonder why that was needed. Probably the nil let-binding was intended to negate the effect of a non-nil let-binding higher in the stack of recursive minibuffers. So this is another reason to prefer buffer-local settings. --=-=-= Content-Type: text/x-diff Content-Disposition: inline; filename=minibuffer_allow_text_properties.patch diff --git a/etc/NEWS b/etc/NEWS index 4e52d4dccb2..cefbc0eb938 100644 --- a/etc/NEWS +++ b/etc/NEWS @@ -2033,6 +2033,17 @@ UTF-8 byte sequence, and the optional parameter MULTIBYTE of 'dbus-string-to-byte-array' should be a regular Lisp string, not a unibyte string. ++++ +** 'minibuffer-allow-text-properties' now can be set buffer-local. +'read-from-minibuffer' and functions that use it can take the +buffer-local value from the minibuffer. + ++++ +** 'minibuffer-allow-text-properties' also affects completions. +When it has a non-nil value, then completion functions like +'completing-read' don't discard text properties from the returned +completion candidate. + * Lisp Changes in Emacs 30.1 diff --git a/doc/lispref/minibuf.texi b/doc/lispref/minibuf.texi index 8f2d0d702f9..af5552851e2 100644 --- a/doc/lispref/minibuf.texi +++ b/doc/lispref/minibuf.texi @@ -185,7 +185,8 @@ Text from Minibuffer History}. If the variable @code{minibuffer-allow-text-properties} is -non-@code{nil}, then the string that is returned includes whatever text +non-@code{nil}, either let-bound or buffer-local in the minibuffer, +then the string that is returned includes whatever text properties were present in the minibuffer. Otherwise all the text properties are stripped when the value is returned. (By default this variable is @code{nil}.) @@ -352,28 +353,27 @@ Text from Minibuffer @defvar minibuffer-allow-text-properties If this variable is @code{nil}, the default, then -@code{read-from-minibuffer} and @code{read-string} strip all text +@code{read-from-minibuffer}, @code{read-string}, and all +functions that do minibuffer input with completion strip all text properties from the minibuffer input before returning it. However, -@code{read-no-blanks-input} (see below), as well as @code{read-minibuffer} and related functions (@pxref{Object from -Minibuffer,, Reading Lisp Objects With the Minibuffer}), and all -functions that do minibuffer input with completion, remove the +Minibuffer,, Reading Lisp Objects With the Minibuffer}), remove the @code{face} property unconditionally, regardless of the value of this variable. -If this variable is non-@code{nil}, most text properties on strings -from the completion table are preserved---but only on the part of the -strings that were completed. +If this variable is non-@code{nil}, either let-bound or buffer-local in +the minibuffer, most text properties on strings from the completion +table are preserved---but only on the part of the strings that were +completed. @lisp (let ((minibuffer-allow-text-properties t)) (completing-read "String: " (list (propertize "foobar" 'data 'zot)))) -=> #("foobar" 3 6 (data zot)) +=> #("foobar" 0 6 (data zot)) @end lisp In this example, the user typed @samp{foo} and then hit the @kbd{TAB} -key, so the text properties are only preserved on the last three -characters. +key, so the text properties are preserved on all characters. @end defvar @vindex minibuffer-mode-map @@ -433,18 +433,6 @@ Text from Minibuffer keymap as the @var{keymap} argument for that function. Since the keymap @code{minibuffer-local-ns-map} does not rebind @kbd{C-q}, it @emph{is} possible to put a space into the string, by quoting it. - -This function discards text properties, regardless of the value of -@code{minibuffer-allow-text-properties}. - -@smallexample -@group -(read-no-blanks-input @var{prompt} @var{initial}) -@equiv{} -(let (minibuffer-allow-text-properties) - (read-from-minibuffer @var{prompt} @var{initial} minibuffer-local-ns-map)) -@end group -@end smallexample @end defun @c Slightly unfortunate name, suggesting it might be related to the diff --git a/src/minibuf.c b/src/minibuf.c index 9c1c86680d4..f2a76086361 100644 --- a/src/minibuf.c +++ b/src/minibuf.c @@ -563,7 +563,8 @@ DEFUN ("minibuffer-contents-no-properties", Fminibuffer_contents_no_properties, DEFALT specifies the default value for the sake of history commands. - If ALLOW_PROPS, do not throw away text properties. + If ALLOW_PROPS or `minibuffer-allow-text-properties' is non-nil, + do not throw away text properties. if INHERIT_INPUT_METHOD, the minibuffer inherits the current input method. */ @@ -928,7 +929,7 @@ read_minibuf (Lisp_Object map, Lisp_Object initial, Lisp_Object prompt, /* Make minibuffer contents into a string. */ Fset_buffer (minibuffer); - if (allow_props) + if (allow_props || minibuffer_allow_text_properties) val = Fminibuffer_contents (); else val = Fminibuffer_contents_no_properties (); @@ -1321,7 +1322,8 @@ DEFUN ("read-from-minibuffer", Fread_from_minibuffer, Seventh arg INHERIT-INPUT-METHOD, if non-nil, means the minibuffer inherits the current input method and the setting of `enable-multibyte-characters'. -If the variable `minibuffer-allow-text-properties' is non-nil, +If the variable `minibuffer-allow-text-properties' is non-nil + (either let-bound or buffer-local in the minibuffer), then the string which is returned includes whatever text properties were present in the minibuffer. Otherwise the value has no text properties. @@ -2464,9 +2466,10 @@ syms_of_minibuf (void) DEFVAR_BOOL ("minibuffer-allow-text-properties", minibuffer_allow_text_properties, doc: /* Non-nil means `read-from-minibuffer' should not discard text properties. -This also affects `read-string', but it does not affect `read-minibuffer', -`read-no-blanks-input', or any of the functions that do minibuffer input -with completion; they always discard text properties. */); +The value could be let-bound or buffer-local in the minibuffer. +This also affects `read-string', or any of the functions that do +minibuffer input with completion, but it does not affect `read-minibuffer' +that always discards text properties. */); minibuffer_allow_text_properties = 0; DEFVAR_LISP ("minibuffer-prompt-properties", Vminibuffer_prompt_properties, diff --git a/lisp/simple.el b/lisp/simple.el index bcd26da13ed..8fbfa683e97 100644 --- a/lisp/simple.el +++ b/lisp/simple.el @@ -10127,9 +10127,9 @@ choose-completion (completion-no-auto-exit (if no-exit t completion-no-auto-exit)) (choice (if choose-completion-deselect-if-after - (if-let ((str (get-text-property (posn-point (event-start event)) 'completion--string))) - (substring-no-properties str) - (error "No completion here")) + (or (get-text-property (posn-point (event-start event)) + 'completion--string) + (error "No completion here")) (save-excursion (goto-char (posn-point (event-start event))) (let (beg) @@ -10144,8 +10144,7 @@ choose-completion (setq beg (or (previous-single-property-change beg 'completion--string) beg)) - (substring-no-properties - (get-text-property beg 'completion--string))))))) + (get-text-property beg 'completion--string)))))) (unless (buffer-live-p buffer) (error "Destination buffer is dead")) diff --git a/lisp/imenu.el b/lisp/imenu.el index ea097f5da3a..93d84106ec1 100644 --- a/lisp/imenu.el +++ b/lisp/imenu.el @@ -752,6 +752,7 @@ imenu--completion-buffer ;; Display the completion buffer. (minibuffer-with-setup-hook (lambda () + (setq-local minibuffer-allow-text-properties t) (setq-local completion-extra-properties `( :category imenu ,@(when (eq imenu-flatten 'annotation) @@ -765,10 +766,12 @@ imenu--completion-buffer nil t nil 'imenu--history-list name))) (when (stringp name) - (setq choice (assoc name prepared-index-alist)) - (if (imenu--subalist-p choice) - (imenu--completion-buffer (cdr choice) prompt) - choice)))) + (or (get-text-property 0 'imenu-choice name) + (progn + (setq choice (assoc name prepared-index-alist)) + (if (imenu--subalist-p choice) + (imenu--completion-buffer (cdr choice) prompt) + choice)))))) (defun imenu--mouse-menu (index-alist event &optional title) "Let the user select from a buffer index from a mouse menu. @@ -798,7 +801,9 @@ imenu--flatten-index-alist (new-prefix (and concat-names (if prefix (concat prefix imenu-level-separator name) - name)))) + (if (eq imenu-flatten 'annotation) + (propertize name 'imenu-choice item) + name))))) (cond ((not (imenu--subalist-p item)) (list (cons (if (and (eq imenu-flatten 'annotation) prefix) --=-=-=--