From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yuri D'Elia <wavexx@thregr.org>, 34051@debbugs.gnu.org
Subject: bug#34051: "X protocol error: BadMatch" on current master
Date: Thu, 17 Jan 2019 17:39:39 +0000 [thread overview]
Message-ID: <20190117173939.GA44157@breton.holly.idiocy.org> (raw)
In-Reply-To: <83k1j3cso5.fsf@gnu.org>
On Thu, Jan 17, 2019 at 03:36:26PM +0200, Eli Zaretskii wrote:
> > From: Yuri D'Elia <wavexx@thregr.org>
> > Cc: Eli Zaretskii <eliz@gnu.org>
> > Date: Wed, 16 Jan 2019 22:22:30 +0100
> >
> > Let me know if that's enough or if I should also get those darn
> > debugging symbols for X11...
>
> Thanks, this shows the problem very clearly. I think Alan posted a
> proposed patch; could you see if it solves the problems for you?
Yes, I’m sure my patch will fix this, and since Katsumi Yamaoka
reported it as fixing a similar issue I’ve pushed it to master.
--
Alan Third
next prev parent reply other threads:[~2019-01-17 17:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 15:08 "X protocol error: BadMatch" on current master Yuri D'Elia
2019-01-14 16:12 ` Eli Zaretskii
2019-01-12 15:46 ` bug#34051: 27.0.50; Emacs 27 from master segfaults stefan-husmann
2019-01-12 16:15 ` Eli Zaretskii
[not found] ` <87sgxxwtbs.fsf@frege.i-did-not-set--mail-host-address--so-tickle-me>
2019-01-12 20:22 ` Eli Zaretskii
2019-01-13 11:20 ` Stefan Husmann
2019-01-13 15:24 ` Eli Zaretskii
2019-01-15 16:52 ` Alan Third
2019-01-16 21:22 ` bug#34051: "X protocol error: BadMatch" on current master Yuri D'Elia
2019-01-16 21:28 ` Yuri D'Elia
2019-01-17 13:36 ` Eli Zaretskii
2019-01-17 17:39 ` Alan Third [this message]
2019-01-17 17:44 ` Yuri D'Elia
2019-01-17 17:50 ` Alan Third
2019-01-17 0:18 ` bug#34051: 27.0.50; Emacs 27 from master segfaults Katsumi Yamaoka
2019-01-17 17:42 ` Alan Third
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=20190117173939.GA44157@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=34051@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=wavexx@thregr.org \
/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.