ConEmu build: 190714[32]
OS version: Windows 10 x64
Used shell version: Powershell, Cmd
Running Cygwin text utilities with the newest Cygwin test release shows a massive distortion of the output.
ls or tree from Cmd or PowerShell> ls -l
insgesamt 0
-rw-rw----+ 1 thorsten Kein 0 12. Dez 2018 test.txt
-rw-rw----+ 1 thorsten Kein 0 12. Dez 2018 test.txt.1
> ls -l
insgesamt 0
-rw-rw----+ 1 thorsten Kein 0 12. Dez 2018 test.txt
-rw-rw----+ 1 thorsten Kein 0 12. Dez 2018 test.txt.1
I suppose you don't run cygwin via cygwin/msys connector.
If so, the bug most probably should be addressed to Microsoft.
Not really sure what you mean. If I run conemu-cyg-64.exe ls -l then the output is as expected. But it used to work without conemu-cyg-64. So from my perspective the bug is either in ConEmu or in Cygwin. I would rather say Cygwin because Cygwin is the one that changed.
Did you read what Takashi Yano states in https://cygwin.com/ml/cygwin/2019-08/msg00152.html ?
"If ENABLE_VIRTUAL_TERMINAL_INPUT flag is set to console input, it affects to console output and becomes so that the newline '\n' does not cause carriage return."
Can you "do" something with this finding?
This is not cygwin specific problem. To reproduce the problem, compile attached source in https://cygwin.com/ml/cygwin/2019-08/msg00152.html using mingw compiler and execute it in ConEmu.
The expected result and the result in command prompt is:
BBB
However, the result in ConEmu is:
BBB
I'm also being hit by this bug. Latest Cygwin 64bits and latest Conemu Preview.
For me it seems to happen randomly.
Any ideas @Maximus5 ?
This bug and the paste feature removing the newlines made me stop using this software.
Gonna try again in a few months.
I've just encountered this issue in Cmder which uses Conemu, after a Cygwin update.
Until a fix can be done in code either in Cygwin or Conemu - is there a workaround for this? Envvar, setting, anything?
@Pathduck I believe the work around was stated above
When I do this all the cygwin executables in my path display correctly. It completely breaks my workflow (obviously) so I am looking to utilize that in some way.
@PipeItToDevNull For now I've just rolled the Cygwin 'cygwin' package back to 3.0.7-1 and it works. I rarely update Cygwin anyway, and I'll just wait for a couple of months and try again.
@Pathduck How did you achieve this? I just installed cygwin using a portable script
@Pathduck How did you achieve this? I just installed cygwin using a portable script
I use the GUI installer, and you can roll back to older versions there. But the "bug" is in the cygwin1.dll and if you just replace this it will work. You can get the older packages here:
https://cygwin.uib.no/x86/release/cygwin/
https://cygwin.uib.no/x86_64/release/cygwin/
Unpack the cygwin-3.0.7-1.tar.xz with xz -d and find the dll in usr/bin.
But the "bug" is in the cygwin1.dll and if you just replace this it will work.
This is not a bug of cygwin but a lack of feature in ConEmu. The problem is that ConEmu ignores DISABLE_NEWLINE_AUTO_RETURN which is used in cygwin 3.1.x.
I made a patch against ConEmuHk.dll just for testing. I am not familiar with ConEmu source, so I am not sure this is the right thing. However, the following patch solves the issue.
I started using scoops as my work around
I will test this at some point though
Another workaround is to uncheck the "Inject ConEmuHk.dll into all processes started in ConEmu tabs" option in Settings->General
This appears to be fixed in the latest Cygwin 3.1.4-1 base package.
See: https://github.com/Maximus5/ConEmu/issues/2059
Most helpful comment
Another workaround is to uncheck the "Inject ConEmuHk.dll into all processes started in ConEmu tabs" option in Settings->General