From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: eli@barzilay.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Proposal to improve the nomenclature of scrolling directions
Date: Sat, 10 Nov 2012 13:38:35 +0200 [thread overview]
Message-ID: <83r4o1y9fo.fsf@gnu.org> (raw)
In-Reply-To: <509E3504.1050500@gmx.at>
> Date: Sat, 10 Nov 2012 12:05:40 +0100
> From: martin rudalics <rudalics@gmx.at>
> Cc: Eli Barzilay <eli@barzilay.org>, emacs-devel@gnu.org
>
> AFAICT scrolling is partially implemented in the scroll functions and
> partially in the display engine.
True.
> For me, implementing a thing like
> `scroll-in-place' means to leave the scroll functions mainly untouched -
> we'd just record the original window-point and window-start positions
> there. Then we need a `scroll-point' overlay for the "line is too
> short" case (Kim Storm has implemented a similar feature in his
> rectangle code) and adjust it in a `post-display' hook - the one you've
> been asking for in the past decade. Also, that `post-display' hook
> would have to optionally handle the case where scrolling gets back to
> the original point and the user wants the window-start position to match
> the position it had before the scrolling sequence started.
You are talking about a solution that would work around the current
code in creative ways. I would suggest changing the code instead.
Changing the code will necessarily involve touching the scroll
functions, because currently they move point to fit in the window.
next prev parent reply other threads:[~2012-11-10 11:38 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201211080338.qA83c7NY006393@winooski.ccs.neu.edu>
[not found] ` <20635.16010.769769.433949@winooski.ccs.neu.edu>
2012-11-08 16:48 ` Proposal to improve the nomenclature of scrolling directions Stefan Monnier
2012-11-09 9:50 ` martin rudalics
2012-11-09 14:17 ` Stefan Monnier
2012-11-09 15:27 ` Eli Barzilay
2012-11-10 11:05 ` martin rudalics
2012-11-10 11:38 ` Eli Zaretskii [this message]
2012-11-10 14:09 ` martin rudalics
2012-11-10 14:40 ` Eli Zaretskii
2012-11-10 18:49 ` martin rudalics
2012-11-06 17:55 Dmitry Gutov
2012-11-07 0:53 ` Richard Stallman
2012-11-07 15:17 ` Drew Adams
2012-11-07 16:23 ` Eli Zaretskii
2012-11-07 18:03 ` Drew Adams
2012-11-07 18:34 ` Eli Zaretskii
2012-11-07 21:00 ` Drew Adams
2012-11-07 21:17 ` Eli Zaretskii
2012-11-08 22:18 ` Daniel Hackney
2012-11-07 21:12 ` Mathias Dahl
2012-11-07 21:41 ` Dmitry Gutov
2012-11-08 19:26 ` Bruce Korb
2012-11-13 9:07 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2012-11-04 14:10 Dani Moncayo
2012-11-04 14:37 ` Stefan Monnier
2012-11-04 15:00 ` Dani Moncayo
2012-11-04 17:07 ` Juanma Barranquero
2012-11-04 17:30 ` Dani Moncayo
2012-11-04 17:31 ` Eli Zaretskii
2012-11-04 17:35 ` Dani Moncayo
2012-11-04 18:23 ` Eli Zaretskii
2012-11-04 19:10 ` Dani Moncayo
2012-11-04 19:39 ` Eli Zaretskii
2012-11-04 20:01 ` Dani Moncayo
2012-11-05 11:07 ` Richard Stallman
2012-11-05 12:25 ` Dani Moncayo
2012-11-05 14:56 ` Nix
2012-11-05 15:39 ` Teemu Likonen
2012-11-07 8:12 ` Harald Hanche-Olsen
2012-11-13 9:05 ` Bastien
2012-11-13 17:05 ` Stefan Monnier
2012-11-05 3:29 ` Stephen J. Turnbull
2012-11-05 7:27 ` Dani Moncayo
2012-11-05 12:44 ` Jambunathan K
2012-11-05 2:44 ` Stefan Monnier
2012-11-05 7:24 ` Dani Moncayo
2012-11-05 23:32 ` Stefan Monnier
2012-11-06 21:29 ` Daniel Hackney
2012-11-05 11:06 ` Richard Stallman
2012-11-05 15:00 ` Nix
2012-11-06 1:25 ` Stephen J. Turnbull
2012-11-06 17:24 ` Adrian Robert
2012-11-06 17:36 ` Eli Zaretskii
2012-11-06 17:50 ` Drew Adams
2012-11-06 19:14 ` John Yates
2012-11-05 18:05 ` Daniel Hackney
2012-11-06 1:53 ` Stephen J. Turnbull
2012-11-07 16:31 ` Nix
2012-11-08 1:49 ` Stefan Monnier
2012-11-08 17:33 ` Nix
2012-11-08 18:14 ` Eli Barzilay
2012-11-08 18:18 ` Nix
2012-11-08 18:39 ` Eli Barzilay
2012-11-08 18:39 ` Stefan Monnier
2012-11-09 9:50 ` martin rudalics
2012-11-09 14:18 ` Stefan Monnier
2012-11-08 18:40 ` Eli Zaretskii
2012-11-08 18:48 ` Juanma Barranquero
2012-11-08 19:29 ` Eli Zaretskii
2012-11-09 2:52 ` Richard Stallman
2012-11-09 7:35 ` Eli Zaretskii
2012-11-09 14:20 ` Nix
2012-11-09 14:56 ` Eli Zaretskii
2012-11-09 20:24 ` Nix
2012-11-10 11:09 ` martin rudalics
2012-11-10 11:40 ` Eli Zaretskii
2012-11-10 14:11 ` martin rudalics
2012-11-10 0:13 ` Richard Stallman
2012-11-10 7:42 ` Eli Zaretskii
2012-11-10 11:09 ` martin rudalics
2012-11-10 11:45 ` Eli Zaretskii
2012-11-10 11:48 ` Nix
2012-11-10 14:38 ` Eli Zaretskii
2012-11-10 14:47 ` Nix
2012-11-10 14:10 ` martin rudalics
2012-11-10 14:49 ` Eli Zaretskii
2012-11-10 18:50 ` martin rudalics
2012-11-10 19:09 ` Eli Zaretskii
2012-11-10 11:10 ` martin rudalics
2012-11-10 11:46 ` Eli Zaretskii
2012-11-10 14:12 ` martin rudalics
2012-11-09 9:51 ` martin rudalics
2012-11-09 14:19 ` Stefan Monnier
2012-11-10 11:05 ` martin rudalics
2012-11-08 7:18 ` Stephen J. Turnbull
2012-11-08 11:12 ` Stephen Leake
2012-11-08 15:43 ` Drew Adams
2012-11-08 17:35 ` Nix
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=83r4o1y9fo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eli@barzilay.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).