From: "andrés ramírez" <rrandresf@hotmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 57364@debbugs.gnu.org
Subject: bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY
Date: Thu, 25 Aug 2022 14:29:06 +0000 [thread overview]
Message-ID: <SJ1PR12MB6363E2B93EE9D349B4AF0E5EA6729@SJ1PR12MB6363.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87tu624d64.fsf@yahoo.com>
Hi. Po.
>>>>> "Po" == Po Lu <luangruo@yahoo.com> writes:
[...]
Po> you must make Xlib check for errors immediately, by running Emacs with
Po> -xrm 'Emacs.synchronous: True'.
For following your suggestion I have adapted my test receipt a little
bit.
--8<---------------cut here---------------start------------->8---
1. gdb -i=mi --args ./emacs -Q -f toogle-debug-on-error --fg-daemon
2. emacsclient -c -n
3. M-x eval-expresion (x-synchronize t)
4. M-x eshell
5. on eshell-buffer emacs-version Return
6. @remoteMachine emacsclient -c -n {Xephyr could be used}
7. M-x eval-expresion (x-synchronize t)
8. C-x C-f ~/.bashrc
9. M-x dired-jump
10. M-x close-display-connection
--8<---------------cut here---------------end--------------->8---
Trying those steps above. The error does NOT produce.
Let me know If You have something else I could try.
Best Regards
next prev parent reply other threads:[~2022-08-25 14:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 17:51 bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY Andrés Ramírez
2022-08-24 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 14:29 ` andrés ramírez [this message]
2022-08-25 15:13 ` andrés ramírez
2022-08-26 1:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 1:50 ` andrés ramírez
2022-08-26 3:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 3:43 ` andrés ramírez
2022-08-26 5:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 13:59 ` andrés ramírez
2022-08-27 1:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 19:58 ` andrés ramírez
2022-08-30 1:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 5:28 ` andrés ramírez
2022-08-30 7:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 7:29 ` bug#57364: [PATCH] (was: bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY) andrés ramírez
2022-08-30 10:07 ` bug#57364: [PATCH] Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-27 12:49 ` bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY Lars Ingebrigtsen
2022-09-27 13:46 ` andrés ramírez
2022-09-27 17:32 ` Lars Ingebrigtsen
2022-08-30 8:02 ` bug#57364: 28.1; emacs segfaulted when debugging emacs form within emacs for bug#57364 Andrés Ramírez
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=SJ1PR12MB6363E2B93EE9D349B4AF0E5EA6729@SJ1PR12MB6363.namprd12.prod.outlook.com \
--to=rrandresf@hotmail.com \
--cc=57364@debbugs.gnu.org \
--cc=luangruo@yahoo.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).