From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.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 10:24:21 -0800 [thread overview]
Message-ID: <5B662D61FFDD4245AB78878FE8993AB5@us.oracle.com> (raw)
In-Reply-To: <AANLkTinDBvgy7KhJddQQfZPbtbEq1kwHk+AoEp1=nsW8@mail.gmail.com>
> > 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?
Yes, but that's the last part of what I wrote: "then we decide what to do".
And, a priori at least, that decision is the same anytime a window is resized.
IOW, a priori there is nothing special in that regard about fitting a window to
a buffer.
> > 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?
I don't know, but that question is a general one and independent of _this_
bug/feature, which is fitting a window to its displayed buffer.
You are bringing in extraneous stuff. Interesting stuff no doubt, but not
specific to fitting a window to its buffer.
> 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?
No I don't. No doubt window experts such as Martin have some ideas and have
already considered the question. My point is that it is outside the scope of
this thread. _Any_ time a window is resized the questions you raise are
pertinent - they have nothing in particular to do with _this_ resizing of a
window.
> > 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.)
I repeat. I don't see why this resizing is any different from any other window
resizing.
next prev parent reply other threads:[~2011-01-12 18:24 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
2011-01-12 18:24 ` Drew Adams [this message]
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5B662D61FFDD4245AB78878FE8993AB5@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7822@debbugs.gnu.org \
--cc=lennart.borgman@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.