From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: option doc strings and Customize tags Date: Tue, 28 Oct 2008 13:25:01 -0700 Message-ID: <005401c9393b$41ee26b0$0200a8c0@us.oracle.com> References: <005601c9385f$86a998c0$c2b22382@us.oracle.com> <4907637E.8090402@gmx.at> <005201c93933$6bd2eb30$0200a8c0@us.oracle.com> <005301c93936$4a358b10$0200a8c0@us.oracle.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 1225225617 2984 80.91.229.12 (28 Oct 2008 20:26:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 28 Oct 2008 20:26:57 +0000 (UTC) Cc: 'martin rudalics' , emacs-devel@gnu.org To: "'Lennart Borgman'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 28 21:27:58 2008 connect(): Connection refused 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 1KuvAO-0005vM-K2 for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 21:27:53 +0100 Original-Received: from localhost ([127.0.0.1]:60020 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kuv9H-0005HP-NB for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 16:26:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kuv7p-0004dg-7H for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:25:13 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kuv7m-0004cE-5T for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:25:12 -0400 Original-Received: from [199.232.76.173] (port=45596 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kuv7l-0004c6-Ti for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:25:09 -0400 Original-Received: from agminet01.oracle.com ([141.146.126.228]:23593) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Kuv7l-00054s-JB for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:25:10 -0400 Original-Received: from rgmgw2.us.oracle.com (rgmgw2.us.oracle.com [138.1.186.111]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id m9SKP0wr027121; Tue, 28 Oct 2008 15:25:00 -0500 Original-Received: from acsmt707.oracle.com (acsmt707.oracle.com [141.146.40.85]) by rgmgw2.us.oracle.com (Switch-3.2.4/Switch-3.2.4) with ESMTP id m9SKOwUE005577; Tue, 28 Oct 2008 14:24:58 -0600 Original-Received: from dradamslap1 (/24.23.165.218) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 28 Oct 2008 20:24:58 +0000 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: Ack5OEQV3YIKJacAR1WwltPhAu9WkQAAkOCQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 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:105107 Archived-At: > >> >> > nil Case-sensitive > >> >> > t Case-insensitive > >> >> > Use default > >> >> > >> >> I'd put the Lisp values in parentheses as > >> >> > >> >> Case-sensitive (nil) > >> >> Case-insensitive (t) > >> >> Use default > >> > > >> > Sure, fine, whatever. It doesn't matter much what format we > >> > use. Except that adding parens might confuse things for Lisp > >> > values that are lists: ((foo bar)). > >> > > >> > A more general formatting problem is that the Lisp values > >> > might be quite long. Some kind of abbreviation is probably > >> > called for. > >> > >> A link that is opened in *Help* and shows the value with an > >> explanation where it came from? > > > > Possibly. But the point here is to show all of the possible > > values *together*. You don't want to click a button/link and > > open *Help* for each possible value, to see its Lisp value > > separately from the others. > > > > A single display of all tags and their Lisp values (in > > *Help* or elsewhere) is what's needed. See the original > > suggestion. > > I meant that for the long values only. But the buffer that shows the > long value can show all the values together. If it shows all of the values together, then there is no sense in showing it "for the long values only". The point is to show all of the values, for comparison and comprehension, whenever you try to look at any of them (even a short one). For the need to see the values together, it's irrelevant whether a value is long or short. Perhaps you are saying that if all values are short enough then no separate display is needed - they can be shown in the menu. But if even one value is long (whatever "long" means), then a separate display is needed.