bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Andreas Röhler]

Customization of

report-emacs-bug-no-explanations

seems pointless, as emacs -Q will ignore it.

Being in favor of dropping this section and all other auto-inserts, keeping it in info etc. only

GNU Emacs 24.3.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.14) of 2013-02-21
Configured using:
  `configure CFLAGS='-g -O2 -fno-optimize-sibling-calls''

Important settings:
   value of $LC_CTYPE: de_DE.UTF-8
   value of $LANG: de_DE.utf8
   value of $XMODIFIERS: @im=local
   locale-coding-system: utf-8-unix
   default enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
   tooltip-mode: t
   mouse-wheel-mode: t
   tool-bar-mode: t
   menu-bar-mode: t
   file-name-shadow-mode: t
   global-font-lock-mode: t
   font-lock-mode: t
   blink-cursor-mode: t
   auto-composition-mode: t
   auto-encryption-mode: t
   auto-compression-mode: t
   line-number-mode: t
   transient-mark-mode: t

Recent input:
M-x r e p o r t - e a c <backspace> <backspace> m a
c s - c u <backspace> <backspace> b u g <return>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

Load-path shadows:
None found.

Features:
(shadow sort gnus-util mail-extr emacsbug message format-spec rfc822 mml
easymenu mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231
mailabbrev gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums
mm-util mail-prsvr mail-utils time-date tooltip ediff-hook vc-hooks
lisp-float-type mwheel x-win x-dnd tool-bar dnd fontset image regexp-opt
fringe tabulated-list newcomment lisp-mode register page menu-bar
rfn-eshadow timer select scroll-bar mouse jit-lock font-lock syntax
facemenu font-core frame cham georgian utf-8-lang misc-lang vietnamese
tibetan thai tai-viet lao korean japanese hebrew greek romanian slovak
czech european ethiopic indian cyrillic chinese case-table epa-hook
jka-cmpr-hook help simple abbrev minibuffer loaddefs button faces
cus-face macroexp files text-properties overlay sha1 md5 base64 format
env code-pages mule custom widget hashtable-print-readable backquote
make-network-process dbusbind inotify dynamic-setting
system-font-setting font-render-setting move-toolbar gtk x-toolkit x
multi-tty emacs)

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Glenn Morris]

Andreas Röhler wrote:

> Customization of
>
> report-emacs-bug-no-explanations
>
> seems pointless, as emacs -Q will ignore it.

You don't need to report bugs from emacs -Q.
You need to try and reproduce them from emacs -Q, is all.

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Eli Zaretskii]

> Date: Fri, 22 Feb 2013 19:21:53 +0100
> From: Andreas Röhler <andreas.roehler@online.de>
> 
> Customization of
> 
> report-emacs-bug-no-explanations
> 
> seems pointless, as emacs -Q will ignore it.

Emacs bugs are supposed to be reported from the same session that
discovered the bugs, which is rarely "emacs -Q".

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Andreas Röhler]

Am 22.02.2013 21:04, schrieb Eli Zaretskii:
>> Date: Fri, 22 Feb 2013 19:21:53 +0100
>> From: Andreas Röhler <andreas.roehler@online.de>
>>
>> Customization of
>>
>> report-emacs-bug-no-explanations
>>
>> seems pointless, as emacs -Q will ignore it.
>
> Emacs bugs are supposed to be reported from the same session that
> discovered the bugs, which is rarely "emacs -Q".
>
>
>
>
>

Then exists a doku bug, it's told

Please describe exactly what actions triggered the bug, and
the precise symptoms of the bug.  If you can, give a recipe
starting from `emacs -Q':

;;;;

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Eli Zaretskii]

> Date: Fri, 22 Feb 2013 22:27:42 +0100
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> 
> Then exists a doku bug, it's told
> 
> Please describe exactly what actions triggered the bug, and
> the precise symptoms of the bug.  If you can, give a recipe
> starting from `emacs -Q':

It's not a bug.  It is easier to debug a problem if it can be
reproduced starting with "emacs -Q".  But there's no requirement to
report the bug (with the recipe) from "emacs -Q".

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Andreas Röhler]

Am 22.02.2013 22:46, schrieb Eli Zaretskii:
>> Date: Fri, 22 Feb 2013 22:27:42 +0100
>> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
>>
>> Then exists a doku bug, it's told
>>
>> Please describe exactly what actions triggered the bug, and
>> the precise symptoms of the bug.  If you can, give a recipe
>> starting from `emacs -Q':
>
> It's not a bug.  It is easier to debug a problem if it can be
> reproduced starting with "emacs -Q".  But there's no requirement to
> report the bug (with the recipe) from "emacs -Q".
>
>

