From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman" Newsgroups: gmane.emacs.devel Subject: Re: option doc strings and Customize tags Date: Tue, 28 Oct 2008 21:29:12 +0100 Message-ID: References: <005601c9385f$86a998c0$c2b22382@us.oracle.com> <4907637E.8090402@gmx.at> <005201c93933$6bd2eb30$0200a8c0@us.oracle.com> <005301c93936$4a358b10$0200a8c0@us.oracle.com> <005401c9393b$41ee26b0$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1225225778 3511 80.91.229.12 (28 Oct 2008 20:29:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 28 Oct 2008 20:29:38 +0000 (UTC) Cc: martin rudalics , emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 28 21:30:39 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 1KuvD3-0006m6-Vo for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 21:30:38 +0100 Original-Received: from localhost ([127.0.0.1]:33285 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KuvBw-0006Ki-Lz for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 16:29:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KuvBm-0006HQ-Dn for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:29:18 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KuvBl-0006H9-Er for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:29:18 -0400 Original-Received: from [199.232.76.173] (port=45742 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KuvBl-0006H6-9h for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:29:17 -0400 Original-Received: from ey-out-1920.google.com ([74.125.78.147]:34925) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KuvBk-0006KN-L9 for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:29:17 -0400 Original-Received: by ey-out-1920.google.com with SMTP id 4so1164391eyg.24 for ; Tue, 28 Oct 2008 13:29:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=xr4orJRJ41KAwR/yGtbUMBk44qq83U9cRnvae+sYa7A=; b=OisborkuCzRQ7VrfTjzmyS4AUQcK87ioNvXpVjDJY5wBi2J7XHEXI0actiIDZT2Yum 4f34Uy5gLNveOGhbuaYk/FqFx/YZDqCa2wp+k9OnAD0qwWsDhhmz21hXIjlbgr5J41m7 adcd29lR+cPzP82jin5PWJVGe0vNmbl4Lwpos= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=MLqWXgYDTuU15h+ejFOHaxMIofFuh59VfsrDaLRpKTXS/TKkYmU2rcLlM0bzbDPvAS IWuLWqb8vzSXLlYcQ3DOi2/U6m67j09ih+1YHpWHsS3+C0TPIZDxR+cAiT9Ke6NQyCwE Ciqm81rSBHWypUS9NT7GvbPGlhlHVcOBlXVko= Original-Received: by 10.86.95.20 with SMTP id s20mr4899397fgb.39.1225225752374; Tue, 28 Oct 2008 13:29:12 -0700 (PDT) Original-Received: by 10.86.65.3 with HTTP; Tue, 28 Oct 2008 13:29:12 -0700 (PDT) In-Reply-To: <005401c9393b$41ee26b0$0200a8c0@us.oracle.com> Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:105108 Archived-At: On Tue, Oct 28, 2008 at 9:25 PM, Drew Adams wrote: >> >> >> > 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. What I tried to say is: - In the initial display show all values together, but replace the long values with a link. - This link should lead to a second display (in *Help*) where also all values are shown together. Here the long values should of course be shown. There should also be a short explanation what this display is about (and a link back, but that is nearly automatic if the first display is in *Help* too).