From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Luc Teirlinck <teirllm@dms.auburn.edu>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: gnus/html2text.el
Date: Tue, 26 Oct 2004 21:35:28 -0400 [thread overview]
Message-ID: <87acu9osia.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3oeipun6c.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Wed, 27 Oct 2004 00:31:07 +0200")
>>> Perhaps we should arrange for byte-compile to warn about use
>>> of these functions from Lisp code. What do people think of that?
>>
>> That sounds like a good idea. We need a way to cleanly turn off the
>> message, but for end-of-buffer we can use (call-interactively
>> 'end-of-buffer).
> (with-no-warnings (end-of-buffer))
OK, that's a possibility. It would be better to have something more
specific so that it is clear what is happening. Specificity becomes
relevant in cases like:
(with-no-warnings (ent-of-buffer))
which will not give you the warning you'd want to get.
Maybe `with-no-warnings' should take an extra argument listing the kind of
warning to ignore.
Stefan
next prev parent reply other threads:[~2004-10-27 1:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 2:46 gnus/html2text.el Luc Teirlinck
2004-10-25 17:18 ` gnus/html2text.el Reiner Steib
2004-10-26 9:04 ` gnus/html2text.el Richard Stallman
2004-10-26 16:43 ` gnus/html2text.el Stefan Monnier
2004-10-26 22:31 ` gnus/html2text.el Kim F. Storm
2004-10-27 1:35 ` Stefan Monnier [this message]
2004-10-27 1:43 ` gnus/html2text.el Luc Teirlinck
2004-10-27 3:08 ` gnus/html2text.el Stefan Monnier
2004-10-27 3:24 ` gnus/html2text.el Luc Teirlinck
2004-10-27 3:32 ` gnus/html2text.el Luc Teirlinck
2004-10-27 1:45 ` gnus/html2text.el Miles Bader
2004-10-27 17:35 ` gnus/html2text.el Richard Stallman
2004-10-27 2:43 ` gnus/html2text.el Luc Teirlinck
2004-10-27 3:02 ` gnus/html2text.el Luc Teirlinck
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=87acu9osia.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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).