unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: david@ngdr.net
Cc: "25943@debbugs.gnu.org" <25943@debbugs.gnu.org>
Subject: bug#25943: 21.5  Frame Display Difficulties
Date: Sun, 02 Apr 2017 09:55:11 +0200	[thread overview]
Message-ID: <58E0AE5F.3070705@gmx.at> (raw)
In-Reply-To: <7ee8200b866d8067514fb8b0bb9e814b@127.0.0.1>

 > I think that I have done what you ask, with both 25.1 and 23.2.  However,
 > none of the listed functions exists on 23.2

Indeed.

 > 08-19-37: the result of invoking 25.1 with -Q over the network with ssh
 >
 > 08-23-08: after loading .emacs
 >
 > 08-24-07: after enlarging the frame by clicking on the top right +
 >
 > 08-47-05: a new invocation, no -Q
 >
 > 09-05-33: the result of invoking 23.2 with -Q over the network with ssh
 >
 > 09-06-42: after loading .emacs (the same file as above, not even a copy)
 >
 > 09-07-41: after enlarging the frame by clicking on the top right +
 >
 > 09-10-06: a new invocation, no -Q

I'm not 100% sure whether these results are for the right display/frame.
Also I see that you don't have any image support so your tool bars are
empty and useless for comparing.  Please repeat as follows:

(setq frame (make-frame '((tool-bar-lines . 0))))

(list
   (display-monitor-attributes-list frame)
   (frame-geometry frame)
   (frame-edges frame 'outer-edges)
   (frame-edges frame 'native-edges)
   (frame-edges frame 'internal-edges))

Then please run the function

(window--dump-frame frame)

and obtain the dump from the buffer *window-frame-dump*.

I'm only interested in emacs -Q runs for Emacs 25.2 so please do not
load your .emacs and always stay in Lisp interaction mode.  I need two
runs of the above - a first one right after your created the frame and a
second one after you maximized it.  Also please yank the results into
the mail body, it's hard for me to decipher them from the png images.

What I did note from your images is that your 23.2 build (I suppose it's
the one you always referred to in our past discussions) is not a GTK
build but one without toolkit support.  So it seems that we've been
always comparing apples and oranges and I'm quite confident that if your
23.2 build had been a GTK one you would've experienced exactly the same
problems then as you do now with the 25.2 build.

However, the fact that maximizing is not propagated correctly to the
frame's windows for the 25.2 version must be investigated.  Maybe the
frame dump will help.  How do you maximize?  Does any of the following
produce better frames?

(set-frame-parameter frame 'fullscreen 'maximized)
(set-frame-parameter frame 'fullscreen 'fullboth)
(set-frame-parameter frame 'fullscreen 'fullheight)
(set-frame-parameter frame 'fullscreen 'fullwidth)

Thanks for your efforts, martin





  parent reply	other threads:[~2017-04-02  7:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  3:51 bug#25943: 21.5 Frame Display Difficulties david
2017-03-03  8:13 ` martin rudalics
     [not found]   ` <af552a322a8a630796cbddf1133b6dbe@127.0.0.1>
2017-03-04  9:59     ` martin rudalics
2017-03-07  1:51       ` david
2017-03-07  9:45         ` martin rudalics
2017-03-08 22:58           ` david
2017-03-09  8:56             ` martin rudalics
2017-03-10 18:44               ` david
2017-03-11 10:21                 ` martin rudalics
2017-03-23  7:59                   ` martin rudalics
2017-03-28 22:43                     ` david
2017-03-29  7:36                       ` martin rudalics
2017-03-29 19:53                         ` david
2017-03-30  7:29                           ` martin rudalics
2017-04-01  4:35                             ` david
2017-04-01  7:36                               ` martin rudalics
     [not found]                                 ` <7ee8200b866d8067514fb8b0bb9e814b@127.0.0.1>
2017-04-02  7:55                                   ` martin rudalics [this message]
2017-04-04  0:35                                     ` david
2017-04-04  7:25                                       ` martin rudalics
2017-04-07  0:12                                         ` david
2017-04-07  5:56                                           ` martin rudalics
2017-04-07 21:16                                             ` david
2022-04-25 14:48                                               ` Lars Ingebrigtsen
2022-05-24 12:50                                                 ` Lars Ingebrigtsen
2017-04-07 21:19                                             ` david
2017-04-08  9:00                                               ` martin rudalics
2017-04-11  6:49                     ` 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=58E0AE5F.3070705@gmx.at \
    --to=rudalics@gmx.at \
    --cc=25943@debbugs.gnu.org \
    --cc=david@ngdr.net \
    /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).