From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Parital scrolling of image
Date: Sun, 23 Jan 2005 22:42:24 +0100 [thread overview]
Message-ID: <x5oeffvn3z.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")
[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]
storm@cua.dk (Kim F. Storm) writes:
> David Kastrup <dak@gnu.org> writes:
>
>> 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.
Another note: when I execute scroll-down at the following screen shot
(where point is just at the bottom) I get "beginning of buffer"
signalled as an error and nothing changes (I have made sure that this
behavior will also occur when pre-command-hook and post-command-hook
are not modified by preview-latex, so they are not at fault here). As
you can see from the scroll bar, this is patently absurd: there are at
least four more screens of material worth, and although there are
quite a few images in there, there are a lot of positions in between
where point could stop if needed. This is the standard "circ.tex"
file as delivered with the preview-latex package. I don't consider
including the screen shot a shootable offense, since it is just 12kB.
Probably the pixel-based movement routines should more or less
calculate a maximum they should not exceed in movement (overshooting
by more than a screen certainly is bad), as well as a minimum they
should at least progress, and if "sane" movement does not land within
that area, then vscroll gets adjusted instead.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
[-- Attachment #2: scroll.png --]
[-- Type: image/png, Size: 12207 bytes --]
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2005-01-23 21:42 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5oeffvn3z.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 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.