unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: tanzer@gg32.com, Po Lu <luangruo@yahoo.com>
Cc: 65840@debbugs.gnu.org
Subject: bug#65840: 29.1; desktop-load moves frames to the right and down
Date: Sat, 09 Sep 2023 15:59:38 +0300	[thread overview]
Message-ID: <83v8cjtscl.fsf@gnu.org> (raw)
In-Reply-To: <f8b66a90-4f0c-11ee-a335-f2f1999dd7e8@gg32.com> (bug-gnu-emacs@gnu.org)

> Date: Sat, 09 Sep 2023 12:32:42 -0000
> From: tanzer--- via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> In GNU Emacs 29.1, desktop-load moves frames to the right and down.

This is probably specific to macOS, or maybe even to your window
manager, because it doesn't happen to me, and I'm a heavy user of
desktop.el.

When you say "In GNU Emacs 29.1", do you mean this issue is specific
to Emacs 29.1, and does not happen with Emacs 28 and older?

> The three attachements show the shifts in frame positions:
> 
> - .emacs.desktop.1 contains the correct frame positions after using
>   `desktop-save` and copying .emacs.desktop to .emacs.desktop.1
> 
> - Loading .emacs.desktop.1 into Emacs 29 results in the frames being
>   shifted. On exiting Emacs 29, the shifted positions are stored in
>   .emacs.desktop and copied to .emacs.desktop.2.
> 
> - Loading .emacs.desktop.2 into Emacs 29 results in the frames being
>   shifted again. On exiting Emacs 29, the shifted positions are stored
>   in .emacs.desktop and copied to .emacs.desktop.3.
> 
> - Loading any of these .emacs.desktop files into Emacs 28.2 results in
>   the expected frame positions (in case of .2 and .3 the positions
>   incorrectly shifted to by Emacs 29).

You are aware, I hope, that on X and similar GUI systems, the
coordinates of the frames we request from the window-manager are
advisory: the WM doesn't have to adhere to what we request.  I'm not
sure what you see is not a manifestation of that.

Po Lu, can you chime in, please?





  reply	other threads:[~2023-09-09 12:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 12:32 bug#65840: 29.1; desktop-load moves frames to the right and down tanzer--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 12:59 ` Eli Zaretskii [this message]
2023-09-09 13:35   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <031260D8-4159-4BBC-A25F-A8BCBD88B7BA@gg32.com>
2023-09-09 14:47     ` Eli Zaretskii
2023-09-13  5:09   ` Gerd Möllmann
2023-09-13  5:48     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 18:04       ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 18:27     ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 18:51       ` Gerd Möllmann

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=83v8cjtscl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65840@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=tanzer@gg32.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).