From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Glenn Morris <rgm@gnu.org>
Cc: 4837@emacsbugs.donarmstrong.com, rms@gnu.org
Subject: bug#4837: with-fewer-warnings ?
Date: Tue, 10 Nov 2009 12:58:06 -0500 [thread overview]
Message-ID: <jwvr5s6xo2s.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <4ivdhjxh94.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 09 Nov 2009 21:09:43 -0500")
>> Actually, I think I agree (I hate with-no-warnings), but it should be
>> even more precise, and specify which obsolete warning to silence.
> Do you mean, specify precisely which obsolete variable/function(s) not
> to warn about? That's probably doable via
> byte-compile-not-obsolete-vars/funcs, I'll have a look.
> A syntax like this?
> (with-suppressed-warnings
> '((obsolete read-file-name-predicate ...) cl-functions ...)
> body)
Yes, something like that. Also the `cl-functions' is too broad and
should not be allowed.
> Although the motivation for this was not _just_ obsolete warnings, and
> it might not be so simple to extend your request to eg specific free
> variables.
I didn't say it was easy.
BTW, maybe a good way to do it is to implement this in the function
that outputs the warnings: currently it just received some kind of
string, which is not very amenable to what we want, but if you change it
to take a more structured description of the warning, then it might be
doable (tho maybe it won't happen at the right place, I don't know).
Stefan
next prev parent reply other threads:[~2009-11-10 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 2:25 bug#4837: with-fewer-warnings ? Glenn Morris
2009-10-31 8:49 ` Eli Zaretskii
2009-11-01 2:31 ` Richard Stallman
2009-11-09 8:45 ` Glenn Morris
2009-11-09 14:38 ` Stefan Monnier
2009-11-10 2:09 ` Glenn Morris
2009-11-10 17:58 ` Stefan Monnier [this message]
2019-06-12 14:55 ` Lars Ingebrigtsen
2019-06-12 16:13 ` Glenn Morris
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=jwvr5s6xo2s.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=4837@emacsbugs.donarmstrong.com \
--cc=rgm@gnu.org \
--cc=rms@gnu.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 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).