From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org, Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: RE: Remove "Recent messages" from `M-x report-emacs-bug'
Date: Wed, 11 May 2016 07:44:48 -0700 (PDT) [thread overview]
Message-ID: <03aa6991-05db-42d8-93cb-9b45ece07436@default> (raw)
In-Reply-To: <<E1b0HhP-0006Me-VF@fencepost.gnu.org>>
> > Asking is not bad, as a default behavior. But a user who is asked
> > should be able, while responding, to state whether s?he wants to
> > continue to be asked for subsequent bug reports.
>
> Why? The answer won't be the same each time. It depends on what
> you're doing.
The answer _might_ be the same each time. Or it might be the
same _most_ times. The point is to give a user the chance to
_decide whether_ to be asked each time. Some users might not
want to be asked each time.
A user can set personal default behavior. A user can override
that behavior for any given bug report (e.g., if s?he thinks
that some kind of info is important to that report).
These latter two features are what I provided in the slight
extension to emacsbug.el: (1) Let users customize what the
default behavior is, for them. (2) Let users override this
for any given report, by providing commands that insert
particular kinds of info.
What you added to the mix was the suggestion to ask users
what they want to do in this regard, when they submit a
report.
What I added to your suggestion is to let users do that
AND let them choose whether to (a) apply their answer
also to future reports or (b) be asked anew each time.
next prev parent reply other threads:[~2016-05-11 14:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<87k2j3jq28.fsf@gnus.org>
[not found] ` <<6ccbf505-5818-432b-98fa-0733930be2e7@default>
[not found] ` <<E1b09ty-0002sA-MS@fencepost.gnu.org>
2016-05-10 16:20 ` Remove "Recent messages" from `M-x report-emacs-bug' Drew Adams
2016-05-11 0:08 ` Richard Stallman
[not found] ` <<3ad08202-3529-4613-8f78-ef10b3abb9e2@default>
[not found] ` <<E1b0HhP-0006Me-VF@fencepost.gnu.org>
2016-05-11 14:44 ` Drew Adams [this message]
2016-05-12 0:23 ` Richard Stallman
2016-05-09 13:53 Lars Ingebrigtsen
2016-05-09 14:20 ` Kaushal Modi
2016-05-09 14:39 ` Kaushal Modi
2016-05-09 14:46 ` Andreas Schwab
2016-05-09 16:34 ` Eli Zaretskii
2016-05-09 14:44 ` Drew Adams
2016-05-10 15:48 ` Richard Stallman
2016-05-09 16:31 ` Eli Zaretskii
2016-05-09 18:25 ` Lars Ingebrigtsen
2016-05-09 19:09 ` Eli Zaretskii
2016-05-09 19:13 ` Lars Ingebrigtsen
2016-05-09 19:17 ` Dmitry Gutov
2016-05-09 19:25 ` Lars Ingebrigtsen
2016-05-09 19:43 ` Eli Zaretskii
2016-05-09 19:55 ` Lars Ingebrigtsen
2016-05-09 20:13 ` Lars Ingebrigtsen
2016-05-10 22:37 ` Glenn Morris
2016-05-09 19:34 ` Kaushal Modi
2016-05-09 19:37 ` Lars Ingebrigtsen
2016-05-09 19:44 ` Kaushal Modi
2016-05-09 19:58 ` Lars Ingebrigtsen
2016-05-09 20:23 ` Kaushal Modi
2016-05-09 20:56 ` Lars Ingebrigtsen
2016-05-09 21:03 ` Kaushal Modi
2016-05-10 10:06 ` Rasmus
2016-05-10 12:32 ` Nicolas Richard
2016-05-09 19:40 ` Eli Zaretskii
2016-05-09 20:07 ` Lars Ingebrigtsen
2016-05-09 20:35 ` Drew Adams
2016-05-09 17:32 ` Óscar Fuentes
2016-05-09 18:08 ` Paul Eggert
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=03aa6991-05db-42d8-93cb-9b45ece07436@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.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).