From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: incorrect text mode graphic character display
Date: Thu, 7 May 2020 19:31:01 +0200 [thread overview]
Message-ID: <0afd85b5-9bc8-8b6e-a032-8ae9c4b1e0e0@gmail.com> (raw)
In-Reply-To: <20200507081832.54306879@quarternote>
Am 07.05.2020 um 17:18 schrieb briand@pounceofcats.com:
> Hi,
>
> Doesn't matter what terminal i'm using, I'm having a problem with the way graphic characters print.
> Julia uses unicode output, and will generate output that should look like this:
>
> julia> x=DataFrame([(1,2,3), (4,5,6)])
> 2×3 DataFrame
> │ Row │ 1 │ 2 │ 3 │
> │ │ Int64 │ Int64 │ Int64 │
> ├─────┼───────┼───────┼───────┤
> │ 1 │ 1 │ 2 │ 3 │
> │ 2 │ 4 │ 5 │ 6 │
>
> Unfortunately I'm seeing this :
>
> julia> x=DataFrame([(1,2,3), (4,5,6)])
> 2×3 DataFrame
> Γöé Row Γöé 1 Γöé 2 Γöé 3 Γöé
> Γöé Γöé Int64 Γöé Int64 Γöé Int64 Γöé
> Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
> Γöé 1 Γöé 1 Γöé 2 Γöé 3 Γöé
> Γöé 2 Γöé 4 Γöé 5 Γöé 6 Γöé
>
> This was working until a recent upgrade. I have experimented with terminal set encoding and i can make the problem worse, but not better.
> ,
> I've tried several terminal types, e.g. the xfce4 terminal, gnome terminal, rxvt.
> They all give me incorrect displays, but rxvt gives me a different incorrect display. lxterminal and rxvt-unicode give me the same output as shown in this email.
>
> I've been trying to experiment with LC_ALL and related environment variables, but again, i can only make things worse.
>
> Any ideas on what i might try ?
>
> Thanks !
>
>
Assuming Julia is a not Cygwin program,
you can try "CYGWIN=disable_pcon" before any Cygwin process
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
next prev parent reply other threads:[~2020-05-07 17:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 15:18 briand
2020-05-07 16:01 ` Eric Lilja
2020-05-07 16:32 ` briand
2020-05-07 20:22 ` Eric Lilja
2020-05-07 21:11 ` briand
2020-05-07 21:26 ` Eric Lilja
2020-05-07 22:10 ` briand
2020-05-08 2:31 ` David Rothenberger
2020-05-08 3:12 ` briand
2020-05-08 2:47 ` André Bleau
2020-05-07 17:31 ` Marco Atzeri [this message]
2020-05-07 20:07 ` briand
2020-05-07 20:19 ` André Bleau
2020-05-07 21:09 ` briand
2020-05-07 21:52 ` Brian Inglis
2020-05-07 22:12 ` briand
2020-05-08 3:03 ` Brian Inglis
2020-05-08 15:01 ` briand
2020-05-08 18:41 ` Marco Atzeri
2020-05-08 20:14 ` briand
2020-05-09 6:32 ` Marco Atzeri
2020-05-09 6:45 ` Thomas Wolff
2020-05-09 7:30 ` Marco Atzeri
2020-05-09 7:41 ` Thomas Wolff
2020-05-09 20:37 ` briand
2020-05-09 21:32 ` Marco Atzeri
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=0afd85b5-9bc8-8b6e-a032-8ae9c4b1e0e0@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.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.
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).