From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Parital scrolling of image
Date: Sun, 23 Jan 2005 20:32:25 +0100 [thread overview]
Message-ID: <x57jm4vt4m.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3r7kdt14d.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Sun, 23 Jan 2005 01:55:46 +0100")
storm@cua.dk (Kim F. Storm) writes:
> David Kastrup <dak@gnu.org> writes:
>
>> 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),
>
> I have checked in some patches to fix this. Please try again.
This looks much better. But here are some remarks:
a) an "open preview" that starts on a line of its own in preview-latex
has an overlay starting at the beginning of the line. This overlay
has a before-string consisting of an image (display-property on a
single x character IIRC) followed by \n (so that the image will appear
on a line of its own). Note that the image as well as the \n are not
connected to a character in the buffer, but appear just as
before-string. Nevertheless, previous-line in the first _real_ line
of the overlay will be sufficiently confused as to not move at all.
Never. This effect is probably not related to the very latest
changes, though. I just noticed it when playing with the new code.
It leads to pretty unintuitive results, though.
b) Making a window as small as possible (2 lines or so) means that
scroll-down and scroll-up, that are supposed to scroll by a "near full
screen", namely `next-screen-context-lines' less than a full screen,
scroll, if at all, in the opposite direction than expected. In case
that the `next-screen-context-lines' less than a full screen delivers
a negative or zero value, 1 should rather be substituted.
This should be a general paradigm: all window-based movement/scrolling
commands should make _some_ progress, and in the _expected_ direction.
c) when pressing next-line, an image will get scrolled in smaller
chunks (by the way, maybe one should be able to configure the size of
those chunks). That is nice. previous-line shows no such behavior,
however: it scrolls an image with one big jump. A bit of symmetry
here would probably be nice to have.
That being said, the behavior we now have for next-line is much much
better than what was available at any previous time.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-01-23 19:32 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
2005-01-23 0:55 ` Kim F. Storm
2005-01-23 19:32 ` David Kastrup [this message]
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=x57jm4vt4m.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).