From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: Remove "Recent messages" from `M-x report-emacs-bug'
Date: Mon, 9 May 2016 13:35:36 -0700 (PDT) [thread overview]
Message-ID: <04c43f82-234c-4e49-883b-1bb697af3303@default> (raw)
In-Reply-To: <87oa8ff11d.fsf@gnus.org>
> >> Right. What about moving the messages earlier so that the
> >> users notice that they're there?
> >
> > No objections here.
>
> Ok; I've now done this on the trunk.
This is crazy, IMHO.
I really do not understand why you are now entertaining
complex, convoluted, and ugly (IMO) "solutions" to this
problem.
You are envisaging all kinds of things: changing the report
format, changing how bug reports are sent, the UI,...
Talk about overreaction! Lars brings up something that annoys
him and suddenly the Emacs code is changed to adjust to his
annoyance (and in a weird way).
Why don't you just adopt what I suggested (emacsbugs+.el or
similar)? The relevant changes to emacsbug.el are tiny and
trivial. With the default option value, users see no change
whatsoever. But you could change the default option value
so that `report-messages' (or whatever) would not be included.
Among other things, it would make the emacsbug.el code a bit
more modular - it just breaks up the info that is scooped up
into pieces/categories, and makes it easy to include/exclude
the pieces.
It means no changes to the existing bug-report format. It just
gives users an easy way to determine just what information they
send with a bug report - both in general (their preferred default
behavior) and on the fly, for any given bug report.
If you do decide to do what emacsbug+.el does I will gladly
send it as a patch. It is just a small extension to the code
in emacsbug.el. But why don't you just try it first?
https://www.emacswiki.org/emacs/download/emacsbug%2b.el
--
And if you continue to ignore this, then allow me to at least
voice my objection to moving ANY of the data gathered BEFORE
the user-typed bug report itself. That's nuts, IMHO. Keep
the report at the top, and the supporting/background data at
the bottom. Just one opinion.
next prev parent reply other threads:[~2016-05-09 20:35 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
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 [this message]
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=04c43f82-234c-4e49-883b-1bb697af3303@default \
--to=drew.adams@oracle.com \
--cc=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.