From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: Remove "Recent messages" from `M-x report-emacs-bug' Date: Tue, 10 May 2016 09:20:17 -0700 (PDT) Message-ID: <3ad08202-3529-4613-8f78-ef10b3abb9e2@default> References: <<87k2j3jq28.fsf@gnus.org>> <<6ccbf505-5818-432b-98fa-0733930be2e7@default>> <> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1462897264 2125 80.91.229.3 (10 May 2016 16:21:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 May 2016 16:21:04 +0000 (UTC) Cc: larsi@gnus.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 10 18:20:51 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b0AOx-0008Gk-HJ for ged-emacs-devel@m.gmane.org; Tue, 10 May 2016 18:20:51 +0200 Original-Received: from localhost ([::1]:47437 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b0AOw-0005Fc-4q for ged-emacs-devel@m.gmane.org; Tue, 10 May 2016 12:20:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36196) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b0AOb-0005Cx-Fo for emacs-devel@gnu.org; Tue, 10 May 2016 12:20:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b0AOW-0003Gt-EE for emacs-devel@gnu.org; Tue, 10 May 2016 12:20:29 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:41222) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b0AOW-0003Ft-3H; Tue, 10 May 2016 12:20:24 -0400 Original-Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u4AGKIsb008763 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 May 2016 16:20:18 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u4AGKIHe005093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 May 2016 16:20:18 GMT Original-Received: from abhmp0017.oracle.com (abhmp0017.oracle.com [141.146.116.23]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u4AGKHFO014907; Tue, 10 May 2016 16:20:18 GMT In-Reply-To: <> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6744.5000 (x86)] X-Source-IP: userv0021.oracle.com [156.151.31.71] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:203771 Archived-At: > [[[ 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. ]]] >=20 > > It should possible for a _user_ to easily decide this, and not > > just for the most recent lines from *Messages*. >=20 > > Users should be able choose the default behavior for themselves - >=20 > Maybe it would be more useful to ask this question each time > the user runs report-emacs-bug. >=20 > 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. >=20 > 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.