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: Thu, 30 Oct 2008 07:06:43 +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 1225346824 11494 80.91.229.12 (30 Oct 2008 06:07:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 30 Oct 2008 06:07:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Kevin Rodgers" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 30 07:08:05 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 1KvQhN-00036Y-Nz for ged-emacs-devel@m.gmane.org; Thu, 30 Oct 2008 07:08:02 +0100 Original-Received: from localhost ([127.0.0.1]:45729 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KvQgG-00046x-Sf for ged-emacs-devel@m.gmane.org; Thu, 30 Oct 2008 02:06:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KvQgA-00046F-Pp for emacs-devel@gnu.org; Thu, 30 Oct 2008 02:06:46 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KvQg9-00045J-C2 for emacs-devel@gnu.org; Thu, 30 Oct 2008 02:06:45 -0400 Original-Received: from [199.232.76.173] (port=44078 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KvQg9-000459-8c for emacs-devel@gnu.org; Thu, 30 Oct 2008 02:06:45 -0400 Original-Received: from fg-out-1718.google.com ([72.14.220.155]:28957) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KvQg8-0004NJ-Cd for emacs-devel@gnu.org; Thu, 30 Oct 2008 02:06:44 -0400 Original-Received: by fg-out-1718.google.com with SMTP id l26so384352fgb.30 for ; Wed, 29 Oct 2008 23:06:43 -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=L17hvdijrphgy7oIJm+HAHi33RZtRHJTu0bQdGicLRg=; b=PJqHyWA584f4XkCxPuhzGmoQEvwNA6VtkSj1oBQx0cgtIUOxgxVpYyG6l6IYFuy2AH e3QhdjSu0vKCtnK6gKZX9Zixez2LohVs5aDaz4qQX+iwpsWGFIY9AOPMCl92jY/KEsUd 94GwvaStQhmbaJuS3t+N1IUoGGcuqmi9judf8= 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=x3NTUuJbwJq5qlfKlYcuTifu7zC5VoQqQdnmTT/wH8iMp7C06zuyLwpEj5vITnRTKD xh8hp6ELCoFzfpEl3esThlLTDQea1BeQFk/uZ2/I8xEndBluGOKM76y3ZItyMsZwCxfz 3EgEe3s+Hgfa8o2jBjXEf47u47EIJHEP0CFFU= Original-Received: by 10.86.92.4 with SMTP id p4mr6617860fgb.36.1225346803294; Wed, 29 Oct 2008 23:06:43 -0700 (PDT) Original-Received: by 10.86.65.3 with HTTP; Wed, 29 Oct 2008 23:06:43 -0700 (PDT) In-Reply-To: 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:105166 Archived-At: On Thu, Oct 30, 2008 at 6:01 AM, Kevin Rodgers wrote: > Lennart Borgman wrote: >> >> 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). > > Would it make sense to display long values in the same way as evaluation > results in the *scratch* buffer? i.e. with text properties that allow > the user to toggle between the abbreviated value and the complete value. To me it looks like a good idea.