From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 30757@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#30757: Better manipulation (suppressing, examining type) of warnings from *Warnings* buffer
Date: Fri, 09 Mar 2018 20:28:49 +0200 [thread overview]
Message-ID: <83tvtpumqm.fsf@gnu.org> (raw)
In-Reply-To: <87vae5jikg.fsf@gmail.com> (message from Robert Pluim on Fri, 09 Mar 2018 17:54:23 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 30757@debbugs.gnu.org, npostavs@gmail.com
> Date: Fri, 09 Mar 2018 17:54:23 +0100
>
> > "+++" means this change was documented in the manual(s), but this
> > change wasn't, AFAIU. Shkuld this be documented in the ELisp manual?
> >
>
> etc/NEWS says:
>
> +++ indicates that all necessary documentation updates are complete.
> (This means all relevant manuals in doc/ AND lisp doc-strings.)
>
> I'd looked through the manuals and couldn't see anywhere where I
> thought it should be documented, hence I only changed the
> doc-string. We can go for '---' in that case.
"---" is correct if a change needs not be documented, yes.
In this case, I wonder whether we should document this where
warning-suppress-types etc. are documented.
> +---
> +** Specific warnings can now be disabled from the warning buffer.
> +When a warning is displayed to the user, the resulting buffer now has
> +buttons which allow making permanent changes to the treatment of that
> +warning. Automatic showing of the warning can be disabled (although
> +it is still generated), or generation of the warning can be disabled
> +entirely.
Instead of the vague "generation" I'd suggest to say explicitly that
its logged in the *Messages* buffer. Otherwise, this text is a
significant improvement, thanks.
> +(define-button-type 'warning-suppress-warning
> + 'action #'warning-suppress-action
> + 'help-echo "mouse-2, RET: Don't display this warning automatically")
> +(defun warning-suppress-action (button)
> + (customize-save-variable 'warning-suppress-types
> + (cons (list (button-get button 'warning-type))
> + warning-suppress-types)))
> +(define-button-type 'warning-suppress-log-warning
> + 'action #'warning-suppress-log-action
> + 'help-echo "mouse-2, RET: Never generate this warning again")
> +(defun warning-suppress-log-action (button)
> + (customize-save-variable 'warning-suppress-log-types
> + (cons (list (button-get button 'warning-type))
> + warning-suppress-types)))
I think we should make similar changes in the help-echo strings.
> + (insert-button "Disable showing automatically" 'type 'warning-suppress-warning 'warning-type type)
> + (insert " ")
> + (insert-button "Never generate" 'type 'warning-suppress-log-warning 'warning-type type)
And here.
next prev parent reply other threads:[~2018-03-09 18:28 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 [this message]
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=83tvtpumqm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30757@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--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).