From: martin rudalics <rudalics@gmx.at>
To: Robert Pluim <rpluim@gmail.com>
Cc: Trevor Spiteri <tspiteri@ieee.org>, 40817@debbugs.gnu.org
Subject: bug#40817: 27.0.91; setting frame parameter '(left - 0) leaves gap to the right under GTK
Date: Wed, 29 Apr 2020 17:03:18 +0200 [thread overview]
Message-ID: <fde08d9e-90ad-61ff-d7f1-772b5ea356ed@gmx.at> (raw)
In-Reply-To: <m2r1w6v0so.fsf@gmail.com>
> I see this with the GNOME shell on Ubuntu 20.04 (not sure if itʼs
> using mutter, how does one check that?).
With the task manager. With wmctrl it identifies itself as GNOME shell.
> However, the good news is that the behaviour is correct using the
> pgtk build, including '((top - 0)).
Good to hear. I haven't had time to look into this so far but I always
hoped that a pure GTK build would solve this and maybe some of our other
GTK issues. It would be interesting to know whether and how the
arguments of
gtk_window_move (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)),
f->left_pos / scale, f->top_pos / scale);
in xterm.c and
gtk_window_move (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)),
f->left_pos, f->top_pos);
in pgtkterm.c differ. BTW, did you test this with X11 or Wayland?
martin
next prev parent reply other threads:[~2020-04-29 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 13:36 bug#40817: 27.0.91; setting frame parameter '(left - 0) leaves gap to the right under GTK Trevor Spiteri
[not found] ` <handler.40817.B.15877354202944.ack@debbugs.gnu.org>
2020-04-24 14:44 ` bug#40817: Acknowledgement (27.0.91; setting frame parameter '(left - 0) leaves gap to the right under GTK) Trevor Spiteri
2020-04-24 17:55 ` bug#40817: 27.0.91; setting frame parameter '(left - 0) leaves gap to the right under GTK martin rudalics
2020-04-29 14:12 ` Robert Pluim
2020-04-29 15:03 ` martin rudalics [this message]
2020-04-29 16:51 ` Robert Pluim
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=fde08d9e-90ad-61ff-d7f1-772b5ea356ed@gmx.at \
--to=rudalics@gmx.at \
--cc=40817@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=tspiteri@ieee.org \
/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.