From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: larsi@gnus.org, stephen.berman@gmx.net, 53916@debbugs.gnu.org
Subject: bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu
Date: Fri, 11 Feb 2022 09:59:41 +0200 [thread overview]
Message-ID: <83zgmxsuj6.fsf@gnu.org> (raw)
In-Reply-To: <87ee49vrzm.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
> Cc: Stephen Berman <stephen.berman@gmx.net>, 53916@debbugs.gnu.org
> Date: Fri, 11 Feb 2022 14:26:21 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Po Lu <luangruo@yahoo.com> writes:
>
> > Great, does anyone know what "%s" parameters to `add_to_log' are
> > expected in? UTF-8?
>
> About 5 seconds after sending this, I realized that it accepts Lisp
> objects and format control strings like `format'.
Yes, the arguments are Lisp strings.
> So hopefully that means it will be okay to print out unibyte strings via
> that mechanism, since I don't want to go down the rabbit hole of what
> text encodings various libraries using the GLib logging system subject
> it to.
Just use DECODE_SYSTEM, the encoding is already figured out for you.
Please do NOT use the original unibyte strings, they are likely to
display as gibberish in some cases.
next prev parent reply other threads:[~2022-02-11 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 10:43 bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu Stephen Berman
2022-02-10 12:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 12:52 ` Lars Ingebrigtsen
2022-02-10 13:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 6:20 ` Lars Ingebrigtsen
2022-02-11 6:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 6:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 7:59 ` Eli Zaretskii [this message]
2022-02-11 11:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 13:30 ` Robert Pluim
2022-02-10 13:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 17:40 ` Eli Zaretskii
2022-02-11 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 7:18 ` Eli Zaretskii
2022-02-11 7:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 8:10 ` Eli Zaretskii
2022-02-11 11:12 ` 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=83zgmxsuj6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53916@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=stephen.berman@gmx.net \
/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).