From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Remove "Recent messages" from `M-x report-emacs-bug'
Date: Mon, 09 May 2016 22:09:12 +0300 [thread overview]
Message-ID: <83futrcalj.fsf@gnu.org> (raw)
In-Reply-To: <87h9e7hyvw.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 09 May 2016 20:25:39 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org
> Date: Mon, 09 May 2016 20:25:39 +0200
>
> But I'm wondering why our experiences here are so different. I don't
> think I've ever found those messages important for handling a bug
> report. I mean, ever. Do you often find that those messages are
> important for tracking down bugs?
Yes, definitely. Users seldom tell enough details about what they see
or do, and the information collected by report-emacs-bug, including
the *Messages* part, sometimes provides clues that it would be very
hard to get at otherwise. Especially when the bug is not easily
reproducible, or there's no recipe at all. The alternative is to
start asking tedious questions about what they did and what Emacs
displayed, deal with incomplete and inaccurate accounts of that, etc.
> The few times I've even glanced at them, they've have mostly been about
> something completely irrelevant -- what the user had been doing while
> trying to figure out how to file the bug report, and not about what had
> happened when the bug happened.
That happens quite a lot, yes. But disregarding irrelevant data is
easy enough. When the data _is_ relevant it is invaluable, so even if
it happens infrequently, losing it would be a bad blow.
next prev parent reply other threads:[~2016-05-09 19:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 13:53 Remove "Recent messages" from `M-x report-emacs-bug' Lars Ingebrigtsen
2016-05-09 14:20 ` Kaushal Modi
2016-05-09 14:39 ` Kaushal Modi
2016-05-09 14:46 ` Andreas Schwab
2016-05-09 16:34 ` Eli Zaretskii
2016-05-09 14:44 ` Drew Adams
2016-05-10 15:48 ` Richard Stallman
2016-05-09 16:31 ` Eli Zaretskii
2016-05-09 18:25 ` Lars Ingebrigtsen
2016-05-09 19:09 ` Eli Zaretskii [this message]
2016-05-09 19:13 ` Lars Ingebrigtsen
2016-05-09 19:17 ` Dmitry Gutov
2016-05-09 19:25 ` Lars Ingebrigtsen
2016-05-09 19:43 ` Eli Zaretskii
2016-05-09 19:55 ` Lars Ingebrigtsen
2016-05-09 20:13 ` Lars Ingebrigtsen
2016-05-10 22:37 ` Glenn Morris
2016-05-09 19:34 ` Kaushal Modi
2016-05-09 19:37 ` Lars Ingebrigtsen
2016-05-09 19:44 ` Kaushal Modi
2016-05-09 19:58 ` Lars Ingebrigtsen
2016-05-09 20:23 ` Kaushal Modi
2016-05-09 20:56 ` Lars Ingebrigtsen
2016-05-09 21:03 ` Kaushal Modi
2016-05-10 10:06 ` Rasmus
2016-05-10 12:32 ` Nicolas Richard
2016-05-09 19:40 ` Eli Zaretskii
2016-05-09 20:07 ` Lars Ingebrigtsen
2016-05-09 20:35 ` Drew Adams
2016-05-09 17:32 ` Óscar Fuentes
2016-05-09 18:08 ` Paul Eggert
[not found] <<87k2j3jq28.fsf@gnus.org>
[not found] ` <<6ccbf505-5818-432b-98fa-0733930be2e7@default>
[not found] ` <<E1b09ty-0002sA-MS@fencepost.gnu.org>
2016-05-10 16:20 ` Drew Adams
2016-05-11 0:08 ` Richard Stallman
[not found] ` <<3ad08202-3529-4613-8f78-ef10b3abb9e2@default>
[not found] ` <<E1b0HhP-0006Me-VF@fencepost.gnu.org>
2016-05-11 14:44 ` Drew Adams
2016-05-12 0:23 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83futrcalj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.