Open alexdevero opened 7 years ago
What I'm doing wrong?
I have no idea. Do you have Windows 10 Creators Update?
Yes! Solved! Menu -> Debug -> Properties .... Here check "Use legacy console" option on the bottom.
Just to pitch in, I'm using the Creators Update, but haven't run into this problem yet (or even before CU, AU, or in Windows 7). I have run into other problems with yarn though, such as: https://github.com/yarnpkg/yarn/issues/2724
Thanks @kumarharsh for you comment. I had no idea about these issues with colors and background related to yarn. I haven't run into them. Just this one I solved by checking the "Use legacy console" option. Now, the question is what are the issues that can be solved in the side of ConEmu? I think this is on @Maximus5 to decide.
I didn't make a decision yet. This issue needs more investigations, perhaps I can implement some workarounds, if it really depends on ConEmu.
I was having the same issue in Conemu with both zsh.exe
from Cygwin and bash.exe
from Ubuntu For Windows. The “Use legacy console” setting helped, thanks @alexdevero!
BTW, my Cygwin comes from Babun, but the ConEmu task is pointed directly at zsh.exe
, not at mintty.exe
like Babun recommends it. Maybe that’s of any significance.
@hoichi You are welcome! 👍
'Use legacy console' did fix my problem but the window bash (linux subsystem) requires to disable the legacy mode.
node --version
? yarn --version
?I've just run into the same issue while migrating to a new laptop. With the new laptop, yarn doesn't display the status bar correctly.
Working System: OS: Windows 10 Enterprise 1607 1439.1358 node --version: v6.11.1 yarn --version: 0.27.5 ConEmu: 160724 [64]
Non-working System: OS: Windows 10 Enterprise 1703 15063.540 node --version: v6.11.2 yarn --version: 0.27.5 ConEmu: 170807 [64]
The version of bash is the same for both. I'm using the same ConEmu settings on both systems. I've even copied over the ConEmu binaries from the old system to the new to rule out that it's an issue with the ConEmu version.
So, all the only differences I can really see are in the Windows build and the node patch version.
Update: I also attempted to apply the latest Windows Updates to the old system which included the Creators Update, but this didn't break the old version.
ConEmu version 170807 [64] Preview
Node version v8.1.4
yarn version 0.27.5
progress line (gif)
Info screen
Text from sysinfo (I've hidden the path info...)
ConEmu 170807 [64] Startup Info
OsVer: 10.0.15063.x64, Product: 1, SP: 0.0, Suite: 0x100, SM_SERVERR2: 0
CSDVersion: , ReactOS: 0 (), Rsrv: 0
DBCS: 0, WINE: 0, PE: 0, Remote: 0, ACP: 1252, OEMCP: 437, Admin: 0
StartTime: 2017-08-14 09:29:49.445
AppID: 687981e231065cf76721717d5493a377::163
Desktop: ``, SessionId: 1, ConsoleSessionId: 1
Title: `ConEmu`
Size: {0,0},{0,0}
Flags: 0x00000000, ShowWindow: 1, ConHWnd: 0x00000000
char: 1, short: 2, int: 4, long: 4, u64: 8
Handles: 0x00000000, 0x00000000, 0x00000000
Current PID: 4776, TID: 5356
Active HKL: 0x0000000004093C09
GetKeyboardLayoutList: 0x0000000004093C09 0x0000000004040404
CmdLine: "C:\softwares\ConEmu\ConEmu64.exe"
ExecMod: C:\softwares\ConEmu\ConEmu64.exe
WorkDir: C:\Users\jackys
PathEnv: [hidden]
ConFont: 0 Lucida Console 00 Consolas
CMD's AutoRuns:
HKCU: c:\settings\autorun\autorun.bat&&"C:\softwares\clink\0.4.5\clink" inject --profile "~\clink"
Foreground: x00050748 {2006,129}-{2635,537} 'VirtualConsoleClass' - cmd
MouseCursor: {2646,589} MouseMonitor: 00020001 StartMonitor: 00000000
Display: bpp=32, planes=1, align=1, vrefr=60, shade=x00000000, rast=x00007E99, dpi=120x120, per-mon-dpi=1
Monitors (dpi: WholeDesktop, Effective, Angular, RAW):
000600A1: {0,0}-{1920,1080} (1920x1080), Working: {0,0}-{1920,1030} (1920x1030), dpi: {120,120};{120,120};{123,123};{141,141} `\\.\DISPLAY1` <<== Primary
00020001: {1920,0}-{3200,1024} (1280x1024), Working: {1920,0}-{3200,1024} (1280x1024), dpi: {120,120};{96,96};{96,96};{96,96} `\\.\DISPLAY2`
Modules:
00007FF7946D0000-00007FF7949A8FFF 2D9000 C:\softwares\ConEmu\ConEmu64.exe
00007FFCD01A0000-00007FFCD037AFFF 1DB000 C:\WINDOWS\SYSTEM32\ntdll.dll
00007FFCCDB80000-00007FFCCDC2DFFF AE000 C:\WINDOWS\System32\KERNEL32.DLL
00007FFCCC900000-00007FFCCCB48FFF 249000 C:\WINDOWS\System32\KERNELBASE.dll
00007FFCCE680000-00007FFCCE6D0FFF 51000 C:\WINDOWS\System32\SHLWAPI.dll
00007FFCCE5E0000-00007FFCCE67CFFF 9D000 C:\WINDOWS\System32\msvcrt.dll
00007FFCCE2E0000-00007FFCCE5D8FFF 2F9000 C:\WINDOWS\System32\combase.dll
00007FFCCD3C0000-00007FFCCD4B5FFF F6000 C:\WINDOWS\System32\ucrtbase.dll
00007FFCCFEA0000-00007FFCCFFC4FFF 125000 C:\WINDOWS\System32\RPCRT4.dll
00007FFCCD690000-00007FFCCD6F9FFF 6A000 C:\WINDOWS\System32\bcryptPrimitives.dll
00007FFCCDB00000-00007FFCCDB26FFF 27000 C:\WINDOWS\System32\GDI32.dll
00007FFCCC770000-00007FFCCC8F7FFF 188000 C:\WINDOWS\System32\gdi32full.dll
00007FFCCCBA0000-00007FFCCCC39FFF 9A000 C:\WINDOWS\System32\msvcp_win.dll
00007FFCCD700000-00007FFCCD849FFF 14A000 C:\WINDOWS\System32\USER32.dll
00007FFCCD3A0000-00007FFCCD3BDFFF 1E000 C:\WINDOWS\System32\win32u.dll
00007FFCCFCA0000-00007FFCCFDA7FFF 108000 C:\WINDOWS\System32\COMDLG32.dll
00007FFCCD9F0000-00007FFCCDA99FFF AA000 C:\WINDOWS\System32\shcore.dll
00007FFCCE860000-00007FFCCFC96FFF 1437000 C:\WINDOWS\System32\SHELL32.dll
00007FFCCCB50000-00007FFCCCB98FFF 49000 C:\WINDOWS\System32\cfgmgr32.dll
00007FFCCCC40000-00007FFCCD332FFF 6F3000 C:\WINDOWS\System32\windows.storage.dll
00007FFCCFFD0000-00007FFCD0070FFF A1000 C:\WINDOWS\System32\advapi32.dll
00007FFCCFDB0000-00007FFCCFE08FFF 59000 C:\WINDOWS\System32\sechost.dll
00007FFCCC680000-00007FFCCC690FFF 11000 C:\WINDOWS\System32\kernel.appcore.dll
00007FFCCC630000-00007FFCCC67BFFF 4C000 C:\WINDOWS\System32\powrprof.dll
00007FFCCC610000-00007FFCCC624FFF 15000 C:\WINDOWS\System32\profapi.dll
00007FFCCDC30000-00007FFCCDD74FFF 145000 C:\WINDOWS\System32\ole32.dll
00007FFCD0080000-00007FFCD013FFFF C0000 C:\WINDOWS\System32\OLEAUT32.dll
00007FFCBF0C0000-00007FFCBF326FFF 267000 C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.15063.483_none_26002d27e7c744a2\COMCTL32.dll
00007FFCC1AA0000-00007FFCC1AA9FFF A000 C:\WINDOWS\SYSTEM32\VERSION.dll
00007FFCC21A0000-00007FFCC21C2FFF 23000 C:\WINDOWS\SYSTEM32\WINMM.dll
00007FFCB7D90000-00007FFCB7DA6FFF 17000 C:\WINDOWS\SYSTEM32\NETAPI32.dll
00007FFCC2170000-00007FFCC219AFFF 2B000 C:\WINDOWS\SYSTEM32\WINMMBASE.dll
00007FFCCBD50000-00007FFCCBD5CFFF D000 C:\WINDOWS\SYSTEM32\NETUTILS.DLL
00007FFCC48B0000-00007FFCC48C7FFF 18000 C:\WINDOWS\SYSTEM32\SAMCLI.DLL
00007FFCCDB30000-00007FFCCDB5CFFF 2D000 C:\WINDOWS\System32\IMM32.DLL
00007FFCCAE20000-00007FFCCAEB4FFF 95000 C:\WINDOWS\system32\uxtheme.dll
00007FFCC0440000-00007FFCC0469FFF 2A000 C:\WINDOWS\SYSTEM32\dwmapi.dll
00007FFCAD990000-00007FFCADA30FFF A1000 C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
00007FFCCDDF0000-00007FFCCDE8DFFF 9E000 C:\WINDOWS\System32\clbcatq.dll
00007FFC9EED0000-00007FFC9F0F7FFF 228000 C:\WINDOWS\System32\msxml3.dll
00007FFCCC4E0000-00007FFCCC504FFF 25000 C:\WINDOWS\System32\bcrypt.dll
00007FFCCE6F0000-00007FFCCE855FFF 166000 C:\WINDOWS\System32\MSCTF.dll
00007FFCAB630000-00007FFCABAB1FFF 482000 C:\WINDOWS\system32\explorerframe.dll
000000006F780000-000000006F836FFF B7000 C:\softwares\ConEmu\ConEmu\ConEmuCD64.dll
00007FFCB8AA0000-00007FFCB8B21FFF 82000 C:\WINDOWS\System32\TextInputFramework.dll
00007FFCB8760000-00007FFCB8A31FFF 2D2000 C:\WINDOWS\System32\CoreUIComponents.dll
00007FFCC80E0000-00007FFCC81C2FFF E3000 C:\WINDOWS\System32\CoreMessaging.dll
00007FFCCB900000-00007FFCCB930FFF 31000 C:\WINDOWS\SYSTEM32\ntmarta.dll
00007FFCCA1B0000-00007FFCCA2E8FFF 139000 C:\WINDOWS\SYSTEM32\wintypes.dll
00007FFCC35C0000-00007FFCC35D4FFF 15000 C:\WINDOWS\SYSTEM32\usermgrcli.dll
00007FFCA8EE0000-00007FFCA90A4FFF 1C5000 C:\Windows\System32\uiautomationcore.dll
00007FFCCC440000-00007FFCCC4D9FFF 9A000 C:\WINDOWS\SYSTEM32\sxs.dll
00007FFCC02D0000-00007FFCC033AFFF 6B000 C:\Windows\System32\OLEACC.dll
00007FFCABB60000-00007FFCABBA6FFF 47000 C:\WINDOWS\system32\dataexchange.dll
00007FFCC8E20000-00007FFCC8F41FFF 122000 C:\WINDOWS\system32\dcomp.dll
00007FFCC9ED0000-00007FFCCA1AEFFF 2DF000 C:\WINDOWS\system32\d3d11.dll
00007FFCCB470000-00007FFCCB513FFF A4000 C:\WINDOWS\system32\dxgi.dll
00007FFCCAFB0000-00007FFCCB11FFFF 170000 C:\WINDOWS\system32\twinapi.appcore.dll
00007FFCCAB10000-00007FFCCACBBFFF 1AC000 C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
00007FFCC8780000-00007FFCC8915FFF 196000 C:\WINDOWS\SYSTEM32\PROPSYS.dll
@jackysee try using the "Use legacy console" option until this is solved. That should work. Btw, how did you create that gif?
@alexdevero I'm using Gifcam.
Using legacy mode is not supported in bash for windows. It'll quit the console.
2all: are you using clink? Try to disable it.
I'm not using clink.
I'm not using clink also.
not using clink. just powershell within conemu.
Is the problem reproduced if you run ConEmu64.exe -basic -run cmd
?
I can no longer reproduce the problem. A few days ago I installed all the latest drivers for my Dell XPS laptop which is the only thing I know that has changed.
@Maximus5 problem can still be reproduced with ConEmu64.exe -basic -run cmd
.
Problem description
When I run
yarn install
oryarn upgrade
the progress bar is somehow vertical instead of horizontal and - one-line. Take a look at screenshots below for better understanding. I've tried multiple yarn versions with cmd and ConEmu. CMD always works as expected, ConEmu does not. So, it is not a bug in yarn package manager, but in ConEmu. This issue could be caused by latest Windows 10 Creators Update. Is ConEmu fully compatible with it?Versions
ConEmu build: 1.70402 x64 OS version: Windows 10 x64 (Creators Update 1703) Node.js: 7.9.0 Yarn: v0.23.2
Steps to reproduce
Yarn install
in directory with package.json to install npm packages.Actual results
Broken progress bar:
Expected results
One-line progress bar in cmd and how it looked like a couple days ago in ConEmu: