unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Lars Ingebrigtsen" <larsi@gnus.org>,
	"Codruț Constantin Gușoi" <mail@codrut.pro>
Cc: "50811@debbugs.gnu.org" <50811@debbugs.gnu.org>
Subject: bug#50811: [External] : bug#50811: 28.0.50; Misleading Docstring for read-string function
Date: Mon, 27 Sep 2021 15:17:27 +0000	[thread overview]
Message-ID: <SJ0PR10MB54885FBD3ABD4C569BF32BA8F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <877df2ps02.fsf@gnus.org>

> The point is that we want to move away from pre-filled prompts in
> Emacs, and instead put the default in the "future history", i.e., say
> (read-string "PROMPT " nil nil "B")
> and then the user should `M-n' to edit the default.

Yes, and that "moving away" is misguided, IMHO.
There was never any reason to call INITIAL-INPUT
obsolete.

It's not either-or.

Just because `M-n' and DEFAULTS are useful, that's
never been a logical reason to make INITIAL-INPUT
obsolete.

(Oh, and that misguided deprecation was proclaimed
long before we allowed DEFAULTS to be a list and
not just a single value.)

      parent reply	other threads:[~2021-09-27 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26  8:28 bug#50811: 28.0.50; Misleading Docstring for read-string function mail--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-27  4:22 ` Lars Ingebrigtsen
2021-09-27  4:35   ` mail--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-27  4:40     ` Lars Ingebrigtsen
2021-09-27  4:56       ` mail--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-27  5:02         ` Lars Ingebrigtsen
2021-09-27 15:22       ` bug#50811: [External] : " Drew Adams
2021-09-27 15:17   ` Drew Adams [this message]

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=SJ0PR10MB54885FBD3ABD4C569BF32BA8F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=50811@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mail@codrut.pro \
    /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).