unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: michael_heerdegen@web.de, 19869@debbugs.gnu.org
Subject: bug#19869: 25.0.50; default-frame-alist: width versus fullheight
Date: Sun, 15 Feb 2015 12:35:52 +0100	[thread overview]
Message-ID: <54E08498.2050603@gmx.at> (raw)
In-Reply-To: <87twyo13h0.fsf@web.de>

 > There is some inconsistent behavior when setting the with of new
 > frames depending on whether fullheight is specified:
 >
 >
 > (progn
 >    (set-face-attribute 'default nil :height 175)
 >    (setq default-frame-alist
 >          '((width . 100)
 >            ;; (fullscreen . fullheight)
 >            ))
 >    (frame-width (make-frame)))  ==> 100
 >
 >
 > OTOH:
 >
 > (progn
 >    (set-face-attribute 'default nil :height 175)
 >    (setq default-frame-alist
 >          '((width . 100)
 >            (fullscreen . fullheight)
 >            ))
 >    (frame-width (make-frame))) ==> 63
 >
 >
 > I would expect that the results are equal.

They are here (Gtk+, Lucid, Motif and Windows) so probably your window
manager interferes in some way.  I tried with your second form as my
.emacs and by evaluating it in *scratch* with emacs -Q.

 > A related bug was #1522, btw.

I'm not sure.  Doesn't your behavior depend on doing
`set-face-attribute' first?.

Anyway, this gives us a good case for doing some forensics.  Please
evaluate

(setq frame-size-history '(1000))

(defun window-display-history ()
   "..."
   (interactive)
   (with-current-buffer-window
    "*history*" nil nil
    (let ((history (cdr frame-size-history))
	 element sizes rest)
      (while history
        (setq element (car history))
        (when (eq (car element) (selected-frame))
	 (when (setq sizes (nth 2 element))
	   (insert (format "%sx%s -> %sx%s "
			   (nth 0 sizes) (nth 1 sizes)
			   (nth 2 sizes) (nth 3 sizes))))
	 (insert (format "%s" (nth 1 element)))
	 (when (setq rest (nth 3 element))
	   (while rest
	     (insert (format " %s" (car rest)))
	     (setq rest (cdr rest))))
	 (insert "\n"))
        (setq history (cdr history)))))
   'history)

in *scratch* and evaluate your second form (the one where you set
fullheight).  Go to the new frame you created this way, type

M-x: window-display-history

in it and post the contents of the *history* buffer here.

If you want to do the same when that form is in your .emacs we'll have
to proceed in a slightly different way.  Let's do that later.

Thanks, martin





  reply	other threads:[~2015-02-15 11:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-14 23:24 bug#19869: 25.0.50; default-frame-alist: width versus fullheight Michael Heerdegen
2015-02-15 11:35 ` martin rudalics [this message]
2015-02-15 16:31   ` Michael Heerdegen
2015-02-15 20:32   ` Michael Heerdegen
2015-02-15 20:55     ` Michael Heerdegen
2015-02-15 21:05       ` Michael Heerdegen
2015-02-15 21:37         ` Michael Heerdegen
2015-02-16 18:36           ` 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=54E08498.2050603@gmx.at \
    --to=rudalics@gmx.at \
    --cc=19869@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).