unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Parital scrolling of image
Date: Mon, 24 Jan 2005 14:59:33 +0100	[thread overview]
Message-ID: <m3llajorlm.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <x57jm4vt4m.fsf@lola.goethe.zz> (David Kastrup's message of "Sun, 23 Jan 2005 20:32:25 +0100")

David Kastrup <dak@gnu.org> writes:

> 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.

I tried various things with your circ.tex, but I cannot reproduce this
with my latest fixes.  Please test again -- and if you can still
reproduce it, pls. tell me how (and what is unintuitive about the
results you see).

>
> 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.

I fixed this for pixel-based scrolling.  

I have also fixed a redisplay loop where resizing the frame that
displays your circ.tex with graphics loops trying to make the cursor
line fully visible.

>
> This should be a general paradigm: all window-based movement/scrolling
> commands should make _some_ progress, and in the _expected_ direction.

True.

>
> 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.

Inside the image, previous-line does scroll backwards.

It is true that if you use previous-line to move into a tall image
you get to the first part of that image rather than the last part
as you would expect.   I will see what I can do about it.

>
> That being said, the behavior we now have for next-line is much much
> better than what was available at any previous time.

I think so too.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2005-01-24 13:59 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 [this message]
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=m3llajorlm.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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).