From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67753@debbugs.gnu.org, soliidne@gmail.com
Subject: bug#67753: 28.2, 29.1: Making frame invisible always affects frame position parameters
Date: Sat, 16 Dec 2023 20:18:07 +0800 [thread overview]
Message-ID: <87bkaqxrwg.fsf@yahoo.com> (raw)
In-Reply-To: <83plz6mjua.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Dec 2023 14:07:41 +0200")
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?
next prev parent reply other threads:[~2023-12-16 12:18 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 [this message]
2023-12-16 12:53 ` soliidne
2023-12-23 9:05 ` Eli Zaretskii
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
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=87bkaqxrwg.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=67753@debbugs.gnu.org \
--cc=eliz@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 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).