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

[Drew Adams]

>  > 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.
> 
> Yes.  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.

2. See what I said previously about uses of frames larger than the the screen.