unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r99831: Scrolling commands which does not signal errors at top/bottom.
Date: Tue, 06 Apr 2010 03:59:47 +0300	[thread overview]
Message-ID: <877hol5qso.fsf@mail.jurta.org> (raw)
In-Reply-To: <g2kf7ccd24b1004051751mccf92185pe841b9e578b9b4b2@mail.gmail.com> (Juanma Barranquero's message of "Tue, 6 Apr 2010 02:51:17 +0200")

> How do these commands interact with `scroll-preserve-screen-position'?

Exactly as documented in the docstring of `scroll-preserve-screen-position':

  A value of t means point keeps its screen position if the scroll
  command moved it vertically out of the window, e.g. when scrolling
                              =================
  by full screens.

and in the Info manual:

     Some users like the full-screen scroll commands to keep point at the
  same screen position.  To enable this behavior, set the variable
  `scroll-preserve-screen-position' to a non-`nil' value.  Then, whenever
  a command scrolls the text around point offscreen (or within
                                          =========
  `scroll-margin' lines of the edge), Emacs moves point to keep it at the
  same vertical and horizontal position within the window.

i.e. this option doesn't apply when point stays on the same screen.

-- 
Juri Linkov
http://www.jurta.org/emacs/




  reply	other threads:[~2010-04-06  0:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NywTs-00007U-Lf@internal.in.savannah.gnu.org>
2010-04-06  0:51 ` [Emacs-diffs] /srv/bzr/emacs/trunk r99831: Scrolling commands which does not signal errors at top/bottom Juanma Barranquero
2010-04-06  0:59   ` Juri Linkov [this message]
2010-04-06  1:58     ` Juanma Barranquero
2010-04-06 16:12       ` Juri Linkov
2010-04-06 18:26         ` Juanma Barranquero
2010-04-06 20:19           ` Juri Linkov
2010-04-06 20:49             ` Juanma Barranquero
2010-04-06 21:06               ` Juri Linkov
2010-04-06 21:39                 ` Juanma Barranquero
2010-04-06 21:47                   ` Juanma Barranquero
2010-04-07 20:17                     ` Juri Linkov
2010-04-07 22:16                       ` Juanma Barranquero
2010-04-07 23:19                         ` Juri Linkov
2010-04-07 23:35                           ` Juanma Barranquero
2010-04-09 15:29                       ` Stefan Monnier
2010-04-09 22:46                         ` Juri Linkov
2010-04-10 14:51                           ` Stefan Monnier
2010-04-14 16:49                             ` Juri Linkov
2010-04-15  4:41                               ` Stefan Monnier
2010-04-15 23:56                                 ` Juri Linkov
2010-04-16  0:41                                   ` Stefan Monnier
2010-04-16  1:27                                     ` Juri Linkov

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=877hol5qso.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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).