From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: incorrect text mode graphic character display
Date: Thu, 7 May 2020 15:52:06 -0600 [thread overview]
Message-ID: <edec4b7b-9b49-c8b3-a2bb-bb4d41178a84@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200507140945.56e74bce@quarternote>
On 2020-05-07 15:09, briand@pounceofcats.com wrote:
> On Thu, 7 May 2020 20:19:29 +0000
> André Bleau via Cygwin <cygwin@cygwin.com> wrote:
>> Brian D wrote:
>>> Assuming Julia is a not Cygwin program,
>>> you can try "CYGWIN=disable_pcon" before any Cygwin process
>> Did not help.
>> Thanks for that though, I had no idea those kind of env variables were available.
>> Character display problems do not depend only on the program you run, in
>> your case, "Julia", whatever that is, but also in which terminal or console
>> you run it, as it is the terminal that does the actual character display.
>> If you run in in mintty for example, you could try:
>> CYGWIN=disable_pcon /usr/bin/mintty
>> and run Julia in the just opened mintty.
>> I just happened to have a similar issue. If interested, look at:
>> https://cygwin.com/pipermail/cygwin/2020-May/244742.html
> Julia is a programming language and what i've shown is the REPL for it.
> I tried precisely what you showed there and it makes no difference at all.
> I get the exact same display.
> Humorously, it displays just fine in a windows cmd terminal.
As that env var is interpreted by the main Cygwin process cygwin1.dll, which has
to be unloaded and reloaded, I'd set CYGWIN=disable_pcon in the System
environment, then shut down all Cygwin processes, as you would before running
setup, log off, and log on.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-05-07 21:52 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 [this message]
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=edec4b7b-9b49-c8b3-a2bb-bb4d41178a84@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).