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>
Cc: 25303@debbugs.gnu.org
Subject: bug#25303: 24.5; `write-region' enhancement request for MUSTBENEW parameter
Date: Sun, 28 Jul 2019 09:25:13 -0700 (PDT)	[thread overview]
Message-ID: <77f43ded-fd3a-4fa7-a478-5b07614fd8d2@default> (raw)
In-Reply-To: <m3tvb65vv5.fsf@gnus.org>

> >> 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.
> 
> OK; closing this bug report.  If somebody has a specific need for this,
> they'll open a new bug report.

Why close an enhancement request such as this,
just because, years later, I can't recall a
specific scenario where the enhancement is
_needed_?  Why wouldn't this be a good thing
to have (and at no cost)?

Even if you're not personally convinced of the
usefulness (in spite of your saying that it
makes sense), why not leave it open, for someone
else who might decide to implement it at some
point?

What do we gain by your closing such an enhancement
suggestion?

Suppose that the OP suggesting the enhancement had
not replied to your request for remembrance of a
specific scenario.  Suppose that the OP was no
longer around.  Would that be a reason why the
enhancement is a bad idea?  I don't think so.
(And no such bad-idea reason has been given, BTW.)





      reply	other threads:[~2019-07-28 16:25 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
2019-07-28  9:52     ` Lars Ingebrigtsen
2019-07-28 16:25       ` 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=77f43ded-fd3a-4fa7-a478-5b07614fd8d2@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 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).