all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Proper behavior of C-u 3 C-v
Date: Sun, 16 Aug 2020 12:30:08 +0200	[thread overview]
Message-ID: <877dty993j.fsf@ebih.ebihd> (raw)
In-Reply-To: 87h7t3xm2u.fsf@gnu.org

Amin Bandali wrote:

> The doc string is indeed clear, but I personally
> wouldn't have expected that behaviour. I'm curious
> if there's a particular reason why C-v deviates
> from the convention of other similar movement
> commands, where specifying a numerical ARG `n'
> would have the effect of performing that command's
> action `n' times (e.g. M-3 M-f to move forward
> three words).

Another inconsistency is

  (scroll-down 1)
  (scroll-up   1)

where one expects the byte-compiler to say, use
(scroll 1) and (scroll -1) instead, but it doesn't,
and for good reason because there isn't
a `scroll', even.

And another inconsistency is:

  (scroll-other-window-down 1)
  (scroll-other-window      1)

compared to scroll-up/scroll-down, where -up
is explicit.

But actually, I think that looks better and what
I see nothing stops you from using
(scroll-other-window -X) instead of
(scroll-other-window-down X). It is also more clear
since people have different ideas what up and down,
but just "scroll" everyone can agree means "read on".

BTW civilized scrolling, one step at a time,
including horizontally:

  https://dataswamp.org/~incal/emacs-init/scroll.el

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal




  reply	other threads:[~2020-08-16 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14 23:50 Proper behavior of C-u 3 C-v rgrant
2020-08-15 16:29 ` Eli Zaretskii
2020-08-16  4:15   ` Amin Bandali
2020-08-16 10:30     ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-08-16 14:33     ` Eli Zaretskii

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=877dty993j.fsf@ebih.ebihd \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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.