unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 11:19:25 -0700	[thread overview]
Message-ID: <89CF77401D72463FB388F000A0008788@us.oracle.com> (raw)
In-Reply-To: <83mwsclz2j.fsf@gnu.org>

> > > > Is the intention that one cannot change the size, once 
> > > > a frame has been maximized (without first unmaximizing it)?
> > > 
> > > There's no such intention.  What Martin is arguing (I think)
> > > was that in a maximized frame, set-default-font should alway 
> > > behave as if its 2nd argument were non-nil.
> > 
> > Why should it?
> > 
> > Especially given the statement that there is no intention 
> > that one must unmaximize a frame before changing its size.
> > 
> > If we impose such a behavior for `set-default-font' then it 
> > means that in that case there _is_ such an intention: one
> > would need to unmaximize the frame first, before using
> > `set-default-font' with nil KEEP-SIZE, to make a nil KEEP-SIZE
> > value (the default!) be respected.  Why such an exception?
> 
> Because the frame is maximized.
> 
> Let me turn the table and ask you: why would you want to have the
> frame resized just because you changed the font?

Perhaps I am misunderstanding.

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.

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.

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.

As to why one might "want to have the frame resized just because you changed the
font": that is precisely the point of `set-frame-size' with nil KEEP-SIZE (which
is the *default* behavior, not some crazy, exceptional behavior).  (More
precisely, resizing the frame is one of the intended effects if the new font
size is different.)

`set-frame-font' resizes the frame, by default, if the new font size is
different.  That is what it is supposed to do.

Since `set-frame-font' is one way of changing the frame size, and (I think) you
said that to resize a maximized frame you need not first unmaximize it, why
should that not be the case also for resizing using `set-frame-font'?






  reply	other threads:[~2013-05-03 18:19 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 [this message]
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
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=89CF77401D72463FB388F000A0008788@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).