all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Dmitry Gutov'" <dgutov@yandex.ru>
Cc: 13141@debbugs.gnu.org, emacs-devel@gnu.org
Subject: RE: bug#13141: please review bug #13141
Date: Sat, 19 Jan 2013 17:03:16 -0800	[thread overview]
Message-ID: <C4FB38A784204F58AFF747F2F2BCB7B8@us.oracle.com> (raw)
In-Reply-To: <87ip6sofn7.fsf@yandex.ru>

> Personally, I disagree that the user should choose what information
> to include. 

Too bad for you, then.  The user already chooses that.  As well s?he should.  A
user should _of course_ be able to choose what information s?he sends.

This is about the information that is _automatically_ inserted into the
report-preparation buffer.  If the user does not want to send some of that info
then s?he need not, even today, as Xue Fuqiao made clear.  All my patch does is
make it easier for a user to not send this or that info.

> The report goes to Emacs maintainers, so they should pick the
> always-useful parts

The maintainers should pick the parts that they think should be provided _by
default_, just as they do today.  They cannot and should not pick, in place of
the user, what the user actually sends.

And one of the maintainers has already stated, FWIW, that he finds "most of
those info useless".

> (say, the version, bzr revision and build options) and leave
> out the noise.

One person's noise is another's important information.  That's part of the point
of providing this option: if a user so chooses, s?he can easily cut down on what
s?he considers noise.

Let users decide.  Emacs proposes, users dispose.

And I repeat, the default behavior - the information that is automatically
included by default - does NOT change with this patch.

> While possibly still providing interactive commands
> allowing to insert the additional information in a follow-up email.

Nothing wrong with that, IMO.  Consider submitting an enhancement request for
the addition of such commands.

> I also think this is one of the parts of Emacs where backwards
> compatibility is the least important, so it's odd that the 
> bug reporting interface hasn't changed much in years.

You are welcome to submit an enhancement request to change the set of info that
gets inserted by default.

My patch is not so radical as what you are requesting.  It maintains the status
quo wrt that set of info - the default behavior.  It simply makes it easy for a
user to customize what which info gets inserted by default.

There already is a user option, `report-emacs-bug-no-explanations', that turns
it all off.  My patch just gives users more control than an on/off switch.




  parent reply	other threads:[~2013-01-20  1:03 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2012-12-11 16:12 ` Dani Moncayo
2012-12-11 16:18   ` Drew Adams
2012-12-11 16:24     ` Dani Moncayo
2012-12-11 16:28       ` Drew Adams
2012-12-11 19:13   ` Jambunathan K
2012-12-11 19:19     ` Glenn Morris
2012-12-11 19:34       ` Stefan Monnier
2013-01-20  9:45         ` bug#13141: 24.3.50; Be able to customize the info included by default for`report-emacs-bug' Drew Adams
2013-01-21  1:22           ` Stefan Monnier
2013-01-21  1:35             ` Drew Adams
2013-01-21  1:54               ` Stefan Monnier
2013-01-21  2:09                 ` Drew Adams
2012-12-11 19:27     ` bug#13141: 24.3.50; Be able to customize the info included by default for `report-emacs-bug' Drew Adams
2012-12-11 16:29 ` Stefan Monnier
2012-12-11 16:37   ` Drew Adams
2012-12-11 19:45 ` Glenn Morris
2012-12-11 19:59   ` bug#13141: [PATCH]: 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
2013-01-20  0:35   ` Dmitry Gutov
2013-01-20  0:54     ` Xue Fuqiao
2013-01-20  0:54     ` Xue Fuqiao
2013-01-20  7:19       ` Stephen J. Turnbull
2013-01-20 19:46         ` Harald Hanche-Olsen
2013-01-20  7:19       ` Stephen J. Turnbull
2013-01-20  1:03     ` Drew Adams [this message]
2013-01-20  1:03     ` Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2013-01-19 23:10 Drew Adams
2013-01-19 23:20 ` bug#13141: " Alan Mackenzie
2013-01-19 23:20 ` Alan Mackenzie
2013-01-19 23:59   ` bug#13141: " Drew Adams
2013-01-19 23:59   ` Drew Adams
2013-01-20  0:12     ` bug#13141: " Xue Fuqiao
2013-01-20  7:16     ` Stephen J. Turnbull
2013-01-20  7:16     ` Stephen J. Turnbull
2013-01-20 10:33       ` bug#13141: " Xue Fuqiao
2013-01-20 17:08       ` Eli Zaretskii
2013-01-20 18:41       ` Richard Stallman
2013-01-21  1:03         ` Dmitry Gutov
2013-01-21  1:03         ` Dmitry Gutov
2013-01-21  3:02           ` Stephen J. Turnbull
2013-01-21  3:26           ` Stephen J. Turnbull
2013-01-21  2:39         ` Stephen J. Turnbull
2013-01-20 10:50     ` Alan Mackenzie
2013-01-20 12:02       ` bug#13141: " Xue Fuqiao
2013-01-20 17:40       ` Drew Adams
2013-01-20 17:40       ` Drew Adams
2013-01-21  4:24         ` bug#13141: " Drew Adams
2013-01-20 10:50     ` Alan Mackenzie
2013-01-19 23:21 ` Drew Adams

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=C4FB38A784204F58AFF747F2F2BCB7B8@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13141@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@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 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.