From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.bugs Subject: bug#11297: 24.1.50; `report-emacs-bug': help, TAB Date: Sat, 21 Apr 2012 08:28:56 -0700 Message-ID: <531DF00274A246298C1665C5E6879AE3@us.oracle.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1335022184 27546 80.91.229.3 (21 Apr 2012 15:29:44 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 21 Apr 2012 15:29:44 +0000 (UTC) To: 11297@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Apr 21 17:29:43 2012 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1SLcFq-0005KN-Mn for geb-bug-gnu-emacs@m.gmane.org; Sat, 21 Apr 2012 17:29:42 +0200 Original-Received: from localhost ([::1]:55524 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLcFq-0000hu-1y for geb-bug-gnu-emacs@m.gmane.org; Sat, 21 Apr 2012 11:29:42 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:56474) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLcFj-0000Y0-U4 for bug-gnu-emacs@gnu.org; Sat, 21 Apr 2012 11:29:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SLcFg-0003Mg-Nw for bug-gnu-emacs@gnu.org; Sat, 21 Apr 2012 11:29:35 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:44793) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLcFg-0003Mc-KX for bug-gnu-emacs@gnu.org; Sat, 21 Apr 2012 11:29:32 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1SLcGA-00030G-TP for bug-gnu-emacs@gnu.org; Sat, 21 Apr 2012 11:30:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "Drew Adams" Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 21 Apr 2012 15:30:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 11297 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: X-Debbugs-Original-To: Original-Received: via spool by submit@debbugs.gnu.org id=B.133502219411493 (code B ref -1); Sat, 21 Apr 2012 15:30:02 +0000 Original-Received: (at submit) by debbugs.gnu.org; 21 Apr 2012 15:29:54 +0000 Original-Received: from localhost ([127.0.0.1]:45824 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1SLcG1-0002zK-Fe for submit@debbugs.gnu.org; Sat, 21 Apr 2012 11:29:53 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:51177) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1SLcFy-0002z6-D6 for submit@debbugs.gnu.org; Sat, 21 Apr 2012 11:29:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SLcFM-0003L3-NS for submit@debbugs.gnu.org; Sat, 21 Apr 2012 11:29:14 -0400 Original-Received: from lists.gnu.org ([208.118.235.17]:46932) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLcFM-0003Kz-Jq for submit@debbugs.gnu.org; Sat, 21 Apr 2012 11:29:12 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:56377) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLcFK-0000WH-MV for bug-gnu-emacs@gnu.org; Sat, 21 Apr 2012 11:29:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SLcFI-0003Kn-ER for bug-gnu-emacs@gnu.org; Sat, 21 Apr 2012 11:29:10 -0400 Original-Received: from acsinet15.oracle.com ([141.146.126.227]:43366) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLcFI-0003Kc-7y for bug-gnu-emacs@gnu.org; Sat, 21 Apr 2012 11:29:08 -0400 Original-Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q3LFT3LO017908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 21 Apr 2012 15:29:04 GMT Original-Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q3LFT33S025720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 21 Apr 2012 15:29:03 GMT Original-Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q3LFT38i020989 for ; Sat, 21 Apr 2012 10:29:03 -0500 Original-Received: from dradamslap1 (/10.159.63.181) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 21 Apr 2012 08:29:02 -0700 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Ac0f03cdPP0SMSoPSy+GdOc/mb025Q== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-CT-RefId: str=0001.0A090207.4F92D240.01AC,ss=1,re=0.000,fgs=0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 1) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:59361 Archived-At: 1. Since Emacs 23, TAB in the bug-reporting buffer is bound to `message-tab'. Before that it was bound to `indent-for-tab-command'. The doc string of `message-tab' really should say what `TAB' does in the typical case where it is pressed in such a buffer. Instead, it says what TAB does when in a message header (but without ever saying clearly that that is what it is describing). And then it sends readers packing for info about what it does in the actual message body they are writing. The last sentence is all readers have in this regard: "Execute function specified by `message-tab-body-function' when not in those headers." There is no indication of what "those headers" refers to, but with a little guessing, especially if you follow the links to look up `message-completion-alist' and `message-tab-body-function', you can perhaps figure out that (a) the first part of the doc string only describes TAB in message headers and (b) in the body, TAB does what it does in the `text-mode-map' or the `global-map'. That's a lot of runaround and not very helpful. Those two bits of info should at the very least be reversed: Say first what TAB does in the body of the message, which is 99% of what users write. Then say that TAB in a header completes a header field. Better would be to just start out by saying that by default TAB in the body does `indent-for-tab-command' for regular text. Details about the actual command coming from `text-mode-map' or `global-map' can follow that. It is important for users to realize that (a) TAB generally does what it does for regular text and (b) they can change the buffer mode temporarily to make it act differently. E.g., to edit a Lisp snippet they can use `M-x emacs-lisp-mode'. For (b), they must be made aware that to actually send the message (`C-c C-c') they must return to `message-mode' or use `M-x message-send-and-exit'. 2. All of the information we provide to users about writing a bug report should be consolidated in the same place. Some is now in the separate little `*Bug Help*' buffer that is popped up (why?), and some is in the message buffer itself (why?), even though it does not get included in the message that is sent. That separation makes little sense, unless I'm missing something. Users should have all of the help in the same place, and it should include help about writing a bug report and help about sending that report as a mail message. One possibility would be to have a single sentence telling you to hit some key, or providing a link, which would show all of the help. But if you really want to fill the buffer with the help text for some reason, that will work too. And as mentioned above, the help info we provide should also mention that you can change the mode but that you must return to `message-mode' to use `C-c C-c'. (Too bad about that, BTW.) Bug reports often include snippets of Emacs Lisp or code from other modes. It might not be obvious to some users that they can do this, that they need not edit the code somewhere else and then yank the final, edited snippet to the message buffer. In GNU Emacs 24.1.50.1 (i386-mingw-nt5.1.2600) of 2012-04-19 on MARVIN Bzr revision: 107968 monnier@iro.umontreal.ca-20120419220225-gijdcbfxuiqy5dhb Windowing system distributor `Microsoft Corp.', version 5.1.2600 Configured using: `configure --with-gcc (4.6) --no-opt --enable-checking --cflags -ID:/devel/emacs/libs/libXpm-3.5.8/include -ID:/devel/emacs/libs/libXpm-3.5.8/src -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include -ID:/devel/emacs/libs/giflib-4.1.4-1/include -ID:/devel/emacs/libs/jpeg-6b-4/include -ID:/devel/emacs/libs/tiff-3.8.2-1/include -ID:/devel/emacs/libs/gnutls-3.0.9/include -ID:/devel/emacs/libs/libiconv-1.13.1-1-dev/include -ID:/devel/emacs/libs/libxml2-2.7.8/include/libxml2'