From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Dave Abrahams <dave@boostpro.com>
Cc: "10920@debbugs.gnu.org" <10920@debbugs.gnu.org>
Subject: bug#10920: 24.0.93; Poor response to display size changes
Date: Sat, 3 Mar 2012 18:04:43 +0100 [thread overview]
Message-ID: <55763E33-611C-42D1-ADDF-1A7CA35753D3@swipnet.se> (raw)
In-Reply-To: <m2mx7xvg74.fsf@pluto.luannocracy.com>
Hello.
3 mar 2012 kl. 16:48 skrev Dave Abrahams:
>
> on Sat Mar 03 2012, Jan Djärv <jan.h.d-AT-swipnet.se> wrote:
>
>> Hello.
>>
>> 1 mar 2012 kl. 15:56 skrev Dave Abrahams <dave@boostpro.com>:
>>
>>>
>>> It seems to me:
>>>
>>> * When the display size changes, any visible frames that aren't completely
>>> visible should be moved/resised so they are
>>
>> This is not as easy as it seems. If you have Emacs spanning several
>> monitors and one of them changes it is not obvious what to do. One
>> could special case it for the single monitor case I guess.
>
> It may have not been easy 15-20 years ago, but today it is a solved
> problem. Many other applications have worked out ways to deal with such
> changes. Emacs could simply emulate one of those.
Can you give an example of an application that behaves sane when spread out over four monitors and one of them changes?
>
>>> * The same goes for "fullscreen" (which IIUC is only supported via a
>>> patch that lives outside emacs, but I mention it here for
>>> completeness).
>>>
>>
>> The 10.7 style fullscreen does not have this problem, which is an
>> argument for just supporting that type of fullscreen in 24.2.
>
> Not really, IMO. On the mac there's a green button in the upper left of
> every application window that maximizes it. You have to respond to that
> button somehow and maximizing the frame is the right (and consistent)
> response.
Maximizing and fullscreen is not the same thing.
Jan D.
next prev parent reply other threads:[~2012-03-03 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 14:56 bug#10920: 24.0.93; Poor response to display size changes Dave Abrahams
2012-03-03 14:12 ` Jan Djärv
2012-03-03 15:48 ` Dave Abrahams
2012-03-03 17:04 ` Jan Djärv [this message]
2012-03-03 19:08 ` Dave Abrahams
2012-04-09 10:05 ` Jan Djärv
2012-04-09 13:32 ` Dave Abrahams
2012-04-09 14:27 ` Jan D.
2012-04-09 14:55 ` Dave Abrahams
2012-04-09 18:55 ` Jan D.
2012-04-09 14:13 ` Dave Abrahams
2012-04-09 18:53 ` Jan D.
2022-02-20 13:41 ` Lars Ingebrigtsen
2022-02-20 16:30 ` Dave Abrahams
2022-02-21 14:01 ` Lars Ingebrigtsen
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=55763E33-611C-42D1-ADDF-1A7CA35753D3@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=10920@debbugs.gnu.org \
--cc=dave@boostpro.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).