unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: no-spam@cua.dk (Kim F. Storm)
Subject: Re: scroll-conservatively overflow
Date: 30 Apr 2004 18:38:10 +0200	[thread overview]
Message-ID: <m3vfjhjua5.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87d65p1yxk.fsf@orebokech.com>

Romain Francoise <romain@orebokech.com> writes:

> Romain Francoise <romain@orebokech.com> writes:
> 
> > About scrolling: I've been bitten by a bug for some weeks now, I
> > originally thought it was specific to the multi-tty code but I
> > discovered this morning that it's not.  (A fresh checkout from CVS HEAD
> > this morning exhibited the same issues.)
> 
> I have finally found enough time to track it down.  The change
> responsible for all my scrolling problems is Richard's change to
> indent.c on March 2nd:
> 
> 2004-03-02  Richard M. Stallman  <rms@gnu.org>
> 
> 	* indent.c (compute_motion): Save vpos in prev_vpos, like hpos etc.
> 
> Reverting this change (see attached patch) solves all issues in Dired,
> Gnus, etc.
> 
> I have tried to come up with a fix but failed.  I don't really
> understand why this change was necessary, it adds complexity and does
> not fix anything as far as I can see.  If it was just a code cleanup,
> maybe the best would be to revert it for the time being.

The change was made in response to the following bug report:
The fix was obviously not correct.


Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Place the following in a file named `/tmp/x'
======cut here=====
Barf

        Whee!

Yadda
======cut here=====

(the above contains three lines, no tabs, and no trailing spaces, for
a total of 27 characters)

Now do the following:

* start `emacs -q --no-site-file'

* find the file: C-x C-f /tmp/x RET

* turn on selective-display: C-u C-x $

* attempt to move point forward: C-n C-n

Note that the cursor did not appear to move after the second C-n.
That's the bug; it should have appeared on the third visible line
(right before the `Y').

* sanity check: C-x =

You should see point 6 of 27.

* again attempt to move point forward: C-n

* again sanity check: C-x =

It's still at 6 of 27.

If it matters, you can "un-stick" point by typing C-f, *then* typing
C-n; in that case, point indeed winds up on the third visible line,
where I'd expect it to.


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

  reply	other threads:[~2004-04-30 16:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 10:00 scroll-conservatively overflow Juanma Barranquero
2004-04-16 13:17 ` Kim F. Storm
2004-04-16 14:03   ` Romain Francoise
2004-04-30 11:35     ` Romain Francoise
2004-04-30 16:38       ` Kim F. Storm [this message]
2004-05-01 17:50       ` Richard Stallman
2004-05-02 12:37         ` Romain Francoise
2004-05-02 16:58           ` Stefan Monnier
2004-05-03 14:03           ` Richard Stallman
2004-04-17 19:42   ` Richard Stallman
2004-04-17 20:52     ` Juanma Barranquero
2004-04-18 21:31       ` Kim F. Storm
2004-04-19 11:37       ` Richard Stallman

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=m3vfjhjua5.fsf@kfs-l.imdomain.dk \
    --to=no-spam@cua.dk \
    /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).