unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mathias Dahl" <mathias.dahl@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: put value last in *Help* buffer for C-h v?
Date: Mon, 26 Mar 2007 15:33:59 +0200	[thread overview]
Message-ID: <7dbe73ed0703260633i312eedebt31a3a1413cd4db45@mail.gmail.com> (raw)
In-Reply-To: <BDEIJAFNGDOAGCJIPKPBAEHNCDAA.drew.adams@oracle.com>

> 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

  reply	other threads:[~2007-03-26 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 20:45 put value last in *Help* buffer for C-h v? Drew Adams
2007-03-26 13:33 ` Mathias Dahl [this message]
2007-03-26 15:12   ` Drew Adams
2007-03-27 11:16     ` Mathias Dahl
2007-03-26 23:14   ` Richard Stallman
2007-03-27 11:18     ` Mathias Dahl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7dbe73ed0703260633i312eedebt31a3a1413cd4db45@mail.gmail.com \
    --to=mathias.dahl@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).