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:03:31 +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> 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 1225224336 30622 80.91.229.12 (28 Oct 2008 20:05:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 28 Oct 2008 20:05:36 +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:06:36 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 1Kuuop-0005kT-ML for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 21:05:52 +0100 Original-Received: from localhost ([127.0.0.1]:38235 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kuuni-0006vm-5R for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 16:04:26 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kuumu-0006iU-T6 for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:03:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kuumt-0006hq-Aq for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:03:36 -0400 Original-Received: from [199.232.76.173] (port=33254 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kuumt-0006hh-0l for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:03:35 -0400 Original-Received: from nf-out-0910.google.com ([64.233.182.188]:4257) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kuums-0007C6-CQ for emacs-devel@gnu.org; Tue, 28 Oct 2008 16:03:34 -0400 Original-Received: by nf-out-0910.google.com with SMTP id c7so1214998nfi.26 for ; Tue, 28 Oct 2008 13:03:32 -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=6eAo/s2MxX9H9OJ/RxdpTSm53E4h+uVaewFDFa7ZDvg=; b=KMNOK2JHomWy12zk5OB/prk8qVuBp/hcyBOr+6bcX7l6TdYRPYLbjtfJGMBKkciCZ6 tVL/gpyHiouCK3bTSLKyd0LT5G0qaWtbqcRtDM3LZuEnxj7ST0gqL3nswqqdFk/EWMYa IePTwpVyNzegV0vhamq4sOMsWgqpM4y4ykW/o= 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=BSAVDyf8+TEHv6xMMW1QZG6qcv3lAnZ7Uhj5yWmPAtBv1eV9oLfDPpk9MXPkz7AjMq GiZuUELbCQDK7zk5EWrAd1mMNA8U2zAawXOAFJ4GcgRha+6iz8UqKEcUhSE2CJJvPZ0c TKFBl+5lPGVqrAqIhzzmAXD0h/SKkMyIRDG+8= Original-Received: by 10.86.74.4 with SMTP id w4mr4905046fga.2.1225224211838; Tue, 28 Oct 2008 13:03:31 -0700 (PDT) Original-Received: by 10.86.65.3 with HTTP; Tue, 28 Oct 2008 13:03:31 -0700 (PDT) In-Reply-To: <005301c93936$4a358b10$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:105101 Archived-At: On Tue, Oct 28, 2008 at 8:49 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.