From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 56372@debbugs.gnu.org, dick.r.chiang@gmail.com
Subject: bug#56372: 29.0.50; [PATCH] Avoid BadMatch X11 error
Date: Tue, 05 Jul 2022 08:15:49 +0900 [thread overview]
Message-ID: <b4m8rp8sc4a.fsf@jpl.org> (raw)
In-Reply-To: <87czemtfv0.fsf@dick>
On Mon, 04 Jul 2022 13:21:46 +0800, Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> By the patch, 29.0.50 built on Cygwin got stable. It crashed
>> for the BadMatch error whenever I did something. Thank you.
> Would you please show the complete error message resulting from the
> BadMatch error with a new build from master?
I got not to be able to reproduce the problem thanks to your
recent change in revno c4e93b6. :) But it at least said "GDK"
error and "Badmatch".
> Also, what toolkit are you using?
gtk3
Anyway thank you very much for fixing this.
Regards,
next prev parent reply other threads:[~2022-07-04 23:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 14:45 bug#56372: 29.0.50; [PATCH] Avoid BadMatch X11 error dick.r.chiang
2022-07-04 0:50 ` Katsumi Yamaoka
2022-07-04 5:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04 23:15 ` Katsumi Yamaoka [this message]
2022-07-04 1:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04 6:05 ` po lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-05 0:21 ` dick
2022-07-05 1:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04 4:50 ` dick
2022-07-04 10:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04 10:19 ` Lars Ingebrigtsen
2022-07-04 10:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04 12:12 ` dick
2022-07-04 12:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=b4m8rp8sc4a.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=56372@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--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).