From: Geoff Kuenning <geoff@cs.hmc.edu>
To: martin rudalics <rudalics@gmx.at>
Cc: 27923@debbugs.gnu.org
Subject: bug#27923: 24.3; -iconic switch screws up geometry
Date: Fri, 17 Nov 2017 01:31:34 -0800 [thread overview]
Message-ID: <pnih8tt5k09.fsf@bow.cs.hmc.edu> (raw)
In-Reply-To: <5A0EAAAA.7000402@gmx.at> (martin rudalics's message of "Fri, 17 Nov 2017 10:23:54 +0100")
>> Sorry, bad typing on my part. 35/34 was the height.
>>
>>>> Anyway, I finally got down to the following two lines:
>>>>
>>>> (menu-bar-mode -1)
>>>> (set-default-font (x-get-resource "Font" ""))
>>>
>>>> With both of those present, I get the absurdly narrow
>>>> frame. If I
>>>> remove the first, then I get a frame that's 38x78. If I
>>>> leave the
>>>> first and remove the second, I get a teeny frame that's too
>>>> small to
>>>> type in, but xwininfo reports it as 1x1 (so suppose emacs
>>>> thinks it's
>>>> 2x2). And if I remove both, I get a properly sized
>>>> frame. (This is
>>>> all with my xrdb restored, BTW.)
>
> So are you getting a weird height, a weird width, independently
> both or
> simultaneously both?
Sometimes normal height, tiny width (that's what prompted the
original bug report). Sometimes both weird height and weird
width. I don't think I've seen a normal width with a weird height
but I might be misremembering.
>> It would be wonderful if the bug
>> went away on its own!
>
> Do they ever?
Heisenbugs!
More seriously, not without help from talented developers...
--
Geoff Kuenning geoff@cs.hmc.edu
http://www.cs.hmc.edu/~geoff/
It's is not, it isn't ain't, and it's it's, not its, if you mean
it
is. If you don't, it's its. Then too, it's hers. It isn't
her's. It
isn't our's either. It's ours, and likewise yours and theirs.
-- Oxford University Press, Edpress News
next prev parent reply other threads:[~2017-11-17 9:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 20:41 bug#27923: 24.3; -iconic switch screws up geometry Geoff Kuenning
2017-08-17 9:22 ` martin rudalics
[not found] ` <pniziawo843.fsf@bow.cs.hmc.edu>
2017-08-19 9:55 ` martin rudalics
2017-11-15 0:12 ` Geoff Kuenning
2017-11-16 9:04 ` martin rudalics
2017-11-16 9:13 ` Geoff Kuenning
2017-11-16 9:29 ` martin rudalics
2017-11-16 23:20 ` Geoff Kuenning
2017-11-17 8:53 ` martin rudalics
2017-11-16 23:16 ` Geoff Kuenning
2017-11-17 8:52 ` martin rudalics
2017-11-17 8:59 ` Geoff Kuenning
2017-11-17 9:23 ` martin rudalics
2017-11-17 9:31 ` Geoff Kuenning [this message]
2022-02-21 15:32 ` Lars Ingebrigtsen
2022-02-21 22:53 ` Geoff Kuenning
2022-02-22 1:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-22 13:24 ` Lars Ingebrigtsen
2022-02-23 9:28 ` martin rudalics
2022-02-23 22:17 ` Geoff Kuenning
2022-02-24 9:16 ` Lars Ingebrigtsen
2022-02-24 17:55 ` Geoff Kuenning
2022-02-24 18:07 ` Lars Ingebrigtsen
2022-02-24 9:19 ` martin rudalics
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=pnih8tt5k09.fsf@bow.cs.hmc.edu \
--to=geoff@cs.hmc.edu \
--cc=27923@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).