all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: RE: Remove "Recent messages" from `M-x report-emacs-bug'
Date: Mon, 9 May 2016 07:44:52 -0700 (PDT)	[thread overview]
Message-ID: <6ccbf505-5818-432b-98fa-0733930be2e7@default> (raw)
In-Reply-To: <87k2j3jq28.fsf@gnus.org>

> Emacs bug reports include the ten most recent lines from the *Messages*
> buffer.  I think that's kinda unfortunate -- there may be private stuff
> there that people are not expecting to share with the world.
> 
> And I've never found that data useful when doing bug triage.
> 
> Should we remove it from the report?

It should possible for a _user_ to easily decide this, and not
just for the most recent lines from *Messages*.

Users should be able choose the default behavior for themselves -
which types of info to automatically include when they use
`M-x report-emacs-bug'.

And if they choose to not include certain types of info by default
they should still be able to easily include it interactively, for
any given bug report.

Library `emacsbug+.el' offers this, with option
`ebp-report-emacs-bug-included-fields' and these commands:

 `ebp-insert-all', `ebp-insert-features',
 `ebp-insert-load-path-shadows', `ebp-insert-major-mode',
 `ebp-insert-minor-modes', `ebp-insert-recent-input',
 `ebp-insert-recent-messages', `ebp-insert-settings',
 `ebp-insert-version'.

The default value of the option includes all of the fields:

  (version settings major-mode minor-modes recent-input
   recent-messages load-shadows features)

https://www.emacswiki.org/emacs/download/emacsbug%2b.el

So to satisfy only your concern, a user would only need to
remove `recent-messages' from the option value.  If your
suggestion of removing it by default were taken, then it
would just be removed from the default value of the option.

FWIW, I suggested such a user-control feature for vanilla
Emacs, but it was rejected.  See this (long) emacs-devel
thread:

http://lists.gnu.org/archive/html/emacs-devel/2013-01/msg00431.html



  parent reply	other threads:[~2016-05-09 14:44 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 [this message]
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
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=6ccbf505-5818-432b-98fa-0733930be2e7@default \
    --to=drew.adams@oracle.com \
    --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.