From: Robert Pluim <rpluim@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 30757@debbugs.gnu.org
Subject: bug#30757: Better manipulation (suppressing, examining type) of warnings from *Warnings* buffer
Date: Mon, 12 Mar 2018 12:04:31 +0100 [thread overview]
Message-ID: <87k1uhk11c.fsf@gmail.com> (raw)
In-Reply-To: <87vae4zknx.fsf@gmail.com> (Noam Postavsky's message of "Fri, 09 Mar 2018 22:14:42 -0500")
Noam Postavsky <npostavs@gmail.com> writes:
> Robert Pluim <rpluim@gmail.com> writes:
>
>> Yes. I'm stuck between being precise but verbose, and more general and
>> succinct, and expressing the permanence of the resulting change. I've
>> make another attempt, although I'm still not entirely happy with it,
>> especially since the button texts are now quite long (I thought about
>> using the verb 'hide', but that's not accurate either).
>
> Perhaps taking Drew's suggestion to popup a *Help* window would give
> more room to be descriptive?
It would, but I thought the target user here was someone who doesn't
necessarily know much about how to configure stuff in Emacs, but just
wants to disable an annoying warning, so a long verbose detailed
*Help* window might be counter-productive.
Robert
next prev parent reply other threads:[~2018-03-12 11:04 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 [this message]
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=87k1uhk11c.fsf@gmail.com \
--to=rpluim@gmail.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 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).