From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.bugs Subject: bug#3526: 23.0.94; `list-character-sets' display Date: Wed, 17 Jun 2009 09:13:22 -0700 Message-ID: <0BC1AA42727545459F59E04016F62801@us.oracle.com> References: <8385521F908145EE8D60682CEAB9D7D1@us.oracle.com> <3057BD2C673B48079D31AC58DBF72C08@us.oracle.com> <0F745F1932EF4338B8D737D20FB2B94F@us.oracle.com> <4A39120F.9070806@gnu.org> Reply-To: Drew Adams , 3526@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1245257323 25215 80.91.229.12 (17 Jun 2009 16:48:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 17 Jun 2009 16:48:43 +0000 (UTC) To: "'Jason Rumney'" , <3526@emacsbugs.donarmstrong.com> Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Jun 17 18:48:39 2009 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MGyJT-0000iS-8T for geb-bug-gnu-emacs@m.gmane.org; Wed, 17 Jun 2009 18:48:39 +0200 Original-Received: from localhost ([127.0.0.1]:36654 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGyJS-0000Zk-Lt for geb-bug-gnu-emacs@m.gmane.org; Wed, 17 Jun 2009 12:48:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGy8f-0007qQ-4k for bug-gnu-emacs@gnu.org; Wed, 17 Jun 2009 12:37:29 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGy8Z-0007kR-TM for bug-gnu-emacs@gnu.org; Wed, 17 Jun 2009 12:37:28 -0400 Original-Received: from [199.232.76.173] (port=37354 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGy8Z-0007k6-Ms for bug-gnu-emacs@gnu.org; Wed, 17 Jun 2009 12:37:23 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:42801) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MGy8Z-0001Ce-1s for bug-gnu-emacs@gnu.org; Wed, 17 Jun 2009 12:37:23 -0400 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with ESMTP id n5HGbKww019878; Wed, 17 Jun 2009 09:37:21 -0700 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.14.3/8.14.3/Submit) id n5HGK6Z3016742; Wed, 17 Jun 2009 09:20:06 -0700 X-Loop: owner@emacsbugs.donarmstrong.com Resent-From: "Drew Adams" Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs Resent-Date: Wed, 17 Jun 2009 16:20:05 +0000 Resent-Message-ID: Resent-Sender: owner@emacsbugs.donarmstrong.com X-Emacs-PR-Message: followup 3526 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by 3526-submit@emacsbugs.donarmstrong.com id=B3526.124525520515569 (code B ref 3526); Wed, 17 Jun 2009 16:20:05 +0000 Original-Received: (at 3526) by emacsbugs.donarmstrong.com; 17 Jun 2009 16:13:25 +0000 X-Spam-Bayes: score:0.5 Bayes not run. spammytokens:Tokens not available. hammytokens:Tokens not available. Original-Received: from rgminet11.oracle.com (rcsinet11.oracle.com [148.87.113.123]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with ESMTP id n5HGDK8Y015559 for <3526@emacsbugs.donarmstrong.com>; Wed, 17 Jun 2009 09:13:21 -0700 Original-Received: from rgminet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rgminet11.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n5HGEGCS026494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Jun 2009 16:14:18 GMT Original-Received: from abhmt004.oracle.com (abhmt004.oracle.com [141.146.116.13]) by rgminet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n5HGDHak018914; Wed, 17 Jun 2009 16:13:17 GMT Original-Received: from dradamslap1 (/141.144.73.196) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 17 Jun 2009 09:13:09 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4A39120F.9070806@gnu.org> Thread-Index: AcnvZD09VBt4kRg4Td+4cKpicYFIlgAAEuOA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Source-IP: abhmt004.oracle.com [141.146.116.13] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A010208.4A391618.005D:SCFSTAT5015188,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Resent-Date: Wed, 17 Jun 2009 12:37:28 -0400 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:28779 Archived-At: Your changes look good to me, Jason. > > Some of the charsets listed as supplementary are obsolete; > > they were used in Emacs versions prior to version 23. > > > > [Is that correct? If so, why not get rid of these here? Why > > show stuff that is no longer in Emacs?] > > I think charsets like mule-unicode-0100-23ff, which existed > in previous versions because of technical restrictions on the > size of charsets, may be referred to by old lisp code, so we > need to keep them around for compatibility. That we need, for backward compatibility, to keep around code that is not used by the current version is one thing. That doesn't mean, however, that we should show those charsets to the Emacs 23 user in a help display. I can't judge whether that display could be useful to Emacs 23 users or not - it's your call. Typically, only the current release is described in user doc (and in the UI). Compatibility issues are sometimes called out in the doc, but more often that is done in release notes (e.g. NEWS). > >> To find out which charset a character in the buffer belongs to, > > > > To find out which charset a character belongs to, > > Since the described function acts on a character in a buffer, I think > the original wording is correct. "the buffer" confuses more than it helps here, IMO. It could easily be taken to refer to the list-charsets display buffer, given the context so far. And "put point before it and type @kbd{C-u C-x =}" can only apply to a character in a (displayed) buffer anyway, so "in the buffer" is redundant at best and confusing at worst. But if this sentence is moved, as I suggested, so that the context is no longer the list charsets display, then that possible confusion can be removed. Personally, I would say just this: "To show the charset of the character at point, use @kbd{C-u C-x =}." There is no need to describe, in addition, how to make a given character become the character at point.