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

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

[debbugs-tracker] bug#6385: closed (A slightly less aggressive fit-windo


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#6385: closed (A slightly less aggressive fit-window-to-buffer)
Date: Tue, 11 Oct 2011 09:32:01 +0000

Your message dated Tue, 11 Oct 2011 11:31:01 +0200
with message-id <address@hidden>
and subject line Re: A slightly less aggressive fit-window-to-buffer
has caused the debbugs.gnu.org bug report #6385,
regarding A slightly less aggressive fit-window-to-buffer
to be marked as done.

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


-- 
6385: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6385
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: A slightly less aggressive fit-window-to-buffer Date: Wed, 9 Jun 2010 20:56:51 +0200
I believe fit-window-to-buffer has become a bit upset and unnecessary
aggressive because of visual lines. It looks like it need a bit more
feedback from the display system to be really sure that the buffer is
entirely visible.

The attached patch is something I have used to get around the problem.
I am not sure it is the right thing but I am rather sure it does not
hurt.

Too see the problem it tries to fix just call the function with a
buffer larger than window and point below the window bottom (you have
to write a bit elisp code for that).

Of course we need a non-killing version of fit-window-to-buffer, but
for the moment this patch might be useful.

Attachment: windows-less-aggressive-fit-1.diff
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: A slightly less aggressive fit-window-to-buffer Date: Tue, 11 Oct 2011 11:31:01 +0200 User-agent: Thunderbird 2.0.0.21 (Windows/20090302)
> Of course we need a non-killing version of fit-window-to-buffer, but
> for the moment this patch might be useful.

`fit-window-to-buffer' doesn't kill windows any more so this issue
should have been resolved.

martin


--- End Message ---

reply via email to

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