unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: RE: Remove "Recent messages" from `M-x report-emacs-bug'
Date: Tue, 10 May 2016 09:20:17 -0700 (PDT)	[thread overview]
Message-ID: <3ad08202-3529-4613-8f78-ef10b3abb9e2@default> (raw)
In-Reply-To: <<E1b09ty-0002sA-MS@fencepost.gnu.org>>

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 
>   > It should possible for a _user_ to easily decide this, and not
>   > just for the most recent lines from *Messages*.
> 
>   > Users should be able choose the default behavior for themselves -
> 
> Maybe it would be more useful to ask this question each time
> the user runs report-emacs-bug.
> 
> It could ask, "Should Emacs insert information on your recent editing
> into the bug report?  (If you say yes, you will be able to delete any
> parts of that text from the mail buffer.)"  If the user says yes to
> this, it should insert all the data we would find useful.  If no, then
> none of it.
> 
> This should be enough to protect the user anyone from leaking anything
> private.

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.

Instead of all or none, present the user with the customize buffer,
to decide just which kinds of information to include by default.

It's not just about privacy, and it's not just about recent editing.
There can be other reasons why a user might not want to include (or
to bother with) different kinds of info.

1. It should be apparent to a user what info s?he is sending.
2. It should be up to the user to decide what s?he sends by default.
3. It should be easy (and obvious how) to change what gets sent for
   any given bug report - i.e., to do something different from what
   the user has chosen as preferred default behavior.
4. None of this should introduce inconvenience.  No bothersome
   questions each time you send a bug report, etc.
5. The bug report itself should be first, and any background,
   supporting information should follow, in the bug report.

In addition, I (too) think that everything sent should be in one
plain-text message, with no attachments (as now).  And I do not
think we should change the format (e.g. order of information)
gratuitously.





       reply	other threads:[~2016-05-10 16:20 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     ` Drew Adams [this message]
2016-05-11  0:08       ` Remove "Recent messages" from `M-x report-emacs-bug' 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
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=3ad08202-3529-4613-8f78-ef10b3abb9e2@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).