From: <briand@pounceofcats.com>
To: David Rothenberger <daveroth@acm.org>
Cc: cygwin@cygwin.com
Subject: Re: incorrect text mode graphic character display
Date: Thu, 7 May 2020 20:12:24 -0700 [thread overview]
Message-ID: <20200507201224.06a00d5f@quarternote> (raw)
In-Reply-To: <c3dd7754e8d8fd62fea314efca044603@acm.org>
On Thu, 07 May 2020 19:31:28 -0700
David Rothenberger <daveroth@acm.org> wrote:
> On 2020-05-07 15:10, briand@pounceofcats.com wrote:
> > On Thu, 7 May 2020 23:26:37 +0200
> > Eric Lilja <mindcooler@gmail.com> wrote:
> >
> >> Cygwin itself is actually just DLL, you can select a previous version
> >> of it
> >> in setup.exe. That solved our issue with corrupted display of Maven.
> >> You
> >> can also install older versions of any package (but not all old
> >> versions
> >> ever published will be available to choose from, just a few ones).
> >> Anyway,
> >> my suggestion is downgrade Cygwin itself and see if that helps (if
> >> not, we
> >> know the problem is elsewhere). All the other packages you can keep at
> >> latest versions.
> >>
> >
> > success!
>
> I'm glad that worked for you, but it may not a good long-term solution
> unless you're willing to use old packages, too. New APIs are added to
> the DLL from time to time, and that may cause packages compiled against
> the new DLL that use the new APIs to fail if you keep the old DLL
> installed.
>
> Personally, I would use the CYGWIN=disable_pcon work-around and help the
> maintainers track down the root cause of the issue so it can be fixed.
>
ok. i'll have to give it a try per Brian Inglis' instructions and see if that makes the difference in that "fix" actually working.
next prev parent reply other threads:[~2020-05-08 3:12 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 [this message]
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
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=20200507201224.06a00d5f@quarternote \
--to=briand@pounceofcats.com \
--cc=cygwin@cygwin.com \
--cc=daveroth@acm.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.
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).