unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 27932@debbugs.gnu.org, rms@gnu.org
Subject: bug#27932: 26.0.50; Feature request: prevent scroll commands from changing the buffer location of point
Date: Mon, 07 Aug 2017 19:38:16 +0300	[thread overview]
Message-ID: <83bmnrtjt3.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0iPd==2KmqvEKM4wOPn1ext5cQYqKTU8v4-nz0x31JUxg@mail.gmail.com> (message from Dani Moncayo on Mon, 7 Aug 2017 07:54:21 +0200)

> From: Dani Moncayo <dmoncayo@gmail.com>
> Date: Mon, 7 Aug 2017 07:54:21 +0200
> Cc: "Richard M. Stallman" <rms@gnu.org>, 27932@debbugs.gnu.org
> 
> In short: point movement should trigger auto-scrolling (as now), but
> scrolling should not move point.

I see a possible misunderstanding here: the way scrolling works in
Emacs, it moves point and then lets the display engine scroll the text
in the window to make point visible.  So the two use cases you try to
differentiate are actually indistinguishable as far as the display
engine is concerned.  For example, invoking goto-char invokes the same
display code as scrolling commands, which is why scroll-conservatively
is obeyed even by goto-char (as many users expect).





  parent reply	other threads:[~2017-08-07 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 13:34 bug#27932: 26.0.50; Feature request: prevent scroll commands from changing the buffer location of point Dani Moncayo
2017-08-03 16:42 ` Eli Zaretskii
     [not found]   ` <CAH8Pv0gjYZZAfciNTaqKcj37C51dSdJOzD+4AZFFY2wjOu6Fgg@mail.gmail.com>
     [not found]     ` <83ini3yi49.fsf@gnu.org>
2017-08-04  6:34       ` Dani Moncayo
2017-08-04 21:36   ` Richard Stallman
2017-08-05  6:44     ` Eli Zaretskii
2017-08-05 20:19       ` Richard Stallman
2017-08-06 17:18         ` Eli Zaretskii
2017-08-06 21:00           ` Dani Moncayo
2017-08-07  2:28             ` Eli Zaretskii
2017-08-07  5:54               ` Dani Moncayo
2017-08-07 12:32                 ` Tak Kunihiro
2017-08-07 16:38                 ` Eli Zaretskii [this message]
2017-08-07 21:09                   ` Dani Moncayo
2017-08-03 17:56 ` martin rudalics
2017-08-03 23:16 ` Tak Kunihiro
2017-08-04  6:15   ` Eli Zaretskii
2017-08-04  6:39     ` Tak Kunihiro
2017-08-04  8:01       ` Eli Zaretskii
2017-08-04 10:33         ` Tak Kunihiro

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=83bmnrtjt3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27932@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=rms@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).