unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13788@debbugs.gnu.org
Subject: bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations
Date: Sat, 23 Feb 2013 08:32:27 +0100	[thread overview]
Message-ID: <5128708B.80705@easy-emacs.de> (raw)
In-Reply-To: <83sj4okomz.fsf@gnu.org>

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.





  reply	other threads:[~2013-02-23  7:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 18:21 bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations Andreas Röhler
2013-02-22 18:24 ` Glenn Morris
2013-02-22 20:04 ` Eli Zaretskii
2013-02-22 21:27   ` Andreas Röhler
2013-02-22 21:46     ` Eli Zaretskii
2013-02-23  7:32       ` Andreas Röhler [this message]
2013-02-23 10:27         ` Eli Zaretskii
2013-02-23 13:19           ` Andreas Röhler
2013-02-23 14:51             ` Eli Zaretskii
2013-02-23 16:44               ` Andreas Röhler
2013-02-23 17:01             ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5128708B.80705@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=13788@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).