From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 64310@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#64310: 29.0.92; pure-GTK warning under Wayland
Date: Thu, 17 Aug 2023 22:21:05 +0530 [thread overview]
Message-ID: <87zg2pwr2e.fsf@codeisgreat.org> (raw)
In-Reply-To: <878ragprku.fsf@yahoo.com> (Po Lu's message of "Sat, 12 Aug 2023 16:56:01 +0800")
Po Lu <luangruo@yahoo.com> writes:
>> If the bug is not reproducible, we can close it as such.
>>
It is reproducible at my end. But if it not widely encountered then it
should be noted in "known problems".
>>> Do we have an option that prompts emacsclient to print the output it's
>>> sending through the server socket?
>>
>> No, but it should be easy to add this: see send_to_emacs in
>> emacsclient.c. You can also see what was received by the server if
>> you set server-log non-nil: then the server will log the received
>> directives in the " *server*" buffer.
>>
>> Not sure how this would help you, given the description of the
>> original problem, though. Am I missing something?
>
> It occured to me that such logs from Pankaj's machine might help me
> devise a fix or the means to reproduce the problem myself.
Let me try to produce logs as suggested above. I will be able to do this
over the coming weekend.
next prev parent reply other threads:[~2023-08-17 16:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 4:45 bug#64310: 29.0.92; pure-GTK warning under Wayland Pankaj Jangid
2023-06-28 0:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-01 8:41 ` Eli Zaretskii
2023-07-01 9:25 ` Pankaj Jangid
2023-07-01 9:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-01 9:53 ` Pankaj Jangid
2023-07-06 7:12 ` Eli Zaretskii
2023-07-06 11:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-13 9:30 ` Pankaj Jangid
2023-07-22 13:15 ` Eli Zaretskii
2023-07-22 13:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-26 13:54 ` Eli Zaretskii
2023-07-27 5:18 ` Pankaj Jangid
2023-08-03 8:01 ` Eli Zaretskii
2023-08-12 6:47 ` Eli Zaretskii
2023-08-12 7:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 8:16 ` Eli Zaretskii
2023-08-12 8:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 16:51 ` Pankaj Jangid [this message]
2023-08-24 6:16 ` Eli Zaretskii
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=87zg2pwr2e.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=64310@debbugs.gnu.org \
--cc=eliz@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).