unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 17:19:28 +0300	[thread overview]
Message-ID: <83a6z99nv3.fsf@gnu.org> (raw)
In-Reply-To: <875z9xcrrk.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  05 Aug 2020 12:26:55 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 05 Aug 2020 12:26:55 +0200
> Cc: 42366@debbugs.gnu.org
> 
> > Compare how
> > $ qrencode -t UTF8 x
> > looks in
> > $ emacs -nw -f shell # vs.
> > $ emacs     -f shell
> >
> > As you can see in the latter it is quite mangled,
> > perhaps beyond machine recognition.
> 
> It's not good in any case, really.  Here's the X version:

Can you send the file itself?

> Note the horizontal lines -- it should be a solid white field.

How do you know that?

> And with -nw it's just a complete mess:

No, it isn't...

> I guess...  it's translating all the Unicode characters instead of just
> letting the terminal render them?  The terminal does have these
> characters; when running the program directly in the shell everything
> works fine.

That's what happens when Emacs thinks your terminal cannot display
these characters.  What does 'terminal-coding-system' return on that
display?

> Does anybody know how to make shell-mode (under -nw) just output the
> characters?

Hmm... shell-mode?  Now I'm beginning to think I don't really
understand what are the steps to reproduce the problem, and what is
their meaning (jidanni needs to learn how to report bugs clearly).
Would you please describe the steps, starting from "emacs -Q"?





  parent reply	other threads:[~2020-08-05 14:19 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 [this message]
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
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

  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=83a6z99nv3.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 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).