From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, handa@m17n.org
Subject: Re: translation-table-for-input
Date: Sat, 31 Jan 2009 11:02:25 +0200 [thread overview]
Message-ID: <upri3zw4e.fsf@gnu.org> (raw)
In-Reply-To: <jwveiykfdqs.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Kenichi Handa <handa@m17n.org>, emacs-devel@gnu.org
> Date: Fri, 30 Jan 2009 20:50:50 -0500
>
> > Compiling simple.el curses thusly:
> > In quoted-insert:
> > simple.el:692:22:Warning: `translation-table-for-input' is an obsolete
> > variable (as of Emacs 23.1).
>
> > In zap-to-char:
> > simple.el:3150:21:Warning: `translation-table-for-input' is an obsolete
> > variable (as of Emacs 23.1).
> > simple.el:3151:28:Warning: `translation-table-for-input' is an obsolete
> > variable (as of Emacs 23.1).
>
> > I don't think we want to release Emacs 23 with these warnings. But
> > what should references to `translation-table-for-input' be replaced
> > with? I looked in etc/NEWS, and all it says is that this variable is
> > obsolete, but doesn't offer any advice about the alternatives.
>
> This code is part of the implementation of the feature accessible via
> translation-table-for-input, so removing it would amount to removing
> the feature.
>
> There is no alternative to this feature, BTW. The only use I've ever
> seen for it, was the char-unification we did in Emacs-22, but in
> Emacs-23 we do this unification differently, which is why it's obsolete.
IIUC, you are saying that translation-table-for-input was only ever
used by Emacs itself. In that case, there should be no need to mark
this variable as ``obsolete'', since we already got rid of its
obsolete uses in Emacs. For other uses, this is a useful feature
(according to you), so marking it ``obsolete'' is simply misleading.
> 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.
We could say something in the doc string, but what would that be?
``don't use this variable for character unification''?
next prev parent reply other threads:[~2009-01-31 9:02 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 ` Eli Zaretskii [this message]
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 ` 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=upri3zw4e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=monnier@iro.umontreal.ca \
/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).