From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "andrés ramírez" <rrandresf@hotmail.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: Sat, 27 Aug 2022 09:17:38 +0800 [thread overview]
Message-ID: <875yiescwd.fsf@yahoo.com> (raw)
In-Reply-To: <SJ1PR12MB63635AFA9DA64DBDD57CCD49A6759@SJ1PR12MB6363.namprd12.prod.outlook.com> ("andrés ramírez"'s message of "Fri, 26 Aug 2022 13:59:25 +0000")
andrés ramírez <rrandresf@hotmail.com> writes:
> My distro is Archlinux, almost and up-to-date distro. I had installed
> 1.17.6. After your comment I upgrade cairo to the git version. And the
> error is still present.
Too bad.
> I should add that this error does NOT happen with emacs-master. So
> something has changed on emacs-master, that incidentally has avoided
> this error. Perhaps You could have an idea about what change has solved
> it on master.
No, sorry, but I know it's not present on master. Try bisecting to see
which change resolves the problem.
> Ok. But again. I am getting rid of all the frames that belong to this
> display. If the border change it is something I am not going to watch
> (because. It is going to be too quick for my eyes). IMO It could be an
> optimization there. Perhaps When 'dpyinfo->display == NULL' not updating
> the frame anymore. Anyway that is a kind of tangent for this bug.
dpyinfo->display is not NULL at that time, because async input will not
be read if it is.
Anyway, such an optimization done by itself is insignificant, and
applied to all async input will get in the way of legitimate work
performed while reading async input, such as responding to
SelectionNotify events.
next prev parent reply other threads:[~2022-08-27 1:17 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
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 [this message]
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=875yiescwd.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=57364@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=rrandresf@hotmail.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).