From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Mathias Dahl" Newsgroups: gmane.emacs.devel Subject: Re: put value last in *Help* buffer for C-h v? Date: Mon, 26 Mar 2007 15:33:59 +0200 Message-ID: <7dbe73ed0703260633i312eedebt31a3a1413cd4db45@mail.gmail.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1174916057 22215 80.91.229.12 (26 Mar 2007 13:34:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 26 Mar 2007 13:34:17 +0000 (UTC) Cc: Emacs-Devel To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 26 15:34:11 2007 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 1HVpKp-0004Br-4z for ged-emacs-devel@m.gmane.org; Mon, 26 Mar 2007 15:34:07 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HVpN4-0007Jf-0x for ged-emacs-devel@m.gmane.org; Mon, 26 Mar 2007 08:36:26 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HVpN0-0007HG-93 for emacs-devel@gnu.org; Mon, 26 Mar 2007 09:36:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HVpMy-0007Dr-N8 for emacs-devel@gnu.org; Mon, 26 Mar 2007 09:36:21 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HVpMy-0007Di-JC for emacs-devel@gnu.org; Mon, 26 Mar 2007 08:36:20 -0500 Original-Received: from ug-out-1314.google.com ([66.249.92.174]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HVpKi-0002BK-RM for emacs-devel@gnu.org; Mon, 26 Mar 2007 09:34:01 -0400 Original-Received: by ug-out-1314.google.com with SMTP id j3so1743562ugf for ; Mon, 26 Mar 2007 06:33:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=l+en+4yw+abU9lB5ZgaEVQNo2Zv/SJYKwWZTISHT9MFPfizvfvLLLB0eos0icuIa6bhzpFxILsPoSl6yDSy9GK5UYnh2a/Ld6zEbHC/vhMW3ISaNl/DpZKdmmEArVu94Se5t0/+BEuylm8sHwFdIJbOAJAifThPrIrESF58KP/4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WozDXKhBvsl8AoUVr1nXY3J7/gI8qVjcJGXJkkkI3Btgp3T0O67rgBGLu8amQ9gVRZsQ6gFxVCU3kgjjvi916zli9UKmCIJwFzs6OL8WxThz5LtKYLUJ1viY1zPB2XceRmiSTpWvG1wqhJC9T655znjZPlDK/MChpempqScxw4Y= Original-Received: by 10.78.158.11 with SMTP id g11mr2978771hue.1174916039360; Mon, 26 Mar 2007 06:33:59 -0700 (PDT) Original-Received: by 10.78.12.3 with HTTP; Mon, 26 Mar 2007 06:33:59 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-kernel: Linux 2.4-2.6 (Google crawlbot) 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:68601 Archived-At: > I wonder if it wouldn't be better to systematically put the variable's value > last in the *Help* buffer for `C-h v'? I think I agree. It is a bit strange to see the value at the beginning of the buffer sometimes and sometimes not (because it is "large"). Shouldn't we strive for a consistent user interface if we can? > but wouldn't it always be best to put the value last? The information about > the local and global values, and the [back] button, are more convenient if > presented before the value, no? I agree, it seems logical to keep all information about the variable together, in one block. > We might also consider placing a second [back] button after the value, if it > is longer than, say, 50 lines. I have no strong opinion on this apart from thinking that this too is inconsistent; as a user I want to be able to trust that the same user interface widgets are available each time I execute a certain operation. However, I it might look goofy to see something like this: [back] Value: t [back] /Mathias