unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: 30757@debbugs.gnu.org
Subject: bug#30757: Better manipulation (suppressing, examining type) of warnings from *Warnings* buffer
Date: Fri, 9 Mar 2018 09:53:58 -0500	[thread overview]
Message-ID: <CAM-tV-9kTL7wbBoFyDfdhV7E+LnC+ar4ZRh9RnwhvapguHkjyQ@mail.gmail.com> (raw)
In-Reply-To: <87woylminv.fsf@gmail.com>

On Fri, Mar 9, 2018 at 9:24 AM, Robert Pluim <rpluim@gmail.com> wrote:
> Robert Pluim <rpluim@gmail.com> writes:
>
>> Noam Postavsky <npostavs@gmail.com> writes:
>>
>>> It would be nice if warnings in the *Warnings* buffer came with some
>>> kind of button to let the user add the relevant value to
>>> warning-suppress-types or warning-suppress-log-types.
>>
>
> Reading your message on emacs-devel, I guess you'd want this kind of
> change to be made permanent? So customize-push-and-save of the
> resulting values?

Ah, yes, something using customize was more what I had in mind.

Also, potentially reusing the Warning(foo) prefix for the button might
save some space, the different types of suppression could accessed by
different keybindings/mouse clicks (maybe that conflicts with the
"easy to use" goal, though, not sure).


For reference, the emacs-devel post:
https://lists.gnu.org/archive/html/emacs-devel/2018-03/msg00314.html





  reply	other threads:[~2018-03-09 14:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 12:31 bug#30757: Better manipulation (suppressing, examining type) of warnings from *Warnings* buffer Noam Postavsky
2018-03-09 14:11 ` Robert Pluim
2018-03-09 14:24   ` Robert Pluim
2018-03-09 14:53     ` Noam Postavsky [this message]
2018-03-09 15:53       ` Robert Pluim
2018-03-09 16:18         ` Eli Zaretskii
2018-03-09 16:54           ` Robert Pluim
2018-03-09 18:28             ` Eli Zaretskii
2018-03-10  3:14             ` Noam Postavsky
2018-03-12 11:04               ` Robert Pluim
2020-09-04  4:30             ` Lars Ingebrigtsen
2020-09-04  8:54               ` Robert Pluim
2020-09-04 11:22                 ` Lars Ingebrigtsen
2018-03-09 15:05 ` Drew Adams
2018-03-09 15:49   ` Robert Pluim

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=CAM-tV-9kTL7wbBoFyDfdhV7E+LnC+ar4ZRh9RnwhvapguHkjyQ@mail.gmail.com \
    --to=npostavs@gmail.com \
    --cc=30757@debbugs.gnu.org \
    --cc=rpluim@gmail.com \
    /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).