unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 7822@debbugs.gnu.org
Subject: bug#7822: 24.0.50; `fit-window-to-buffer': take display artefacts into account
Date: Wed, 12 Jan 2011 18:55:47 +0100	[thread overview]
Message-ID: <AANLkTinDBvgy7KhJddQQfZPbtbEq1kwHk+AoEp1=nsW8@mail.gmail.com> (raw)
In-Reply-To: <476E17C645D142EEB115E2021ACAD92F@us.oracle.com>

On Wed, Jan 12, 2011 at 4:11 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> To be more clear: I was taking into account to few windows. All
>> windows below and above must be taken into account.
>
> I don't see why _any_ windows should be taken into account.  The window for the
> buffer should be resized to fit the displayed buffer, period.  If that is not
> possible for some reason, then we decide what to do.

Hm. Just because you have to actually do the resizing and that affects
other windows and a decision has to be made how?

> For that decision, I would imagine that we decide the same way we decide now
> when you try to resize a window to size S and that is not possible.  Why is this
> case any different from other resizing cases?

Do we really have good ways to easily solve this? Maybe I am missing
something? Perhaps you have some specific suggestion for how to do
this? Which functions do you think supply the needed features?

> AFAICT, all that's involved here is to determine the desired window size.
> Beyond that, there should be nothing new.

One little detail of course: It should not delete other windows. (If
you allow it do delete other windows there are much simpler
implementations than the one I am suggesting. Much simpler.)





  reply	other threads:[~2011-01-12 17:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  0:21 bug#7822: 24.0.50; `fit-window-to-buffer': take display artefacts into account Drew Adams
2011-01-11  4:40 ` Lennart Borgman
2011-01-12  2:14   ` Lennart Borgman
2011-01-12  3:16     ` Drew Adams
2011-01-12 10:40       ` Lennart Borgman
2011-01-12 11:33         ` Lennart Borgman
2011-01-12 15:11           ` Drew Adams
2011-01-12 17:55             ` Lennart Borgman [this message]
2011-01-12 18:24               ` Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2008-11-14 22:46 bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows Themba Fletcher
2014-09-21 18:02 ` martin rudalics
2014-09-22  9:02   ` bug#7822: 24.0.50; `fit-window-to-buffer': take display artefacts into account martin rudalics
2014-09-22 14:02     ` Drew Adams
2014-09-22 17:42       ` martin rudalics
2014-09-22 18:24         ` Drew Adams
2014-09-22 19:31           ` Stefan Monnier
2014-09-22 20:24             ` Drew Adams
2014-09-22 20:54               ` Stefan Monnier
2014-09-22 21:04                 ` Drew Adams

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='AANLkTinDBvgy7KhJddQQfZPbtbEq1kwHk+AoEp1=nsW8@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=7822@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).