From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Parital scrolling of image
Date: Sat, 22 Jan 2005 17:55:28 +0100 [thread overview]
Message-ID: <x5brbh5rpb.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3zmz21bht.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Sat, 22 Jan 2005 02:46:54 +0100")
storm@cua.dk (Kim F. Storm) writes:
> storm@cua.dk (Kim F. Storm) writes:
>
>> A brief message to let you know that I've started to look into
>> the problem of scrolling through images that are higher/wider
>> than the current window.
>>
>> I've already have a working solution for tall images.
>
> I have installed my changes. They modify line-move and
> scroll-up, scroll-down.
>
> If you have problems with this, set auto-window-vscroll to nil.
Cough, cough. If I have a window with the upper half taken up by an
image, and point is in some normal text below the image, then pressing
C-n will _not_ move to the next line (which is perfectly on screen and
quite far from the edge), but instead the window will get vscrolled a
line. This process repeats a few time: just vscrolling happens, but
point does not change the buffer position. At some point of time
which does not appear overly related to how much of the image has
already scrolled off-screen, the image jumps back fully into sight,
and at the same time point moves one line down, finally. If you keep
using C-n, again the very same image will vscroll off the screen for
several keypresses (while point does not change), then jump back to
fully visible at which time point finally moves one line down.
This isn't it yet. As long as point can move down a line without
causing scrolling, it should do so. Only when scrolling would occur
on movement should vscrolling be considered as an alternative to
actually moving point.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-01-22 16:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 23:26 Parital scrolling of image Kim F. Storm
2005-01-21 0:32 ` David Kastrup
2005-01-21 23:57 ` Kim F. Storm
2005-01-21 20:11 ` Richard Stallman
2005-01-22 1:46 ` Kim F. Storm
2005-01-22 16:55 ` David Kastrup [this message]
2005-01-23 0:55 ` Kim F. Storm
2005-01-23 19:32 ` David Kastrup
2005-01-24 13:59 ` Kim F. Storm
2005-01-24 15:02 ` Ralf Angeli
2005-01-24 16:41 ` Ralf Angeli
2005-01-24 20:45 ` Kim F. Storm
2005-01-25 0:01 ` Ralf Angeli
2005-01-24 15:27 ` David Kastrup
2005-02-21 23:15 ` Kim F. Storm
2005-02-22 1:48 ` David Kastrup
2005-01-23 21:42 ` David Kastrup
2005-01-23 23:06 ` David Kastrup
2005-01-24 13:49 ` Kim F. Storm
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=x5brbh5rpb.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@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).