all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>, 30757@debbugs.gnu.org
Subject: bug#30757: Better manipulation (suppressing, examining type) of warnings from *Warnings* buffer
Date: Fri, 9 Mar 2018 07:05:56 -0800 (PST)	[thread overview]
Message-ID: <2c7d7920-8c41-4ad5-bde2-7c6b1f08dc46@default> (raw)
In-Reply-To: <877eql1ld0.fsf@gmail.com>

> 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.

+1

It would be good for the button/link to open *Help* with a more
complete description of the warning.  And there (in *Help*) there
could be buttons/links to suppress things.

In addition, we might have a command or commands that would
show such *Help* regardless of whether the warnings are being
shown.  In *Help*, if the warning is currently not being
shown then the button/link would enable showing it (i.e.,
the button toggles the behavior show/suppress).





  parent reply	other threads:[~2018-03-09 15:05 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2c7d7920-8c41-4ad5-bde2-7c6b1f08dc46@default \
    --to=drew.adams@oracle.com \
    --cc=30757@debbugs.gnu.org \
    --cc=npostavs@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 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.