From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25303@debbugs.gnu.org
Subject: bug#25303: 24.5; `write-region' enhancement request for MUSTBENEW parameter
Date: Sat, 27 Jul 2019 10:02:49 -0700 (PDT) [thread overview]
Message-ID: <3257e031-78dc-483b-98f9-77c54dfcc836@default> (raw)
In-Reply-To: <87sgqrkb51.fsf@mouse.gnus.org>
> > If parameter MUSTBENEW is not `excl' and is non-nil then the user is
> > prompted to confirm overwriting. The enhancement would be that if
> > the value is a string then use that as the confirmation prompt.
> >
> > The would allow for more specific prompting, such as saying something
> > more than that the file exists - something that can help the user decide
> > whether to overwrite.
>
> I think that does make some sense, but do you have a specific scenario
> in mind? What kind of prompt would help the user more than the
> standard prompt here?
I might have had a specific scenario in mind when
I filed the request 3 years ago, but if so it's
forgotten by now. ;-) Especially since there's
no real workaround to realize the requested
behavior easily.
> > This is pretty much backward compatible:
> > In existing code it is likely that few,
> > if any, non-nil and non-`excl' arg values
> > are strings. And in the case of any that are,
> > the use of the string as a prompt will make
> > things obvious to a maintainer, if not
> > immediately to the user.
>
> It's a slightly non-compatible change, but I think it sounds unlikely
> to be bothersome (as you point out).
>
> Anybody else have an opinion here?
next prev parent reply other threads:[~2019-07-27 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 22:33 bug#25303: 24.5; `write-region' enhancement request for MUSTBENEW parameter Drew Adams
2019-07-27 10:46 ` Lars Ingebrigtsen
2019-07-27 17:02 ` Drew Adams [this message]
2019-07-28 9:52 ` Lars Ingebrigtsen
2019-07-28 16:25 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3257e031-78dc-483b-98f9-77c54dfcc836@default \
--to=drew.adams@oracle.com \
--cc=25303@debbugs.gnu.org \
--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 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.