all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>,
	"'Eli Zaretskii'" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: proposal to rename scrolling directions up/down as forward/backward [was: scroll-*-aggressively]
Date: Sat, 26 Mar 2011 09:40:53 -0700	[thread overview]
Message-ID: <DC290C1868E74667AF311B8F0D35770E@us.oracle.com> (raw)
In-Reply-To: <yyxr59tontg.fsf@fencepost.gnu.org>

> BTW, I think we should replace ye olde "scroll-up" and "scroll-down"
> terminology with "scroll-forward" and "scroll-backward".

1+

In principle, forward/backward has the same problem as up/down (ambiguous,
depending on what is considered to be moving), but in practice it does not.  

In Emacs, forward/backward generally refers to direction of movement through the
buffer.  The `scroll-up' doc refers to scrolling direction of the text/buffer
movement relative to the view, whereas many users think in terms of window (view
port) movement along the buffer (forward and down).

Renaming the commands to use forward/backward will help for this reason alone
(users think of forward as movement through the text/buffer).

Not sure what the best way of making such a change is, however.  In any case, we
no longer bind `scroll-up' - we bind `scroll-up-command' instead.  I just filed
a doc bug (#8349) about this.

Renaming the commands will no doubt help, but many users will never pay
attention to the command names.  They will use `C-h k' and look at the doc, so
it is especially the doc that needs to be clear.  (It is currently clear and
correct, but users can still become confused by the terminology.)




      parent reply	other threads:[~2011-03-26 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 14:51 scroll-*-aggressively Eli Zaretskii
2011-03-26 16:20 ` scroll-*-aggressively Chong Yidong
2011-03-26 16:40   ` scroll-*-aggressively Óscar Fuentes
2011-03-26 16:40   ` Drew Adams [this message]

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

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

  git send-email \
    --in-reply-to=DC290C1868E74667AF311B8F0D35770E@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.