From: Dr Hartmut Bartels <dr.hartmut.bartels@googlemail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin programs display output incorrectly when run under conemu
Date: Mon, 17 Feb 2020 01:07:00 -0000 [thread overview]
Message-ID: <a3734b3a-fdf2-68e6-6cb6-6b202b25ccc3@gmail.com> (raw)
In-Reply-To: <CACac1F9k-8b2UsQ2xEuWu2okLh961BgxRY0sxySLoeL=8AgAUg@mail.gmail.com>
I had the same issue and got answer from Takashi Yano
https://cygwin.com/ml/cygwin/2020-01/msg00003.html
My workareound is
using version ConEmuPack.170807.7z. This works
together with cygwin 3.1.2-1. Versions of Comemu greater 170807 won't.
Same for cmder, if replacing conemu with version 170807.
Hartmut
Am 16.02.2020 um 13:22 schrieb Paul Moore:
> This issue has also been reported to the ConEmu tracker as
> https://github.com/Maximus5/ConEmu/issues/2059.
>
> If I run a cygwin command (for example ls, or for a simpler example,
> "printf hello\nthere", although the latter needs care to get the
> correct level of \n escaping :-)) newlines are displayed by the text
> moving down a line, but *not* returning to the left hand margin.
>
> An example, running in Powershell as my shell:
>
>> E:\Utils\Cygwin64\bin\printf.exe hello\nthere
> hello
> there
>
> This behaviour is present with the latest version of cygwin1.dll, as
> well as with the 20200212 snapshot. It is not present if I replace the
> Cygwin dll with version 3.0.7-1.
>
> The problem does not appear with a standard cmd.exe terminal (standard
> Windows console host) or the new Windows Terminal application. I
> understand that ConEmu handles the console management differently
> "behind the scenes" to present a GUI front end, but I don't know
> enough about the internals to know how it does that.
>
> I can work around the issue by pinning to cygwin 3.0.7-1, but it's
> obviously not ideal. I have been unable to find any details as to what
> changed between cygwin 3.0.7-1 and the next version to help me track
> down the issue any more specifically.
>
> There are some notes at https://conemu.github.io/en/CygwinMsys.html
> that I've read, but to be honest I don't entirely understand. I did,
> however, confirm that this issue doesn't occur in a standard `cmd`
> window (and I added that information to the ConEmu issue report).
>
> Any information that would help to pin down the cause of this problem
> would be very much appreciated.
>
> Paul
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
------------------------------
Dr.-Ing. Hartmut Bartels
dr.hartmut.bartels@gmail.com
dr.hartmut.bartels@t-online.de
------------------------------
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-02-17 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 12:22 Paul Moore
2020-02-17 1:07 ` Dr Hartmut Bartels [this message]
2020-02-17 7:49 ` Paul Moore
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=a3734b3a-fdf2-68e6-6cb6-6b202b25ccc3@gmail.com \
--to=dr.hartmut.bartels@googlemail.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).