From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: eliz@gnu.org, handa@m17n.org, emacs-devel@gnu.org
Subject: Re: translation-table-for-input
Date: Sun, 01 Feb 2009 16:46:28 -0500 [thread overview]
Message-ID: <jwvhc3d96gq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1LTVqz-0001Zb-UY@fencepost.gnu.org> (Richard M. Stallman's message of "Sun, 01 Feb 2009 01:30:49 -0500")
> These `obsolete' warnings are a general problem: we have no way to say
> "yes, I know this variable is obsolete, but this is the implementation
> rather than a use of the feature". The closest we have is
> with-no-warnings, which is a rather blunt tool.
> It is not blunt if you use it around a small piece of code
> with a comment to explain why.
It still silences any other warning that might occur (e.g. in the
future) in that same small piece of code. So it's still blunt.
Stefan
next prev parent reply other threads:[~2009-02-01 21:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 14:22 translation-table-for-input Eli Zaretskii
2009-01-31 1:50 ` translation-table-for-input Stefan Monnier
2009-01-31 9:02 ` translation-table-for-input Eli Zaretskii
2009-01-31 17:08 ` translation-table-for-input Stefan Monnier
2009-02-01 6:30 ` translation-table-for-input Richard M Stallman
2009-02-01 21:46 ` Stefan Monnier [this message]
2009-02-03 9:59 ` translation-table-for-input Richard M Stallman
2009-02-07 10:50 ` translation-table-for-input Eli Zaretskii
2009-02-08 2:00 ` translation-table-for-input Glenn Morris
2009-02-08 4:12 ` translation-table-for-input Eli Zaretskii
2009-02-12 21:58 ` translation-table-for-input Stefan Monnier
2009-02-13 10:38 ` translation-table-for-input Eli Zaretskii
2009-02-13 14:27 ` translation-table-for-input Stefan Monnier
2009-02-13 15:25 ` translation-table-for-input Eli Zaretskii
2009-02-13 15:54 ` translation-table-for-input Stefan Monnier
2009-02-14 9:09 ` translation-table-for-input Eli Zaretskii
2009-02-14 21:17 ` translation-table-for-input Stefan Monnier
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=jwvhc3d96gq.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).