From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42366@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#42366: UTF8 QR codes vs. emacs
Date: Wed, 05 Aug 2020 18:03:22 +0300 [thread overview]
Message-ID: <83zh79879h.fsf@gnu.org> (raw)
In-Reply-To: <87mu39jg7r.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 05 Aug 2020 16:54:32 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: jidanni@jidanni.org, 42366@debbugs.gnu.org
> Date: Wed, 05 Aug 2020 16:54:32 +0200
>
> > Can you redirect the output to a file?
>
> Sure, it's just a bunch of UTF-8. I guess I could also just include the
> data here:
Thanks. FWIW, with the default font my Emacs uses, I see no lines.
> > So you are saying that your problem with \uNNNN was because you used
> > an incorrect locale? IOW, that there's no bug here at all?
>
> Yes. Except for the horizontal lines in the X version of Emacs.
Can you try other fonts, and see if some of them eliminate the
problem? I think this is simply a matter of the shell window and the
terminal emulator using different fonts.
next prev parent reply other threads:[~2020-08-05 15:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 14:20 bug#42366: UTF8 QR codes vs. emacs 積丹尼 Dan Jacobson
2020-07-16 15:59 ` Robert Pluim
2020-07-16 17:44 ` 積丹尼 Dan Jacobson
2020-08-05 10:26 ` Lars Ingebrigtsen
2020-08-05 10:44 ` Andreas Schwab
2020-08-05 10:53 ` Lars Ingebrigtsen
2020-08-05 14:19 ` Eli Zaretskii
2020-08-05 14:22 ` Lars Ingebrigtsen
2020-08-05 14:48 ` Eli Zaretskii
2020-08-05 14:54 ` Lars Ingebrigtsen
2020-08-05 15:03 ` Eli Zaretskii [this message]
2020-08-05 15:33 ` Robert Pluim
2020-08-05 15:38 ` Eli Zaretskii
2020-08-05 15:42 ` Eli Zaretskii
2020-08-06 7:57 ` Robert Pluim
2020-08-06 13:44 ` Eli Zaretskii
2020-08-06 14:35 ` Robert Pluim
2020-08-06 14:40 ` Eli Zaretskii
2020-08-05 16:49 ` Andreas Schwab
2020-08-05 17:47 ` Lars Ingebrigtsen
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=83zh79879h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42366@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.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.