* bug#50935: minibuffer-electric-default-mode interface
@ 2021-10-01 11:43 Stefan Kangas
2021-10-02 19:15 ` Juri Linkov
0 siblings, 1 reply; 14+ messages in thread
From: Stefan Kangas @ 2021-10-01 11:43 UTC (permalink / raw)
To: 50935
In (info "(emacs) Basic Minibuffer"), I see:
if you change the variable ‘minibuffer-eldef-shorten-default’ to a
non-‘nil’ value, the default argument is displayed as ‘[DEFAULT-ARG]’
instead of ‘(default DEFAULT-ARG)’, saving some screen space. To
enable this minor mode, type ‘M-x minibuffer-electric-default-mode’.
But when I run "emacs -Q", I can't customize
'minibuffer-eldef-shorten-default', and this has no effect:
0. emacs -Q
1. (setq minibuffer-eldef-shorten-default t)
2. M-x set-fill-column RET
I still see "(default 0)". Only if I run 'M-x
minibuffer-electric-default-mode' does this change to "[0]". So the
above text seems wrong.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-01 11:43 bug#50935: minibuffer-electric-default-mode interface Stefan Kangas
@ 2021-10-02 19:15 ` Juri Linkov
2021-10-02 23:14 ` Stefan Kangas
2021-10-03 11:51 ` Eli Zaretskii
0 siblings, 2 replies; 14+ messages in thread
From: Juri Linkov @ 2021-10-02 19:15 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 50935
> In (info "(emacs) Basic Minibuffer"), I see:
>
> if you change the variable ‘minibuffer-eldef-shorten-default’ to a
> non-‘nil’ value, the default argument is displayed as ‘[DEFAULT-ARG]’
> instead of ‘(default DEFAULT-ARG)’, saving some screen space. To
> enable this minor mode, type ‘M-x minibuffer-electric-default-mode’.
While I don't know how to fix this issue, I have to note that
this Info node should also mention that minibuffer-electric-default-mode
is now obsoleted by the new user option minibuffer-default-prompt-format.
The only problem is that currently not all prompts use 'format-prompt'.
Maybe this should be added to etc/TODO?
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-02 19:15 ` Juri Linkov
@ 2021-10-02 23:14 ` Stefan Kangas
2021-10-03 16:54 ` Juri Linkov
2021-10-03 11:51 ` Eli Zaretskii
1 sibling, 1 reply; 14+ messages in thread
From: Stefan Kangas @ 2021-10-02 23:14 UTC (permalink / raw)
To: Juri Linkov; +Cc: 50935
Juri Linkov <juri@linkov.net> writes:
> > In (info "(emacs) Basic Minibuffer"), I see:
> >
> > if you change the variable ‘minibuffer-eldef-shorten-default’ to a
> > non-‘nil’ value, the default argument is displayed as ‘[DEFAULT-ARG]’
> > instead of ‘(default DEFAULT-ARG)’, saving some screen space. To
> > enable this minor mode, type ‘M-x minibuffer-electric-default-mode’.
>
> While I don't know how to fix this issue, I have to note that
> this Info node should also mention that minibuffer-electric-default-mode
> is now obsoleted by the new user option minibuffer-default-prompt-format.
Hmm, shouldn't the info node then just mention
'minibuffer-default-prompt-format' instead, and only that? I don't
think we mention obsolete things if we can avoid it, do we?
Also, should 'minibuffer-electric-default-mode' be declared obsolete,
or is it too early for that?
> The only problem is that currently not all prompts use 'format-prompt'.
> Maybe this should be added to etc/TODO?
It can't hurt.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-02 19:15 ` Juri Linkov
2021-10-02 23:14 ` Stefan Kangas
@ 2021-10-03 11:51 ` Eli Zaretskii
1 sibling, 0 replies; 14+ messages in thread
From: Eli Zaretskii @ 2021-10-03 11:51 UTC (permalink / raw)
To: Juri Linkov; +Cc: stefan, 50935
> From: Juri Linkov <juri@linkov.net>
> Date: Sat, 02 Oct 2021 22:15:54 +0300
> Cc: 50935@debbugs.gnu.org
>
> While I don't know how to fix this issue, I have to note that
> this Info node should also mention that minibuffer-electric-default-mode
> is now obsoleted by the new user option minibuffer-default-prompt-format.
> The only problem is that currently not all prompts use 'format-prompt'.
> Maybe this should be added to etc/TODO?
If we haven't yet completed the conversion between the two, I'm not
sure the time is right for us to announce the obsolescence of the old
method, as it is still needed in some situations.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-02 23:14 ` Stefan Kangas
@ 2021-10-03 16:54 ` Juri Linkov
2021-10-04 2:17 ` Stefan Kangas
0 siblings, 1 reply; 14+ messages in thread
From: Juri Linkov @ 2021-10-03 16:54 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 50935
>> While I don't know how to fix this issue, I have to note that
>> this Info node should also mention that minibuffer-electric-default-mode
>> is now obsoleted by the new user option minibuffer-default-prompt-format.
>
> Hmm, shouldn't the info node then just mention
> 'minibuffer-default-prompt-format' instead, and only that? I don't
> think we mention obsolete things if we can avoid it, do we?
>
> Also, should 'minibuffer-electric-default-mode' be declared obsolete,
> or is it too early for that?
It seems it's too early to obsolete it. But maybe still
'minibuffer-default-prompt-format' should be mentioned?
Since it's a user option supporting the same format (but in
a limited set of prompts) as 'minibuffer-electric-default-mode'.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-03 16:54 ` Juri Linkov
@ 2021-10-04 2:17 ` Stefan Kangas
2021-10-04 17:22 ` Juri Linkov
2021-10-05 6:43 ` Juri Linkov
0 siblings, 2 replies; 14+ messages in thread
From: Stefan Kangas @ 2021-10-04 2:17 UTC (permalink / raw)
To: Juri Linkov; +Cc: 50935
Juri Linkov <juri@linkov.net> writes:
> It seems it's too early to obsolete it. But maybe still
> 'minibuffer-default-prompt-format' should be mentioned?
> Since it's a user option supporting the same format (but in
> a limited set of prompts) as 'minibuffer-electric-default-mode'.
I guess we have this problem for many defcustoms, unless they are
autoloaded, so for `minibuffer-eldef-shorten-default' we have that:
- "Setting it to a non-nil value" using setq before the library is
loaded will work.
- "Setting it to a non-nil value" using setq after the library is loaded
will *not* work, you must use customize.
- You can only set it with customize after the library has been loaded.
I think instead of documenting all that, we could just delete the
reference to `minibuffer-eldef-shorten-default' from the manual, as it
is the same thing as `minibuffer-default-prompt-format', just with a
different interface. Of course, the latter is not yet perfect, but
anywhere it isn't, that's just a bug, right? That option would look
like the below diff.
Another option is to just add a reference to
'minibuffer-default-prompt-format' without any deletions, basically
accepting that the text is not perfect and move on.
A third option is to add 'minibuffer-default-prompt-format' on emacs-28,
but make the suggested deletion on master -- which give us more time to
get `minibuffer-default-prompt-format' up to scrap.
Thoughts?
diff --git a/doc/emacs/mini.texi b/doc/emacs/mini.texi
index 6dcee3fa82..2581be30ba 100644
--- a/doc/emacs/mini.texi
+++ b/doc/emacs/mini.texi
@@ -41,11 +41,14 @@ Basic Minibuffer
canceling the command asking for the argument (@pxref{Quitting}).
@cindex default argument
+@vindex minibuffer-default-prompt-format
Sometimes, the prompt shows a @dfn{default argument}, inside
parentheses before the colon. This default will be used as the
argument if you just type @key{RET}. For example, commands that read
buffer names usually show a buffer name as the default; you can type
-@key{RET} to operate on that default buffer.
+@key{RET} to operate on that default buffer. You can customize how
+the default argument is shown with the user option
+@code{minibuffer-default-prompt-format}.
@cindex Minibuffer Electric Default mode
@cindex mode, Minibuffer Electric Default
@@ -55,11 +58,7 @@ Basic Minibuffer
Emacs hides the default argument as soon as you modify the contents of
the minibuffer (since typing @key{RET} would no longer submit that
default). If you ever bring back the original minibuffer text, the
-prompt again shows the default. Furthermore, if you change the
-variable @code{minibuffer-eldef-shorten-default} to a non-@code{nil}
-value, the default argument is displayed as @samp{[@var{default-arg}]}
-instead of @samp{(default @var{default-arg})}, saving some screen
-space. To enable this minor mode, type @kbd{M-x
+prompt again shows the default. To enable this minor mode, type @kbd{M-x
minibuffer-electric-default-mode}.
Since the minibuffer appears in the echo area, it can conflict with
diff --git a/lisp/minibuf-eldef.el b/lisp/minibuf-eldef.el
index f67ec353c8..039d0f8828 100644
--- a/lisp/minibuf-eldef.el
+++ b/lisp/minibuf-eldef.el
@@ -56,7 +56,9 @@ minibuffer-default--in-prompt-regexps
("\\( \\[.*\\]\\):? *\\'" 1))))
(defcustom minibuffer-eldef-shorten-default nil
- "If non-nil, shorten \"(default ...)\" to \"[...]\" in minibuffer prompts."
+ "If non-nil, shorten \"(default ...)\" to \"[...]\" in minibuffer prompts.
+This only takes effect if `minibuffer-electric-default-mode' is
+active."
:set (lambda (symbol value)
(set-default symbol value)
(setq-default minibuffer-default-in-prompt-regexps
@@ -183,7 +185,9 @@ minibuffer-electric-default-mode
the default when it's applicable -- that is, when hitting RET
would yield the default value. If the user modifies the input
such that hitting RET would enter a non-default value, the prompt
-is modified to remove the default indication."
+is modified to remove the default indication.
+
+See also the user option `minibuffer-eldef-shorten-default'."
:global t
:group 'minibuffer
(if minibuffer-electric-default-mode
^ permalink raw reply related [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-04 2:17 ` Stefan Kangas
@ 2021-10-04 17:22 ` Juri Linkov
2021-10-05 16:55 ` Stefan Kangas
2021-10-05 6:43 ` Juri Linkov
1 sibling, 1 reply; 14+ messages in thread
From: Juri Linkov @ 2021-10-04 17:22 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 50935
> I think instead of documenting all that, we could just delete the
> reference to `minibuffer-eldef-shorten-default' from the manual, as it
> is the same thing as `minibuffer-default-prompt-format', just with a
> different interface. Of course, the latter is not yet perfect, but
> anywhere it isn't, that's just a bug, right? That option would look
> like the below diff.
>
> Another option is to just add a reference to
> 'minibuffer-default-prompt-format' without any deletions, basically
> accepting that the text is not perfect and move on.
>
> A third option is to add 'minibuffer-default-prompt-format' on emacs-28,
> but make the suggested deletion on master -- which give us more time to
> get `minibuffer-default-prompt-format' up to scrap.
>
> Thoughts?
I guess the answer depends on the question how many prompts
are already converted to 'minibuffer-default-prompt-format',
and how many remain. I checked a few commands, and noticed
only one command that doesn't use the new format. It's 'M-.'
('xref-find-definitions'). But maybe it can't use the new option
'minibuffer-default-prompt-format' because xref.el should be
available in old versions? Still it could use
(if (boundp 'minibuffer-default-prompt-format) ...
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-04 2:17 ` Stefan Kangas
2021-10-04 17:22 ` Juri Linkov
@ 2021-10-05 6:43 ` Juri Linkov
2021-10-05 14:11 ` Stefan Kangas
1 sibling, 1 reply; 14+ messages in thread
From: Juri Linkov @ 2021-10-05 6:43 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 50935
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
> A third option is to add 'minibuffer-default-prompt-format' on emacs-28,
> but make the suggested deletion on master -- which give us more time to
> get `minibuffer-default-prompt-format' up to scrap.
>
> Thoughts?
Thanks for adding format-prompt to many more prompts. I noticed
that when minibuffer-default-prompt-format is customized to the
recommended format " [%s]", then the prompt of proced-send-signal
is confusing with two pairs of the same brackets:
Send signal [3 processes] [TERM]:
The following patch makes the prompt more readable:
Send signal to 3 processes [TERM]:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: proced-send-signal.patch --]
[-- Type: text/x-diff, Size: 1159 bytes --]
diff --git a/lisp/proced.el b/lisp/proced.el
index 29996068f9..cb66d68302 100644
--- a/lisp/proced.el
+++ b/lisp/proced.el
@@ -1773,7 +1773,7 @@ proced-send-signal
`(:annotation-function
,(lambda (s) (cdr (assoc s proced-signal-list))))))
(proced-with-processes-buffer process-alist
- (list (completing-read (format-prompt "Send signal [%s]"
+ (list (completing-read (format-prompt "Send signal to %s"
"TERM" pnum)
proced-signal-list
nil nil nil nil "TERM")
@@ -1798,7 +1798,7 @@ proced-send-signal
`(:annotation-function
,(lambda (s) (cdr (assoc s proced-signal-list))))))
(proced-with-processes-buffer process-alist
- (setq signal (completing-read (format-prompt "Send signal [%s]"
+ (setq signal (completing-read (format-prompt "Send signal to %s"
"TERM" pnum)
proced-signal-list
nil nil nil nil "TERM"))))))
^ permalink raw reply related [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-05 6:43 ` Juri Linkov
@ 2021-10-05 14:11 ` Stefan Kangas
2021-10-05 15:52 ` Eli Zaretskii
2021-10-05 16:42 ` Juri Linkov
0 siblings, 2 replies; 14+ messages in thread
From: Stefan Kangas @ 2021-10-05 14:11 UTC (permalink / raw)
To: Juri Linkov; +Cc: 50935
Juri Linkov <juri@linkov.net> writes:
> The following patch makes the prompt more readable:
>
> Send signal to 3 processes [TERM]:
Sounds good to me.
BTW, did you send the right patch? I can't see the word "processes"
below.
> diff --git a/lisp/proced.el b/lisp/proced.el
> index 29996068f9..cb66d68302 100644
> --- a/lisp/proced.el
> +++ b/lisp/proced.el
> @@ -1773,7 +1773,7 @@ proced-send-signal
> `(:annotation-function
> ,(lambda (s) (cdr (assoc s proced-signal-list))))))
> (proced-with-processes-buffer process-alist
> - (list (completing-read (format-prompt "Send signal [%s]"
> + (list (completing-read (format-prompt "Send signal to %s"
> "TERM" pnum)
> proced-signal-list
> nil nil nil nil "TERM")
> @@ -1798,7 +1798,7 @@ proced-send-signal
> `(:annotation-function
> ,(lambda (s) (cdr (assoc s proced-signal-list))))))
> (proced-with-processes-buffer process-alist
> - (setq signal (completing-read (format-prompt "Send signal [%s]"
> + (setq signal (completing-read (format-prompt "Send signal to %s"
> "TERM" pnum)
> proced-signal-list
> nil nil nil nil "TERM"))))))
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-05 14:11 ` Stefan Kangas
@ 2021-10-05 15:52 ` Eli Zaretskii
2021-10-05 16:46 ` Juri Linkov
2021-10-05 16:42 ` Juri Linkov
1 sibling, 1 reply; 14+ messages in thread
From: Eli Zaretskii @ 2021-10-05 15:52 UTC (permalink / raw)
To: Stefan Kangas; +Cc: juri, 50935
> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 5 Oct 2021 10:11:11 -0400
> Cc: 50935@debbugs.gnu.org
>
> Juri Linkov <juri@linkov.net> writes:
>
> > The following patch makes the prompt more readable:
> >
> > Send signal to 3 processes [TERM]:
>
> Sounds good to me.
It could be confusing. Previously, the prompt was
Send signal [TERM]
So it was much more clear that "TERM" refers to "signal" and vice
versa. Now we have "3 processes" in the way, and someone could think
"TERM" refers to the processes or something.
How about this instead:
Signal N processes with [SIGTERM]:
Note that I deliberately added the "SIG" part so that it would be more
clear this is the name of a signal.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-05 14:11 ` Stefan Kangas
2021-10-05 15:52 ` Eli Zaretskii
@ 2021-10-05 16:42 ` Juri Linkov
1 sibling, 0 replies; 14+ messages in thread
From: Juri Linkov @ 2021-10-05 16:42 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 50935
>> The following patch makes the prompt more readable:
>>
>> Send signal to 3 processes [TERM]:
>
> Sounds good to me.
>
> BTW, did you send the right patch? I can't see the word "processes"
> below.
You can see the word "processes" in the source code
outside of the patch diff context ;-)
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-05 15:52 ` Eli Zaretskii
@ 2021-10-05 16:46 ` Juri Linkov
0 siblings, 0 replies; 14+ messages in thread
From: Juri Linkov @ 2021-10-05 16:46 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: Stefan Kangas, 50935
>> > The following patch makes the prompt more readable:
>> >
>> > Send signal to 3 processes [TERM]:
>>
>> Sounds good to me.
>
> It could be confusing. Previously, the prompt was
>
> Send signal [TERM]
The previous prompt was:
Send signal [3 processes] (default TERM):
or with customized minibuffer-default-prompt-format:
Send signal [3 processes] [TERM]:
This was too confusing.
> So it was much more clear that "TERM" refers to "signal" and vice
> versa. Now we have "3 processes" in the way, and someone could think
> "TERM" refers to the processes or something.
>
> How about this instead:
>
> Signal N processes with [SIGTERM]:
>
> Note that I deliberately added the "SIG" part so that it would be more
> clear this is the name of a signal.
Sorry, the phrase "Signal N processes" is too difficult to comprehend -
it's diffucult to see that "signal" is a verb here.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-04 17:22 ` Juri Linkov
@ 2021-10-05 16:55 ` Stefan Kangas
2022-09-02 12:51 ` Lars Ingebrigtsen
0 siblings, 1 reply; 14+ messages in thread
From: Stefan Kangas @ 2021-10-05 16:55 UTC (permalink / raw)
To: Juri Linkov; +Cc: 50935
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
tags 50935 + patch
thanks
Juri Linkov <juri@linkov.net> writes:
>> A third option is to add 'minibuffer-default-prompt-format' on emacs-28,
>> but make the suggested deletion on master -- which give us more time to
>> get `minibuffer-default-prompt-format' up to scrap.
>
> I guess the answer depends on the question how many prompts
> are already converted to 'minibuffer-default-prompt-format',
> and how many remain. I checked a few commands, and noticed
> only one command that doesn't use the new format. It's 'M-.'
> ('xref-find-definitions'). But maybe it can't use the new option
> 'minibuffer-default-prompt-format' because xref.el should be
> available in old versions? Still it could use
>
> (if (boundp 'minibuffer-default-prompt-format) ...
I've now updated any prompt I could find to use `format-prompt' (by
grepping for " (default "). Maybe I've missed one or two, but that
should mean that that the overwhelming majority of our prompts now
respect `minibuffer-default-prompt-format'. See commit 6640942221.
With that, I think the option `minibuffer-eldef-shorten-default' should
be declared obsolete, as in the attached patch, and consequently removed
from the manual. This change should go to master, of course.
The command `minibuffer-electric-default-mode' shouldn't be declared
obsolete as it does something different.
[-- Attachment #2: 0001-Make-minibuffer-eldef-shorten-default-obsolete.patch --]
[-- Type: text/x-diff, Size: 2543 bytes --]
From 2aa7838e263f8645b1142554a8df164210b35989 Mon Sep 17 00:00:00 2001
From: Stefan Kangas <stefan@marxist.se>
Date: Tue, 5 Oct 2021 18:37:30 +0200
Subject: [PATCH] Make minibuffer-eldef-shorten-default obsolete
* lisp/minibuf-eldef.el (minibuffer-eldef-shorten-default): Make
variable obsolete in favor of 'minibuffer-default-prompt-format'.
* doc/emacs/mini.texi (Basic Minibuffer): Delete above obsolete
variable.
---
doc/emacs/mini.texi | 8 ++------
etc/NEWS | 6 ++++++
lisp/minibuf-eldef.el | 2 ++
3 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/doc/emacs/mini.texi b/doc/emacs/mini.texi
index b0f6e424a7..d764352998 100644
--- a/doc/emacs/mini.texi
+++ b/doc/emacs/mini.texi
@@ -58,12 +58,8 @@ Basic Minibuffer
Emacs hides the default argument as soon as you modify the contents of
the minibuffer (since typing @key{RET} would no longer submit that
default). If you ever bring back the original minibuffer text, the
-prompt again shows the default. Furthermore, if you change the
-variable @code{minibuffer-eldef-shorten-default} to a non-@code{nil}
-value, the default argument is displayed as @samp{[@var{default-arg}]}
-instead of @samp{(default @var{default-arg})}, saving some screen
-space. To enable this minor mode, type @kbd{M-x
-minibuffer-electric-default-mode}.
+prompt again shows the default. To enable this minor mode, type
+@kbd{M-x minibuffer-electric-default-mode}.
Since the minibuffer appears in the echo area, it can conflict with
other uses of the echo area. If an error message or an informative
diff --git a/etc/NEWS b/etc/NEWS
index e9fcfba425..79cca4b4ef 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -98,6 +98,12 @@ also handle ANSI codes for faint, italic and blinking text, displaying
it with new 'ansi-term-faint/italic/slow-blinking/fast-blinking'
faces.
+** Miscellaneous
+
++++
+*** User option 'minibuffer-eldef-shorten-default' is now obsolete.
+Customize the user option 'minibuffer-default-prompt-format' instead.
+
\f
* New Modes and Packages in Emacs 29.1
diff --git a/lisp/minibuf-eldef.el b/lisp/minibuf-eldef.el
index f67ec353c8..c1a4443057 100644
--- a/lisp/minibuf-eldef.el
+++ b/lisp/minibuf-eldef.el
@@ -64,6 +64,8 @@ minibuffer-eldef-shorten-default
:type 'boolean
:group 'minibuffer
:version "24.3")
+(make-obsolete-variable 'minibuffer-eldef-shorten-default
+ 'minibuffer-default-prompt-format "29.1")
(defvar minibuffer-default-in-prompt-regexps
(minibuffer-default--in-prompt-regexps)
--
2.30.2
^ permalink raw reply related [flat|nested] 14+ messages in thread
* bug#50935: minibuffer-electric-default-mode interface
2021-10-05 16:55 ` Stefan Kangas
@ 2022-09-02 12:51 ` Lars Ingebrigtsen
0 siblings, 0 replies; 14+ messages in thread
From: Lars Ingebrigtsen @ 2022-09-02 12:51 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 50935, Juri Linkov
Stefan Kangas <stefan@marxist.se> writes:
> I've now updated any prompt I could find to use `format-prompt' (by
> grepping for " (default "). Maybe I've missed one or two, but that
> should mean that that the overwhelming majority of our prompts now
> respect `minibuffer-default-prompt-format'. See commit 6640942221.
>
> With that, I think the option `minibuffer-eldef-shorten-default' should
> be declared obsolete, as in the attached patch, and consequently removed
> from the manual. This change should go to master, of course.
>
> The command `minibuffer-electric-default-mode' shouldn't be declared
> obsolete as it does something different.
Makes sense to me, so I've now pushed this to Emacs 29 and am closing
this bug report.
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2022-09-02 12:51 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-01 11:43 bug#50935: minibuffer-electric-default-mode interface Stefan Kangas
2021-10-02 19:15 ` Juri Linkov
2021-10-02 23:14 ` Stefan Kangas
2021-10-03 16:54 ` Juri Linkov
2021-10-04 2:17 ` Stefan Kangas
2021-10-04 17:22 ` Juri Linkov
2021-10-05 16:55 ` Stefan Kangas
2022-09-02 12:51 ` Lars Ingebrigtsen
2021-10-05 6:43 ` Juri Linkov
2021-10-05 14:11 ` Stefan Kangas
2021-10-05 15:52 ` Eli Zaretskii
2021-10-05 16:46 ` Juri Linkov
2021-10-05 16:42 ` Juri Linkov
2021-10-03 11:51 ` Eli Zaretskii
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).