unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: mail--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: larsi@gnus.org
Cc: 50811@debbugs.gnu.org
Subject: bug#50811: 28.0.50; Misleading Docstring for read-string function
Date: Mon, 27 Sep 2021 04:56:55 +0000	[thread overview]
Message-ID: <_xpBfOIkHfREnzinZkclptbbDtel8T7CwR2Yxz_75lvMyMixsTP_G-2mkk2bvH2UuxTT1Q0bXBFn7Qobt7UhT50ib7j8dx5OePy7ymZg5VU=@codrut.pro> (raw)
In-Reply-To: <87r1daoclc.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

Bash has `C-u` for this, but that obviously can't be used in emacs. May I suggest a variable that controls the behaviour instead of changing it completely in the future? Just don't take my INITIAL-VALUE away :)

Anyway, there does not seem to be any action to take right now. Thank you for clarifying.

Cheers,
Codruț

www.codrut.pro

-------- Original Message --------
On 27 Sep 2021, 07:40, Lars Ingebrigtsen wrote:

> Codruț Constantin Gușoi <mail@codrut.pro> writes:
>
>> That's exactly the behaviour I need for renaming a file, for example; a
>> prompt pre-filled with the current filename. It's the same UX as in every
>> other program that does this sort of functionality and the extra keypress
>> makes it harder to use.
>
> I wasn't part of the discussions when this happened (I think it was more
> than a decade ago), but I think the idea was that users were annoyed
> that (in many cases) they had to remove the default completely before
> being able to type stuff in.
>
> That is, with
>
> (read-string "PROMPT " "This is the very long default")
>
> you have to delete all that before you can type in "foo", which is what
> you wanted to say. (Or `C-a C-k' is you're an expert.)
>
> Putting the default in the "future history" means that the user can type
> "foo" immediately (if they want that), or RET if they want the default,
> or `M-n' if they want to edit the default.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no

[-- Attachment #2: Type: text/html, Size: 1859 bytes --]

  reply	other threads:[~2021-09-27  4:56 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 [this message]
2021-09-27  5:02         ` Lars Ingebrigtsen
2021-09-27 15:22       ` bug#50811: [External] : " Drew Adams
2021-09-27 15:17   ` Drew Adams

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='_xpBfOIkHfREnzinZkclptbbDtel8T7CwR2Yxz_75lvMyMixsTP_G-2mkk2bvH2UuxTT1Q0bXBFn7Qobt7UhT50ib7j8dx5OePy7ymZg5VU=@codrut.pro' \
    --to=bug-gnu-emacs@gnu.org \
    --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).