unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 27932@debbugs.gnu.org
Subject: bug#27932: 26.0.50; Feature request: prevent scroll commands from changing the buffer location of point
Date: Sat, 05 Aug 2017 09:44:57 +0300	[thread overview]
Message-ID: <83mv7ewm1i.fsf@gnu.org> (raw)
In-Reply-To: <E1ddkGN-0000cn-0D@fencepost.gnu.org> (message from Richard Stallman on Fri, 04 Aug 2017 17:36:07 -0400)

> From: Richard Stallman <rms@gnu.org>
> CC: dmoncayo@gmail.com, 27932@debbugs.gnu.org
> Date: Fri, 04 Aug 2017 17:36:07 -0400
> 
>   > It would require a complete rewrite of most of the display engine
>   > code.  The Emacs display engine is based on the principle that point
>   > should always be visible, so whenever it becomes invisible, Emacs
>   > scrolls the window to make it visible again.
> 
> I don't think the change would be terribly hard.  One would have to
> find the places that insist on putting point on the screen, but I
> think the changes required in each of those places would not be big.

The number of such places got a lot larger than it was when you were
more actively hacking Emacs, because over the years some users (Dani
included) requested more and more accuracy in that direction.

As for whether the changes in those places are hard, depends on how
well the person who'll do that understands what the code they are
looking at is doing, and why.  The answer might not always be obvious.

And then there are higher-level issues, like what does this mode mean
when scroll-conservatively is in effect.

> If someone wants to try it, I encourage per to try it.

Me too.  In fact, I'd encourage even smaller changes related to the
display code, so that we have more people who can make changes there
than we do now.





  reply	other threads:[~2017-08-05  6:44 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 [this message]
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
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=83mv7ewm1i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27932@debbugs.gnu.org \
    --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).