Well, the point is: present implementation clutters reports with directives useless for the receiver.
Better not to insert that into the report, but open a help-buffer, when reporting starts.
Plus an option to disable that help-buffer.

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Eli Zaretskii]

> Date: Sat, 23 Feb 2013 08:32:27 +0100
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> CC: 13788@debbugs.gnu.org
> 
> Well, the point is: present implementation clutters reports with directives useless for the receiver.

They are not useless for me, when I'm the receiver.

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Andreas Röhler]

Am 23.02.2013 11:27, schrieb Eli Zaretskii:
>> Date: Sat, 23 Feb 2013 08:32:27 +0100
>> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
>> CC: 13788@debbugs.gnu.org
>>
>> Well, the point is: present implementation clutters reports with directives useless for the receiver.
>
> They are not useless for me, when I'm the receiver.
>

So let's consider a typical beginning of a bug report when sent not by a core developer,
let's take bug#13787. It starts:

This bug report will be sent to the Bug-GNU-Emacs mailing list
and the GNU bug tracker at debbugs.gnu.org.  Please check that
the From: line contains a valid email address.  After a delay of up
to one day, you should receive an acknowledgement at that address.

Please write in English if possible, as the Emacs maintainers
usually do not have translators for other languages.

Please describe exactly what actions triggered the bug, and
the precise symptoms of the bug.  If you can, give a recipe
starting from `emacs -Q':

;;;;;;;

You really mean that kind of info is useful for you?

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Eli Zaretskii]

> Date: Sat, 23 Feb 2013 14:19:04 +0100
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> CC: 13788@debbugs.gnu.org
> 
> This bug report will be sent to the Bug-GNU-Emacs mailing list
> and the GNU bug tracker at debbugs.gnu.org.  Please check that
> the From: line contains a valid email address.  After a delay of up
> to one day, you should receive an acknowledgement at that address.
> 
> Please write in English if possible, as the Emacs maintainers
> usually do not have translators for other languages.
> 
> Please describe exactly what actions triggered the bug, and
> the precise symptoms of the bug.  If you can, give a recipe
> starting from `emacs -Q':
> 
> ;;;;;;;
> 
> You really mean that kind of info is useful for you?

Yes.  It tells me that the person who reports the bug didn't censor
her report in any way.

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Andreas Röhler]

Am 23.02.2013 15:51, schrieb Eli Zaretskii:
>> Date: Sat, 23 Feb 2013 14:19:04 +0100
>> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
>> CC: 13788@debbugs.gnu.org
>>
>> This bug report will be sent to the Bug-GNU-Emacs mailing list
>> and the GNU bug tracker at debbugs.gnu.org.  Please check that
>> the From: line contains a valid email address.  After a delay of up
>> to one day, you should receive an acknowledgement at that address.
>>
>> Please write in English if possible, as the Emacs maintainers
>> usually do not have translators for other languages.
>>
>> Please describe exactly what actions triggered the bug, and
>> the precise symptoms of the bug.  If you can, give a recipe
>> starting from `emacs -Q':
>>
>> ;;;;;;;
>>
>> You really mean that kind of info is useful for you?
>
> Yes.  It tells me that the person who reports the bug didn't censor
> her report in any way.
>

And you are not afraid making her look somehow foolish that way?

bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations

[Stefan Monnier]

> This bug report will be sent to the Bug-GNU-Emacs mailing list
> and the GNU bug tracker at debbugs.gnu.org.  Please check that
> the From: line contains a valid email address.  After a delay of up
> to one day, you should receive an acknowledgement at that address.

> Please write in English if possible, as the Emacs maintainers
> usually do not have translators for other languages.

> Please describe exactly what actions triggered the bug, and
> the precise symptoms of the bug.  If you can, give a recipe
> starting from `emacs -Q':

This text is not part of the bug-report buffer any more.  I changed it
a few months ago, it's now in a display property, so while you see it,
it's not really there: it won't be in the sent email, and it won't be
present if you copy&paste the text either.


        Stefan