From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: bug#13141: please review bug #13141 Date: Mon, 21 Jan 2013 12:26:21 +0900 Message-ID: <878v7n5i8y.fsf@uwakimon.sk.tsukuba.ac.jp> References: <415AF94149E240B7BCB28128E45D3135@us.oracle.com> <20130119232015.GA517@acm.acm> <87obgk5npd.fsf@uwakimon.sk.tsukuba.ac.jp> <87k3r7mjob.fsf@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1358738793 7126 80.91.229.3 (21 Jan 2013 03:26:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Jan 2013 03:26:33 +0000 (UTC) Cc: acm@muc.de, Richard Stallman , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 21 04:26:51 2013 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 1Tx823-00026I-D5 for ged-emacs-devel@m.gmane.org; Mon, 21 Jan 2013 04:26:47 +0100 Original-Received: from localhost ([::1]:40594 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tx81m-0004mj-BX for ged-emacs-devel@m.gmane.org; Sun, 20 Jan 2013 22:26:30 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:34879) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tx81i-0004mQ-Vf for emacs-devel@gnu.org; Sun, 20 Jan 2013 22:26:28 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tx81h-0000tT-Fp for emacs-devel@gnu.org; Sun, 20 Jan 2013 22:26:26 -0500 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:48571) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tx81g-0000sx-Vr; Sun, 20 Jan 2013 22:26:25 -0500 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 0DA399700E0; Mon, 21 Jan 2013 12:26:22 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id C9B391A3537; Mon, 21 Jan 2013 12:26:21 +0900 (JST) In-Reply-To: <87k3r7mjob.fsf@yandex.ru> X-Mailer: VM undefined under 21.5 (beta32) "habanero" b0d40183ac79 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156528 Archived-At: Not Ccing <13141@debbugs.gnu.org> per Glenn's request. Dmitry Gutov writes: > I usually delete most of it, because the default text looks messy, and I > don't like sending emails that look untidy. Also, it's harder to find > the actual report description if it's surrounded by auto-generated text. Ah, I forgot about that. Steve Youngs fixed that for us ages ago. M-x report-xemacs-bug now pops up *two* buffers. One is a mail composition buffer which looks like this for message mode users: ------------------------------------------------------------------------ To: XEmacs Beta Subject: [Bug: 21.5-b32] Nothing works in the latest beta --text follows this line-- ================================================================ Dear Bug Team! ================================================================ System Info to help track down your bug: --------------------------------------- ------------------------------------------------------------------------ followed by the generated information. The other buffer is a help buffer explaining good style and desired content for bug reports, appended below in full just in case it has useful ideas. (Of course it is tainted from a legal viewpoint, but it wouldn't be hard to rewrite in a more GNU-y style.) The help buffer can be manipulated with the usual commands for such buffers, or suppressed completely. Steve ------------------------------------------------------------------------ This bug report will be sent to the XEmacs Development Team, not to your local site managers!! The working language of XEmacs development is English. Bug reports in English will be dealt with most promptly and most effectively. However, the XEmacs maintainers as a group speak most of the major Western languages and Japanese, so if communicating in English is a problem for you, please feel free to report your bug using one of those other languages. Please describe as succinctly as possible: - What happened. - What you thought should have happened. - Precisely what you were doing at the time. Also include a reliable recipe for triggering the bug, as well as any C and lisp back-traces that you may have. (setq stack-trace-on-error t), or (setq debug-on-error t) if you are familiar with the debugger, to get a lisp back-trace. To get a core file for the C back-trace on a GNU/Linux system do 'ulimit -c unlimited' in the shell prior to starting XEmacs. Type C-c tab to visit in Info the XEmacs Manual section about when and how to write a bug report, and what information to supply so that the bug can be fixed. Type SPC to scroll through this section and its subsections. You are very welcome to scan through the bug report and remove any potentially sensitive data. Turn off this help buffer permanently by adding: (setq report-xemacs-bug-no-explanations t) To your ~/.xemacs/init.el