[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: vertical-motion]

From: Kim F. Storm
Subject: Re: address@hidden: vertical-motion]
Date: Mon, 28 Aug 2006 00:41:55 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

David Kastrup <address@hidden> writes:

> There have been so many changes in that area that it would be hard to
> point to any particular one.  There was progressive deterioration.
> There was even a time where the screen display and the behavior could
> get out of sync (the cursor displays at a different point than it
> behaves) and I am not sure this has not occured recently.
> Since you said no fixes where intended before the release, I stopped
> actively checking for things like that since it would only annoy me to
> no good cause.

.. unless I can find some way to fix it which isn't too complex ..

If you can provide more test cases that I can look at, maybe I can
find the right fix.

> And there are things where clicking on some highlighted line (probably
> not fully visible) will cause the line to jump away in some manner of
> recentering, thus evading the click action, and jump back afterwards.
> Sort of click-avoidance-mode.

This is news to me.  So examples please!

I have fixed a few redisplay issues with "cursors outside visible part
of window" -- one of those might have broken image display or behaviour
with highlighting.

> I just don't understand how stuff like that tests as an improvement.

Fixing one bug often leads to another bug -- so please report problems
that you think are related to _recent_ changes.

  It's a bit annoying for the to be told that fixes I might have made
a year ago broke something else, and I wasn't told at the time -- now
I have to use a lot of time to find out what changes may have broken

>>> The last bug reports I sent in were basically met with "this is not
>>> going to get fixed before the release".
>> I would like to fix it ... but this is not trivial, and I've yet to
>> find a good way to do it (which doesn't break a lot of other code).

And now you tell me, that things degraded gradually, so there are
probably several things that influences the current bad behaviour.
Which is actually also my experience with trying to solve it. :-(

>> Do forward-char / backward-char work better in these cases??
> Irrelevant.  I use the equivalent of auto-reveal-mode on
> forward-char/backward-char.

Too bad -- as I have found that using those keys typically
do scroll images in cases where the scrolling commands don't.

So far, I've found that it is primarily the scrolling commands which
are broken -- often they make false decisions when chosing a new
window start in the presense of a partially visible image.

I'll give fixing it another shot this week.

Kim F. Storm <address@hidden> http://www.cua.dk

reply via email to

[Prev in Thread] Current Thread [Next in Thread]