From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: handa@m17n.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: translation-table-for-input
Date: Sat, 07 Feb 2009 12:50:05 +0200 [thread overview]
Message-ID: <ubptettb6.fsf@gnu.org> (raw)
In-Reply-To: <E1LUI3f-0003W8-Vd@fencepost.gnu.org>
> From: Richard M Stallman <rms@gnu.org>
> Date: Tue, 03 Feb 2009 04:59:07 -0500
> Cc: eliz@gnu.org, emacs-devel@gnu.org, handa@m17n.org
>
> 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.
>
> Yes, but it's rare that another warning occurs in the same small piece
> of code.
I ended up removing the make-obsolete-variable call for
translation-table-for-input, and instead added a blurb to its doc
string to discourage its use for unification purposes.
next prev parent reply other threads:[~2009-02-07 10:50 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 ` translation-table-for-input Stefan Monnier
2009-02-03 9:59 ` translation-table-for-input Richard M Stallman
2009-02-07 10:50 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ubptettb6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.