From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>, martin rudalics <rudalics@gmx.at>
Cc: michael_heerdegen@web.de, gregory@heytings.org,
monnier@iro.umontreal.ca, 51883@debbugs.gnu.org
Subject: bug#51883: 29.0.50; Command to get accidentally deleted frames back
Date: Mon, 24 Jan 2022 20:32:25 +0200 [thread overview]
Message-ID: <838rv5j87a.fsf@gnu.org> (raw)
In-Reply-To: <8635ld0zq7.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 24 Jan 2022 20:12:48 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, michael_heerdegen@web.de, Gregory
> Heytings <gregory@heytings.org>, 51883@debbugs.gnu.org
> Date: Mon, 24 Jan 2022 20:12:48 +0200
>
> While copying some code from `clone-frame` to `undelete-frame`,
> I noticed that `clone-frame` doesn't work on non-GTK builds,
> because window-id frame parameters keep frame-specific X-windows,
> so `clone-frame` is broken in emacs-28.
>
> Eli, is it ok to push the first patch to the release branch?
I don't yet understand the change. I could understand why window-id
should be removed, but why parent-id, for example?
Martin, any comments on this change?
next prev parent reply other threads:[~2022-01-24 18:32 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 23:38 bug#51883: 29.0.50; Command to get accidentally deleted frames back Michael Heerdegen
2021-11-16 7:53 ` Juri Linkov
2021-11-16 8:14 ` Lars Ingebrigtsen
2021-11-16 20:46 ` Juri Linkov
2021-11-16 8:49 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 20:20 ` Juri Linkov
2021-11-16 15:17 ` Gregory Heytings
2021-11-16 17:05 ` Gregory Heytings
2021-11-16 17:40 ` Eli Zaretskii
2021-11-16 21:29 ` Gregory Heytings
2021-11-17 10:02 ` Gregory Heytings
2021-11-17 13:11 ` Eli Zaretskii
2021-11-17 17:06 ` Juri Linkov
2021-11-17 17:14 ` Eli Zaretskii
2021-11-19 9:00 ` Gregory Heytings
2021-11-19 12:17 ` Eli Zaretskii
2021-11-24 0:44 ` Gregory Heytings
2021-11-27 11:36 ` Michael Heerdegen
2021-11-27 11:53 ` Gregory Heytings
2021-11-27 12:05 ` Eli Zaretskii
2021-11-27 12:12 ` Gregory Heytings
2021-11-27 12:30 ` Andreas Schwab
2021-11-27 12:34 ` Eli Zaretskii
2021-11-27 12:23 ` Michael Heerdegen
2021-11-27 12:40 ` Eli Zaretskii
2021-11-27 13:22 ` Michael Heerdegen
2021-11-27 13:26 ` Eli Zaretskii
2021-11-27 13:34 ` Michael Heerdegen
2021-11-27 13:56 ` Eli Zaretskii
2021-11-27 13:59 ` Michael Heerdegen
2021-11-27 14:02 ` Eli Zaretskii
2021-11-27 14:08 ` Michael Heerdegen
2021-11-27 14:47 ` Eli Zaretskii
2021-11-27 14:12 ` Gregory Heytings
2021-11-27 14:24 ` Michael Heerdegen
2021-11-27 14:26 ` Gregory Heytings
2021-11-27 14:33 ` Michael Heerdegen
2021-11-27 14:42 ` Gregory Heytings
2021-11-27 14:54 ` Michael Heerdegen
2021-11-27 17:19 ` Gregory Heytings
2021-11-28 15:47 ` Michael Heerdegen
2021-11-29 13:38 ` Gregory Heytings
2021-11-29 18:18 ` Michael Heerdegen
2021-11-29 19:07 ` Michael Heerdegen
2021-11-29 20:19 ` Juri Linkov
2022-01-13 8:32 ` Juri Linkov
2022-01-14 8:12 ` Juri Linkov
2022-01-16 20:59 ` Juri Linkov
2022-01-17 0:08 ` Michael Heerdegen
2022-01-17 8:24 ` Juri Linkov
2022-01-17 13:00 ` Eli Zaretskii
2022-01-17 18:41 ` Juri Linkov
2022-01-17 18:51 ` Eli Zaretskii
2022-01-18 18:30 ` Juri Linkov
2022-01-19 18:37 ` Juri Linkov
2022-01-19 20:17 ` Eli Zaretskii
2021-12-12 2:44 ` Michael Heerdegen
2022-01-10 8:13 ` Michael Heerdegen
2021-11-27 14:48 ` Eli Zaretskii
2021-11-27 12:13 ` Michael Heerdegen
2022-01-22 18:10 ` Juri Linkov
2022-01-21 17:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 18:08 ` Juri Linkov
2022-01-22 21:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 9:11 ` Juri Linkov
2022-01-23 16:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 18:12 ` Juri Linkov
2022-01-23 21:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-24 18:12 ` Juri Linkov
2022-01-24 18:32 ` Eli Zaretskii [this message]
2022-01-25 9:28 ` martin rudalics
2022-01-25 12:29 ` Eli Zaretskii
2022-01-25 15:58 ` martin rudalics
2022-01-27 17:21 ` Juri Linkov
2022-01-27 17:27 ` Eli Zaretskii
2022-01-27 17:48 ` Juri Linkov
2022-01-24 23:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-27 17:19 ` Juri Linkov
2022-01-30 16:39 ` Juri Linkov
2022-01-30 16:59 ` Eli Zaretskii
2022-01-30 17:17 ` Juri Linkov
2022-01-30 18:17 ` Eli Zaretskii
2022-01-30 20:49 ` Juri Linkov
2021-11-16 20:30 ` Juri Linkov
2021-11-17 4:13 ` Richard Stallman
2021-11-17 10:07 ` Gregory Heytings
2021-11-17 16:39 ` bug#51883: [External] : " Drew Adams
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=838rv5j87a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51883@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=juri@linkov.net \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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.