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: Sun, 06 Aug 2017 20:18:43 +0300 [thread overview]
Message-ID: <83lgmwty18.fsf@gnu.org> (raw)
In-Reply-To: <E1de5Y8-0000Ws-IM@fencepost.gnu.org> (message from Richard Stallman on Sat, 05 Aug 2017 16:19:52 -0400)
> From: Richard Stallman <rms@gnu.org>
> CC: dmoncayo@gmail.com, 27932@debbugs.gnu.org
> Date: Sat, 05 Aug 2017 16:19:52 -0400
>
> > And then there are higher-level issues, like what does this mode mean
> > when scroll-conservatively is in effect.
>
> Person could try it whichever way is easiest and see if person likes it.
I was thinking about the person who will need to decide how to code
that.
In several places we behave under scroll-conservatively with the
explicit goal of keeping point visible in the very first/last
sufficiently-visible screen line: this might need to be changed if
keeping point visible is no longer a requirement.
next prev parent reply other threads:[~2017-08-06 17:18 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lgmwty18.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 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.