all messages for Emacs-related lists mirrored at yhetil.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: Wed, 29 Mar 2017 09:36:13 +0200	[thread overview]
Message-ID: <58DB63ED.8060305@gmx.at> (raw)
In-Reply-To: <f11e0586822cab78b35c54434571756e@127.0.0.1>

 > I have run your frame-position code a few times; I have not had time to do
 > anything else.

I suppose you did not (or were not able to) apply my patch so

(setq x-gtk-use-window-move t)

had not effect on the outcome of your runs.  Right?

 > I am unable to do anything similar for 23.2 because
 > function frame-position does not exist in 23.2.

I forgot.  Instead of

	 (pos (frame-position frame))
	 (left (car pos))
	 (top (cdr pos))

use

	 (left (frame-parameter frame 'left))
	 (top (frame-parameter frame 'top))

for Emacs 23.

 > Mostly, but not always, the 9-C (fun) frames are consistently in their
 > correct corner.  This is true for the 1-4 (arg) frames as well; I do not
 > have any record of a deviation, so arg frames may be perfect.  The 5-8
 > (par) frames are the deviants, which seem to go the the Left Top corner.

Your results for 25.1 are better than mine.  Here only the "arg" runs
position correctly.  The "fun" and "par" frames all end up in the top
left corner.  So if you do want to continue working with an unpatched
Emacs 25.1 and want more or less correct positioning you will have to
use the "arg" notation.  Otherwise you will have to either patch your
25.1 or switch to the current development version.

(
  (arg
   ...
   (name . "4 Right Bottom")
   (p-left . -40)
   (p-top . -40)
   (left . 1181)
   (top . 694)
   (width . 816)
   (height . 400)
   (r-left . -51)
   (r-top . -58))

It might be interesting to see where these differences in the "arg" case
come from - 11 pixels horizontally and 18 pixels vertically.  What does

M-: (frame-geometry)

in that frame return?

Thanks, martin





  reply	other threads:[~2017-03-29  7:36 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58DB63ED.8060305@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.