From: Stefan Kangas <stefan@marxist.se>
To: Juri Linkov <juri@linkov.net>
Cc: 50935@debbugs.gnu.org
Subject: bug#50935: minibuffer-electric-default-mode interface
Date: Sun, 3 Oct 2021 01:14:59 +0200 [thread overview]
Message-ID: <CADwFkmnDpfcJzJX70P4qg4iuwHKLFwLw6gCAB9t=6FRwgDz0sA@mail.gmail.com> (raw)
In-Reply-To: <87k0ixq6wt.fsf@mail.linkov.net>
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.
next prev parent reply other threads:[~2021-10-02 23:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmnDpfcJzJX70P4qg4iuwHKLFwLw6gCAB9t=6FRwgDz0sA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=50935@debbugs.gnu.org \
--cc=juri@linkov.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.