From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: incorrect text mode graphic character display
Date: Sat, 9 May 2020 09:30:02 +0200 [thread overview]
Message-ID: <9fc9522c-d2f5-f903-70d7-ee602c5bb9a5@gmail.com> (raw)
In-Reply-To: <fd81274e-f3dd-c6b4-fbec-cfe8f2343bf5@towo.net>
Am 09.05.2020 um 08:45 schrieb Thomas Wolff:
> Am 09.05.2020 um 08:32 schrieb Marco Atzeri via Cygwin:
>> Am 08.05.2020 um 22:14 schrieb briand@pounceofcats.com:
>>> On Fri, 8 May 2020 20:41:55 +0200
>>> Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
>>>
>>>> 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 │
>>>>>
>>>>
>>>> it works fine for me with
>>>> $ uname -svr
>>>> CYGWIN_NT-10.0 3.1.4(0.340/5/3) 2020-02-19 08:49
>>>>
>>>> both on CMD console and Mintty
>>>> without need to disable pcon
>>>>
>>>> julia> using DataFrames
>>>>
>>>> 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 │
>>>>
>>>> what type of locale are you using ?
>>>> $ echo $LANG
>>>> en_US.UTF-8
>>>
>>> yes, that's the locale
>>>
>>
>> so it is not the DLL alone and it is not the locale
>> that is causing the problem you see.
>>
>> Please provide the cygcheck.out as attachment
>> https://cygwin.com/problems.html
>>
>> Which version of Julia are you running ?
>> How are you running Julia?
>> Do you have any custom user setup in Julia?
>> I just installed it and only installed the DataFrames package.
> Julia had a patch to enable UTF-8 output via Windows output functions in
> previous cygwin versions.
> I remember the details only vaguely right now, but it may be necessary
> to remove that patch for cygwin from 3.1.0, or it might cause some kind
> of double transformation.
> Thomas
> --
there is a Cygwin porting ?
I installed the last windows 64 binary
Current stable release: v1.4.1 (April 14, 2020)
and it works for me, I do not see the issue reported by Brian
Marco
next prev parent reply other threads:[~2020-05-09 7:30 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
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 [this message]
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=9fc9522c-d2f5-f903-70d7-ee602c5bb9a5@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).