From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: translation-table-for-input Date: Sat, 31 Jan 2009 11:02:25 +0200 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1233392572 6773 80.91.229.12 (31 Jan 2009 09:02:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 31 Jan 2009 09:02:52 +0000 (UTC) Cc: emacs-devel@gnu.org, handa@m17n.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 31 10:04:06 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LTBll-0003hc-IA for ged-emacs-devel@m.gmane.org; Sat, 31 Jan 2009 10:04:05 +0100 Original-Received: from localhost ([127.0.0.1]:52755 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LTBkS-0007J5-Ji for ged-emacs-devel@m.gmane.org; Sat, 31 Jan 2009 04:02:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LTBkM-0007J0-PX for emacs-devel@gnu.org; Sat, 31 Jan 2009 04:02:38 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LTBkM-0007Io-23 for emacs-devel@gnu.org; Sat, 31 Jan 2009 04:02:38 -0500 Original-Received: from [199.232.76.173] (port=59359 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LTBkL-0007Il-SL for emacs-devel@gnu.org; Sat, 31 Jan 2009 04:02:37 -0500 Original-Received: from mtaout1.012.net.il ([84.95.2.1]:27589) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LTBkL-00082v-7z for emacs-devel@gnu.org; Sat, 31 Jan 2009 04:02:37 -0500 Original-Received: from conversion-daemon.i-mtaout1.012.net.il by i-mtaout1.012.net.il (HyperSendmail v2007.08) id <0KEB00L00VHMM400@i-mtaout1.012.net.il> for emacs-devel@gnu.org; Sat, 31 Jan 2009 11:02:54 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([77.126.109.18]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KEB00F3BVSID140@i-mtaout1.012.net.il>; Sat, 31 Jan 2009 11:02:44 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 9.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:108451 Archived-At: > From: Stefan Monnier > Cc: Kenichi Handa , 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''?