From: Dmitry Gutov <dgutov@yandex.ru>
To: Richard Stallman <rms@gnu.org>
Cc: acm@muc.de, "Stephen J. Turnbull" <stephen@xemacs.org>,
13141@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#13141: please review bug #13141
Date: Mon, 21 Jan 2013 05:03:32 +0400 [thread overview]
Message-ID: <87k3r7mjob.fsf__30208.8107834154$1358730287$gmane$org@yandex.ru> (raw)
In-Reply-To: <E1TwzpU-0007Of-Pd@fencepost.gnu.org> (Richard Stallman's message of "Sun, 20 Jan 2013 13:41:16 -0500")
Richard Stallman <rms@gnu.org> writes:
> Stephen J. Turnbull writes:
>
> I've had at least half a dozen cases
> where users deleted automatically added information which I then
> requested -- to no avail, since the reporters never responded.
If there's no information at all, maybe the users didn't go through the
Emacs bug reporting interface, writing the report directly in the email client.
> To go out of their way to delete it makes me wonder why. Maybe it was
> a valid reason. Could it be that there was something private in that
> information which they specifically did not want to send?
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.
It's better now that some parts of it are just shown through the display
property, but the user might not know/understand that.
> Because of this consideration it would not be right to hide
> that information. We should not try to trick our users into sending
> us something they did not want to send.
As it is, the exact information the user's sending is not immediately
obvious, they'd have to carefully scroll though a fairly large chunk of
text to know that.
IMO, it would be better to ask about each potentially-sensitive section
(last keystrokes, obviously; local paths, recent messages? maybe), and
then include them as attachment or several.
next prev parent reply other threads:[~2013-01-21 1:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <415AF94149E240B7BCB28128E45D3135@us.oracle.com>
2013-01-19 23:20 ` bug#13141: please review bug #13141 Alan Mackenzie
2013-01-19 23:21 ` Drew Adams
[not found] ` <20130119232015.GA517@acm.acm>
2013-01-19 23:59 ` Drew Adams
[not found] ` <ED6808FFB4C84116B3267774EC79431F@us.oracle.com>
2013-01-20 0:12 ` Xue Fuqiao
2013-01-20 7:16 ` Stephen J. Turnbull
2013-01-20 10:50 ` Alan Mackenzie
[not found] ` <20130120105003.GA3091@acm.acm>
2013-01-20 12:02 ` Xue Fuqiao
2013-01-20 17:40 ` Drew Adams
[not found] ` <1543326591D441B1ABA599BE163B141E@us.oracle.com>
2013-01-21 4:24 ` Drew Adams
[not found] ` <87obgk5npd.fsf@uwakimon.sk.tsukuba.ac.jp>
2013-01-20 10:33 ` Xue Fuqiao
2013-01-20 17:08 ` Eli Zaretskii
2013-01-20 18:41 ` Richard Stallman
2013-01-21 1:03 ` Dmitry Gutov [this message]
2013-01-21 2:39 ` Stephen J. Turnbull
2012-12-11 16:00 bug#13141: 24.3.50; Be able to customize the info included by default for `report-emacs-bug' Drew Adams
2013-01-19 23:10 ` bug#13141: please review bug #13141 Drew Adams
2013-01-20 0:35 ` Dmitry Gutov
[not found] ` <87ip6sofn7.fsf@yandex.ru>
2013-01-20 0:54 ` Xue Fuqiao
2013-01-20 1:03 ` Drew Adams
[not found] ` <20130120085455.93b0f44394a4db0ffcebd5c9@gmail.com>
2013-01-20 7:19 ` Stephen J. Turnbull
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='87k3r7mjob.fsf__30208.8107834154$1358730287$gmane$org@yandex.ru' \
--to=dgutov@yandex.ru \
--cc=13141@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stephen@xemacs.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).