From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Felician Nemeth <felician.nemeth@gmail.com>
Cc: "47215@debbugs.gnu.org" <47215@debbugs.gnu.org>
Subject: bug#47215: [External] : bug#47215: 28.0.50; Let M-x switch between M-x and M-X
Date: Sun, 11 Apr 2021 18:29:05 +0000 [thread overview]
Message-ID: <SA2PR10MB4474E905A0862AF27289C3EEF3719@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87k0p8206f.fsf@gnus.org>
> > Finally, the docstring says initial-input is deprecated.
>
> I think this use case demonstrates that perhaps we should slightly
> un-deprecate initial-input -- instead of deprecating it, we could
> instead just discourage the usage.
It never should have been deprecated - quite unwise.
Arguments against deprecation went unheeded/ignored.
___
The Icicles doc for `completing-read' has always said:
If INITIAL-INPUT is non-nil, insert it in the minibuffer initially,
with point positioned at the end. If it is (STRING . POSITION), the
initial input is STRING, but point is placed at zero-indexed position
POSITION in STRING. (This is different from `read-from-minibuffer'
and related functions, which use one-indexing for POSITION.)
INITIAL-INPUT is considered deprecated by vanilla Emacs, but not by
Icicles. If INITIAL-INPUT is nil and DEF is non-nil, the user can use
`next-history-element' to yank DEF into the minibuffer.
___
As for your `M-x' changes and the addition of `M-X':
they too aren't positive, IMO, but I'll leave it to
time and others for that to be realized. (I already
mentioned better approaches in the "Smarter M-x"
thread.)
next prev parent reply other threads:[~2021-04-11 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 17:56 bug#47215: 28.0.50; Let M-x switch between M-x and M-X Felician Nemeth
2021-03-18 5:08 ` Lars Ingebrigtsen
2021-04-04 17:51 ` Felician Nemeth
2021-04-04 19:52 ` Lars Ingebrigtsen
2021-04-10 17:56 ` Felician Nemeth
2021-04-11 17:36 ` Lars Ingebrigtsen
2021-04-11 18:29 ` Drew Adams [this message]
2022-06-24 18:18 ` Lars Ingebrigtsen
2022-06-24 18:55 ` Juri Linkov
2022-06-24 19:00 ` Lars Ingebrigtsen
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=SA2PR10MB4474E905A0862AF27289C3EEF3719@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=47215@debbugs.gnu.org \
--cc=felician.nemeth@gmail.com \
--cc=larsi@gnus.org \
/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).