From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: Parital scrolling of image Date: Mon, 24 Jan 2005 14:59:33 +0100 Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1106577007 31746 80.91.229.6 (24 Jan 2005 14:30:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Jan 2005 14:30:07 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 24 15:30:00 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Ct5E6-0005mt-00 for ; Mon, 24 Jan 2005 15:29:58 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ct5QJ-0005a7-8y for ged-emacs-devel@m.gmane.org; Mon, 24 Jan 2005 09:42:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ct5PY-0005Ix-NI for emacs-devel@gnu.org; Mon, 24 Jan 2005 09:41:48 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ct5Et-0002ny-Ol for emacs-devel@gnu.org; Mon, 24 Jan 2005 09:30:57 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ct5Ep-0002hD-VZ for emacs-devel@gnu.org; Mon, 24 Jan 2005 09:30:44 -0500 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.34) id 1Ct4kZ-0002ZF-4Q for emacs-devel@gnu.org; Mon, 24 Jan 2005 08:59:27 -0500 Original-Received: (qmail 68525 invoked from network); 24 Jan 2005 13:59:26 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 24 Jan 2005 13:59:26 -0000 Original-To: David Kastrup In-Reply-To: (David Kastrup's message of "Sun, 23 Jan 2005 20:32:25 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:32529 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:32529 David Kastrup 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 http://www.cua.dk