From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: eenliu@gmail.com, 14326@debbugs.gnu.org
Subject: bug#14326: 24.3; Conflict of w32-send-sys-command and set-default-font
Date: Fri, 3 May 2013 13:31:24 -0700 [thread overview]
Message-ID: <4DBCC1F8F1BA4204B449175E8357EAC7@us.oracle.com> (raw)
In-Reply-To: <83ehdnn7ge.fsf@gnu.org>
> > > For example, increasing the font size should not make a
> > > maximized frame larger than the screen. We're kidding users
> > > with such behavior.
> >
> > 1. Your argument here applies to any size increase beyond
> > the screen size, not just doing that via `set-frame-font'.
> > So it is irrelevant as an argument why resizing via
> > `set-frame-font' should be an exception.
>
> It _is_ relevant, because Martin's argument applies not only to
> increasing maximized frames, but also to decreasing their size as
> well, as side effect of any change except an explicit change in frame
> dimensions.
What argument? That is the conclusion, but what is the argument supporting it?
> IOW, when the frame is maximized, only explicitly changing its height
> or width, or explicitly un-maximizing it, should
Should why? That's the question. Haven't seen an answer yet.
> ever affect the frame's size. Any other changes, such as font change or
> adding/removing scroll bars or fringes -- should
Should why?
> leave the frame at the same pixel dimensions, i.e. still maximized.
All of that just repeats the claim; it does not support it.
That is the claim for which I am asking for a supporting reason.
You have also generalized beyond just `set-frame-font' (the only exception
mentioned until now, AFAIK), BTW. Now it is apparently not just
`set-frame-font' that is the exception but any way of resizing other than
"explicitly changing its height or width, or explicitly un-maximizing it".
My question remains, in any case: What is the _reason_ why such ways of resizing
should be neutered? What is the _reason_ why "explicitly changing its height or
width, or explicitly un-maximizing it" should be the only way of changing the
size?
There might be a good reason for such a claim, but I've seen none advanced, so
far. "X because X" is no support for X: it just assumes the conclusion.
next prev parent reply other threads:[~2013-05-03 20:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 1:34 bug#14326: 24.3; Conflict of w32-send-sys-command and set-default-font Eric Liu
2013-05-01 9:15 ` martin rudalics
2013-05-01 15:02 ` Eli Zaretskii
2013-05-01 17:33 ` Eric Liu
2013-05-01 17:37 ` Eli Zaretskii
2013-05-02 9:23 ` martin rudalics
2013-05-02 17:08 ` Eli Zaretskii
2013-05-02 18:32 ` martin rudalics
2013-05-02 18:55 ` Eli Zaretskii
2013-05-02 19:08 ` martin rudalics
2013-05-02 19:38 ` Eli Zaretskii
2013-05-03 6:48 ` martin rudalics
2013-05-03 7:12 ` Eli Zaretskii
2013-05-03 7:28 ` martin rudalics
2013-05-03 14:59 ` Drew Adams
2013-05-03 15:48 ` Eli Zaretskii
2013-05-03 15:54 ` Eli Zaretskii
2013-05-03 16:26 ` Drew Adams
2013-05-03 18:04 ` Eli Zaretskii
2013-05-03 18:19 ` Drew Adams
2013-05-03 19:25 ` Eli Zaretskii
2013-05-03 18:59 ` martin rudalics
2013-05-03 20:06 ` Drew Adams
2013-05-03 20:18 ` Eli Zaretskii
2013-05-03 20:31 ` Drew Adams [this message]
2013-05-04 6:37 ` Eli Zaretskii
2013-05-04 7:50 ` martin rudalics
2013-05-04 14:17 ` 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=4DBCC1F8F1BA4204B449175E8357EAC7@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=14326@debbugs.gnu.org \
--cc=eenliu@gmail.com \
--cc=eliz@gnu.org \
/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).