From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
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, 03 May 2013 22:25:56 +0300 [thread overview]
Message-ID: <83haijn9vf.fsf@gnu.org> (raw)
In-Reply-To: <89CF77401D72463FB388F000A0008788@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <rudalics@gmx.at>, <eenliu@gmail.com>, <14326@debbugs.gnu.org>
> Date: Fri, 3 May 2013 11:19:25 -0700
>
> I thought you said that to resize the frame when it has been maximized one does
> NOT need to first unmaximize it: just go ahead and change the frame parameters
> that establish the new size.
Yes.
> And I thought you said that trying to resize the frame by using `set-frame-font'
> (with nil KEEP-SIZE: the default) would be an exception to this. To resize the
> frame using `set-frame-font' you would first need to unmaximize the frame.
Yes.
> If I understand correctly so far then my question is why resizing the frame
> using `set-frame-font' (with nil KEEP-SIZE) should be an exception.
Because the frame is maximized, which means the user _wants_ it to
stay that way.
> `set-frame-font' resizes the frame, by default, if the new font size is
> different. That is what it is supposed to do.
I asked _you_ why would _you_ want that. The fact that someone at
some point thought KEEP-SIZE should be nil by default, including in
maximized frames (which, btw, didn't exist at that time) does not mean
this is the absolute truth. Do _you_ have any reasons to believe that
default is justified?
> `set-frame-font' is one way of changing the frame size
No, it's just a way to change the font.
next prev parent reply other threads:[~2013-05-03 19:25 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83haijn9vf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14326@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eenliu@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.