unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 16 Nov 2017 01:13:30 -0800	[thread overview]
Message-ID: <pnik1yq37t1.fsf@bow.cs.hmc.edu> (raw)
In-Reply-To: <5A0D54A1.3020307@gmx.at> (martin rudalics's message of "Thu, 16 Nov 2017 10:04:33 +0100")

Caveat: the testing has all been on my desktop at work, so I can't 
run new tests at this instant and am working from memory.

> Do the flashes occur only when you load init.el or also when 
> using the
> --iconic --geometry 80x78+1180+0 switches only?

My memory is that they happen at all times when using --iconic.

>>> emacs -Q --iconic --geometry 80x78+1180+0 --font
>>> "-misc-fixed-bold-r-normal-*-15-*-100-100-*-*-ISO8859-1"
>>
>> This works correctly, but the geometry reported by xwininfo is
>> 79x77+100+0 (which is related to my Emacs.geometry Xrdb setting
>> rather than my gnuemacs.geometry).
>
> Do you mean that both sizes are off by one - 80/79 and 78/77 ? 
> What do

Yes, the size should be 80x78 and instead comes up as 79x77. 
Weird, huh?

> M-: (frame-width) RET
>
> and
>
> M-: (frame-height)

I'll try to remember to try those tomorrow.

> in such a frame give?  Did you remove/comment out the resource 
> settings?
> IIRC Emacs combines everything it finds and applies the last 
> settings it
> read.

When running without -Q, I used grep to remove resource settings 
from my master parameter file and reloaded that into X11 with 
xrdb.

>>> emacs -Q --iconic --load ~/init.el
>>
>> works entirely correctly with the first init.el (including 
>> correct X
>> placement).
>>
>>> emacs -Q --load ~/init.el
>>
>> works entirely correctly with the second init.el.
>
> So apart from the flashes these would be OK?

Yes.  And I never would have noticed the flashes if I hadn't been 
testing; they're under 1/10 second and happen when I'm logging in 
every morning.

>>> Also, please tell me what
>>> your original scenario gives with the line specifying the font 
>>> setting
>>> removed from the resource file.
>>
>> That one still fails.
>
> "still" in the sense that you get the same bad width?  Does 
> removing the
> font setting change _anything_ in the appearance of the frame?

Yes, the same bad width.  I'll check carefully tomorrow to see 
whether there is any frame change.
-- 
    Geoff Kuenning   geoff@cs.hmc.edu 
    http://www.cs.hmc.edu/~geoff/

Statistics don't bore people, people bore people.





  reply	other threads:[~2017-11-16  9:13 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 [this message]
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
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=pnik1yq37t1.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).