GNU bug report logs - #14326
24.3; Conflict of w32-send-sys-command and set-default-font

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: rudalics <at> gmx.at, 14326 <at> debbugs.gnu.org, eenliu <at> gmail.com
Subject: bug#14326: 24.3; Conflict of w32-send-sys-command and set-default-font
Date: Fri, 03 May 2013 21:04:36 +0300

> From: "Drew Adams" <drew.adams <at> oracle.com>
> Cc: <rudalics <at> gmx.at>, <eenliu <at> gmail.com>, <14326 <at> debbugs.gnu.org>
> Date: Fri, 3 May 2013 09:26:16 -0700
> 
> > > 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.