emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#8874: closed (Redisplay confusion in Info, due to


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#8874: closed (Redisplay confusion in Info, due to recentering fix)
Date: Tue, 23 Aug 2011 10:50:02 +0000

Your message dated Tue, 23 Aug 2011 13:40:00 +0300
with message-id <address@hidden>
and subject line Re: bug#8874: Redisplay confusion in Info, due to recentering 
fix
has caused the GNU bug report #8874,
regarding Redisplay confusion in Info, due to recentering fix
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
8874: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8874
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Redisplay confusion in Info, due to recentering fix Date: Wed, 15 Jun 2011 16:22:34 -0400
Recipe to reproduce:

emacs -q
M-: (setq scroll-conservatively 300) RET
C-h i
m CC mode RET
C-s k&r
C-s C-s C-s C-s

Emacs redisplay now shows a garbage window with no cursor.  C-l redraws
the window correctly.

This is caused by the recentering changes from March (revision 103792).
Reverting it eliminates the bug.



--- End Message ---
--- Begin Message --- Subject: Re: bug#8874: Redisplay confusion in Info, due to recentering fix Date: Tue, 23 Aug 2011 13:40:00 +0300
> From: Chong Yidong <address@hidden>
> Cc: address@hidden
> Date: Sat, 18 Jun 2011 14:07:10 -0400
> 
> Eli Zaretskii <address@hidden> writes:
> 
> > How urgent is it to fix this?  Can it be postponed until I'm done with
> > bidi reordering of display strings, and we enter code freeze?
> 
> The bidi work is more urgent, so feel free to postphone the fix for this
> until you have the time.
> 
> FWIW, I took a quick look, and it appears that the following should do
> the trick.  But it can wait till you have time to double-check the code.

The problem was with the header line that Info uses by default, and
which was not accounted for when computing the new window start
position.  (If you set Info-use-header-line to nil, the bug goes
away.)

I fixed (in trunk revision 105541) the calculation of the window start
to account for the header line when it's present, and that solves the
bug.

Thanks.


--- End Message ---

reply via email to

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