From: Eli Zaretskii <eliz@gnu.org>
To: luangruo@yahoo.com, soliidne@gmail.com
Cc: 67753@debbugs.gnu.org
Subject: bug#67753: 28.2, 29.1: Making frame invisible always affects frame position parameters
Date: Sat, 23 Dec 2023 11:05:22 +0200 [thread overview]
Message-ID: <83le9le1bh.fsf@gnu.org> (raw)
In-Reply-To: <CAKCdrGXE0DyhwSbi5uk4vLReBmcSgSQ8iCPr0TTL0EPar96SaA@mail.gmail.com> (soliidne@gmail.com)
Ping! Po Lu, can we make some progress here?
> From: soliidne@gmail.com
> Date: Sat, 16 Dec 2023 14:53:47 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, 67753@debbugs.gnu.org
>
> On Sat, 16 Dec 2023 20:18:07 +0800
> Po Lu <luangruo@yahoo.com> wrote:
>
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > >> From: soliidne@gmail.com
> > >> Date: Sun, 10 Dec 2023 19:45:49 +0200
> > >>
> > >> Always for all frames, position constantly affected by: left - 5
> > >> and top - 29. It seems like a bug, but it could also be an
> > >> oversight. Can someone comment please ?
> > >>
> > >> Thanks !
> > >>
> > >> xfwm4 4.18.0
> > >> xorg-server 21.1.9
> > >> Emacs 28.2, 29.1
> > >> Archlinux
> > >>
> > >> How to reproduce:
> > >> #################
> > >>
> > >> $ emacs --fg-daemon -Q
> > >> ...
> > >> Starting Emacs daemon.
> > >> $ emacsclient --eval "(make-frame-on-display \":0\")"
> > >> #<frame GNU Emacs at Elitebook 0x558cf8d7d120>
> > >> $ emacsclient --eval "(frame-position (nth 0 (frame-list)))"
> > >> (185 . 130)
> > >> $ emacsclient --eval "(make-frame-invisible (nth 0 (frame-list))
> > >> t)" nil
> > >> $ emacsclient --eval "(frame-position (nth 0 (frame-list)))"
> > >> (180 . 101)
> > >>
> > >> Moving frame to left-top corner
> > >> ###############################
> > >>
> > >> $ emacsclient --eval "(make-frame-visible (nth 0 (frame-list)))"
> > >> #<frame GNU Emacs at Elitebook 0x558cf8d7d120>
> > >> $ emacsclient --eval "(frame-position (nth 0 (frame-list)))"
> > >> (0 . 0)
> > >> $ emacsclient --eval "(make-frame-invisible (nth 0 (frame-list))
> > >> t)" nil
> > >> $ emacsclient --eval "(frame-position (nth 0 (frame-list)))"
> > >> (-5 . -29)
> > >> $ emacsclient --eval "(make-frame-visible (nth 0 (frame-list)))"
> > >> #<frame GNU Emacs at Elitebook 0x558cf8d7d120>
> > >> $ emacsclient --eval "(frame-position (nth 0 (frame-list)))"
> > >> (-5 . 0)
> > >> $ emacsclient --eval "(make-frame-invisible (nth 0 (frame-list))
> > >> t)" nil
> > >> $ emacsclient --eval "(frame-position (nth 0 (frame-list)))"
> > >> (-10 . -29)
> > >> $ emacsclient --eval "(make-frame-visible (nth 0 (frame-list)))"
> > >> #<frame GNU Emacs at Elitebook 0x558cf8d7d120>
> > >> $ emacsclient --eval "(frame-position (nth 0 (frame-list)))"
> > >> (-10 . 0)
> > >
> > > Po Lu, any comments?
> >
> > Did the OP mention the toolkit Emacs was built with?
>
> $ emacsclient --eval "system-configuration-options"
> "--sysconfdir=/etc --prefix=/usr --libexecdir=/usr/lib --localstatedir=/var --with-cairo --with-harfbuzz -
> -with-libsystemd --with-modules --with-x-toolkit=gtk3 'CFLAGS=-march=x86-64 -mtune=generic -O2 -
> pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security
> -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/build/emacs/src=/usr/src/debug/emacs -
> flto=auto' 'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -flto=auto'"
next prev parent reply other threads:[~2023-12-23 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 17:45 bug#67753: 28.2, 29.1: Making frame invisible always affects frame position parameters soliidne
2023-12-16 12:07 ` Eli Zaretskii
2023-12-16 12:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-16 12:53 ` soliidne
2023-12-23 9:05 ` Eli Zaretskii [this message]
2024-01-09 19:58 ` Eli Zaretskii
2024-01-10 10:25 ` soliidne
2024-01-20 9:09 ` Eli Zaretskii
2024-01-20 9:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83le9le1bh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67753@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=soliidne@gmail.com \
/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.