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: Mon, 9 May 2016 13:35:36 -0700 (PDT) Message-ID: <04c43f82-234c-4e49-883b-1bb697af3303@default> References: <87k2j3jq28.fsf@gnus.org> <83y47jchvx.fsf@gnu.org> <87h9e7hyvw.fsf@gnus.org> <83futrcalj.fsf@gnu.org> <8737prhwnm.fsf@gnus.org> <83bn4fc951.fsf@gnu.org> <87oa8ff11d.fsf@gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1462826195 6091 80.91.229.3 (9 May 2016 20:36:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 9 May 2016 20:36:35 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 09 22:36:23 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 1azruf-0007Oa-UV for ged-emacs-devel@m.gmane.org; Mon, 09 May 2016 22:36:22 +0200 Original-Received: from localhost ([::1]:43292 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1azruf-0007AZ-6d for ged-emacs-devel@m.gmane.org; Mon, 09 May 2016 16:36:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36465) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1azruN-00071g-Lq for emacs-devel@gnu.org; Mon, 09 May 2016 16:36:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1azruG-0006F6-Qd for emacs-devel@gnu.org; Mon, 09 May 2016 16:36:02 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:51223) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1azru6-0006BM-Tc; Mon, 09 May 2016 16:35:47 -0400 Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u49KZfY6025120 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 May 2016 20:35:41 GMT Original-Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u49KZeN9006146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 May 2016 20:35:40 GMT Original-Received: from abhmp0015.oracle.com (abhmp0015.oracle.com [141.146.116.21]) by aserv0122.oracle.com (8.13.8/8.13.8) with ESMTP id u49KZb23014905; Mon, 9 May 2016 20:35:39 GMT In-Reply-To: <87oa8ff11d.fsf@gnus.org> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6744.5000 (x86)] X-Source-IP: aserv0021.oracle.com [141.146.126.233] 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:203754 Archived-At: > >> Right. What about moving the messages earlier so that the > >> users notice that they're there? > > > > No objections here. >=20 > Ok; I've now done this on the trunk. This is crazy, IMHO. I really do not understand why you are now entertaining complex, convoluted, and ugly (IMO) "solutions" to this problem. You are envisaging all kinds of things: changing the report format, changing how bug reports are sent, the UI,... Talk about overreaction! Lars brings up something that annoys him and suddenly the Emacs code is changed to adjust to his annoyance (and in a weird way). Why don't you just adopt what I suggested (emacsbugs+.el or similar)? The relevant changes to emacsbug.el are tiny and trivial. With the default option value, users see no change whatsoever. But you could change the default option value so that `report-messages' (or whatever) would not be included. Among other things, it would make the emacsbug.el code a bit more modular - it just breaks up the info that is scooped up into pieces/categories, and makes it easy to include/exclude the pieces. It means no changes to the existing bug-report format. It just gives users an easy way to determine just what information they send with a bug report - both in general (their preferred default behavior) and on the fly, for any given bug report. If you do decide to do what emacsbug+.el does I will gladly send it as a patch. It is just a small extension to the code in emacsbug.el. But why don't you just try it first? https://www.emacswiki.org/emacs/download/emacsbug%2b.el -- And if you continue to ignore this, then allow me to at least voice my objection to moving ANY of the data gathered BEFORE the user-typed bug report itself. That's nuts, IMHO. Keep the report at the top, and the supporting/background data at the bottom. Just one opinion.