a space between cursor and words?

[kokutoukiritsugu]

ConEmu build: 170402 x64 OS version: Windows 10 10.0.15063 x64

msys2 + zsh + oh-my-zsh

a space between cursor and commands: conemu and realconsol:

same env in mintty:

I delete conemu.xml --> problem still exist.

[soarqin]

I've also got this problem. I think it is caused by Win10 1703(10.0.15063) update. It seems like that MS put their Office Word space control into normal GDI rendering functions.

[Maximus5]

I have absolutely no idea what you are doing... No problems here

[Maximus5]

1. Show your ConEmu/About text
2. I noted that your first command line has no space identation ~faasd asd. And zsh prints ... not found: fasd. No double aa.

[kokutoukiritsugu]

1. minitty works no space with oh-my-zsh. conemu works no space without oh-my-zsh.

2.I can't reproducing now... I don't remember how I did.

[Maximus5]

Mintty is not a Windows full featured terminal. It's just a pty emulator not related to conhost.

Without repro steps this will be closed.

[kvnxiao]

@Maximus5 This issue still persists for me on the latest version 170709, when displaying characters like ➜ in the ConEmu console.

[Maximus5]

@kvnxiao not enough information.

[kvnxiao]

@Maximus5

ConEmu build: 170709 x64 OS version: Windows 10 v1703 (OS Build 15063.483 x64) Used shell: Any bash shell (Ubuntu Windows Subsystem, Cygwin, Git bash)

Pasting → into any bash shell in ConEmu causes it to consume two character-widths, and deleting it with backspace only removes it as if it were a single character-width.

For what it's worth, I'm on Japanese Locale on Windows 10. As you can see in the above gif, the cursor gets offset-ed by one character-width to the right for every time I paste the → character into the console.

[kvnxiao]

Note that this does not happen when I do the same thing in a cmd instance on ConEmu:

[Maximus5]

@kvnxiao I can't check this on Japanese Win10 now. Can you paste several → in bash (where cursor is bad positioned) and make "Dump screen" (ConEmu system menu / Debug). Please attach created file and show text from ConEmu/About/SysInfo.

[kvnxiao]

I pasted exactly 10 →s in the bash console to get the following outputs below (I did not manually input any spaces whatsoever):

Debug Screen dump:

Raw dump .con file: 20170730.con.zip

And here is SysInfo:

ConEmu 170723 [64] Startup Info
  OsVer: 10.0.15063.x64, Product: 1, SP: 0.0, Suite: 0x100, SM_SERVERR2: 0
  CSDVersion: , ReactOS: 0 (), Rsrv: 0
  DBCS: 1, WINE: 0, PE: 0, Remote: 0, ACP: 932, OEMCP: 932, Admin: 0
  StartTime: 2017-07-30 02:15:49.485
  AppID: 49922b4d6ae2ce22bcf871b666573d5f::163
  Desktop: `Winsta0\Default`, SessionId: 1, ConsoleSessionId: 1
  Title: `C:\Program Files\ConEmu\ConEmu64.exe`
  Size: {0,0},{0,0}
  Flags: 0x00000401, ShowWindow: 1, ConHWnd: 0x00000000
  char: 1, short: 2, int: 4, long: 4, u64: 8
  Handles: 0x00000000, 0x00010001, 0x00000000
  Current PID: 5704, TID: 12984
  Active HKL: 0x0000000004091009
  GetKeyboardLayoutList: 0x0000000004091009 0x0000000004090409 0x0000000004110411 0x0000000008040804
CmdLine: "C:\Program Files\ConEmu\ConEmu64.exe" 
ExecMod: C:\Program Files\ConEmu\ConEmu64.exe
WorkDir: C:\Program Files\ConEmu
PathEnv: C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Java\jdk1.8.0_121\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;C:\Program Files\ffmpeg\bin;C:\Program Files\Common Files\Autodesk Shared\;C:\Program Files (x86)\Autodesk\Backburner\;C:\Users\xlzqw\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Ruby23-x64\bin;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\xlzqw\AppData\Roaming\npm;C:\Program Files\PostgreSQL\9.6\bin;C:\adb;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\cygwin64\bin;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\nodejs\;C:\Go\bin;C:\Program Files\erl8.0\bin;C:\Program Files (x86)\Elixir\bin;C:\WINDOWS\system32\config\systemprofile\.mix\escripts;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\Calibre2\;C:\Program Files\Git\cmd;C:\Users\xlzqw\AppData\Local\Programs\Python\Python36\Scripts\;C:\Users\xlzqw\AppData\Local\Programs\Python\Python36\;C:\Users\xlzqw\AppData\Local\Programs\Python\Python36-32\Scripts\;C:\Users\xlzqw\AppData\Local\Programs\Python\Python36-32\;C:\Ruby23-x64\bin;C:\Program Files\PostgreSQL\9.6\bin;C:\Program Files\Redis;C:\Users\xlzqw\AppData\Local\Microsoft\WindowsApps;C:\Users\xlzqw\AppData\Roaming\npm;C:\Program Files\MKVToolNix;C:\Go\bin;C:\Program Files\MongoDB\Server\3.4\bin;C:\Programming\megatools-1.9.98-win64;
ConFont: 0  Lucida Console  00  Consolas    932 *ＭＳ ゴシック    936 *新宋体    000 Droid Sans Mono for Powerline
CMD's AutoRuns: {not defined}
Foreground: x001B2048 {779,425}-{1795,1098} 'VirtualConsoleClass' - bash
MouseCursor: {1883,891} MouseMonitor: 00010001 StartMonitor: 00010001
Display: bpp=32, planes=1, align=1, vrefr=96, shade=x00000000, rast=x00007E99, dpi=96x96, per-mon-dpi=1
Monitors (dpi: WholeDesktop, Effective, Angular, RAW):
  00010003: {2560,174}-{4480,1254} (1920x1080), Working: {2560,174}-{4480,1214} (1920x1040), dpi: {96,96};{96,96};{101,101};{101,101} `\\.\DISPLAY1`
  00010001: {0,0}-{2560,1440} (2560x1440), Working: {0,0}-{2560,1400} (2560x1400), dpi: {96,96};{96,96};{108,108};{108,108} `\\.\DISPLAY2` <<== Primary
Modules:
  00007FF7D2D90000-00007FF7D306AFFF   2DB000 C:\Program Files\ConEmu\ConEmu64.exe
  00007FFD4E820000-00007FFD4E9FAFFF   1DB000 C:\WINDOWS\SYSTEM32\ntdll.dll
  00007FFD4BD90000-00007FFD4BE3DFFF    AE000 C:\WINDOWS\System32\KERNEL32.DLL
  00007FFD4BA60000-00007FFD4BCA8FFF   249000 C:\WINDOWS\System32\KERNELBASE.dll
  00007FFD4DF10000-00007FFD4DF60FFF    51000 C:\WINDOWS\System32\SHLWAPI.dll
  00007FFD4C1A0000-00007FFD4C23CFFF    9D000 C:\WINDOWS\System32\msvcrt.dll
  00007FFD4E520000-00007FFD4E818FFF   2F9000 C:\WINDOWS\System32\combase.dll
  00007FFD3E4E0000-00007FFD3E746FFF   267000 C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.15063.483_none_26002d27e7c744a2\COMCTL32.dll
  00007FFD4AD40000-00007FFD4AE35FFF    F6000 C:\WINDOWS\System32\ucrtbase.dll
  00007FFD4DF70000-00007FFD4DF96FFF    27000 C:\WINDOWS\System32\GDI32.dll
  00007FFD4D6B0000-00007FFD4D7D4FFF   125000 C:\WINDOWS\System32\RPCRT4.dll
  00007FFD4B8D0000-00007FFD4BA57FFF   188000 C:\WINDOWS\System32\gdi32full.dll
  00007FFD4BD10000-00007FFD4BD79FFF    6A000 C:\WINDOWS\System32\bcryptPrimitives.dll
  00007FFD4B080000-00007FFD4B119FFF    9A000 C:\WINDOWS\System32\msvcp_win.dll
  00007FFD4BE40000-00007FFD4BF89FFF   14A000 C:\WINDOWS\System32\USER32.dll
  00007FFD4B010000-00007FFD4B02DFFF    1E000 C:\WINDOWS\System32\win32u.dll
  00007FFD4E260000-00007FFD4E367FFF   108000 C:\WINDOWS\System32\COMDLG32.dll
  00007FFD4DFA0000-00007FFD4E049FFF    AA000 C:\WINDOWS\System32\shcore.dll
  00007FFD4C270000-00007FFD4D6A6FFF  1437000 C:\WINDOWS\System32\SHELL32.dll
  00007FFD4B030000-00007FFD4B078FFF    49000 C:\WINDOWS\System32\cfgmgr32.dll
  00007FFD4B1D0000-00007FFD4B8C1FFF   6F2000 C:\WINDOWS\System32\windows.storage.dll
  00007FFD43FC0000-00007FFD43FC9FFF     A000 C:\WINDOWS\SYSTEM32\VERSION.dll
  00007FFD49080000-00007FFD490A2FFF    23000 C:\WINDOWS\SYSTEM32\WINMM.dll
  00007FFD4D860000-00007FFD4D900FFF    A1000 C:\WINDOWS\System32\advapi32.dll
  00007FFD4E4C0000-00007FFD4E518FFF    59000 C:\WINDOWS\System32\sechost.dll
  00007FFD4ACE0000-00007FFD4ACF0FFF    11000 C:\WINDOWS\System32\kernel.appcore.dll
  00007FFD3D920000-00007FFD3D936FFF    17000 C:\WINDOWS\SYSTEM32\NETAPI32.dll
  00007FFD48FF0000-00007FFD4901AFFF    2B000 C:\WINDOWS\SYSTEM32\winmmbase.dll
  00007FFD4AC90000-00007FFD4ACDBFFF    4C000 C:\WINDOWS\System32\powrprof.dll
  00007FFD4AD00000-00007FFD4AD14FFF    15000 C:\WINDOWS\System32\profapi.dll
  00007FFD4DD50000-00007FFD4DE94FFF   145000 C:\WINDOWS\System32\ole32.dll
  00007FFD4E3A0000-00007FFD4E45FFFF    C0000 C:\WINDOWS\System32\OLEAUT32.dll
  00007FFD4A430000-00007FFD4A43CFFF     D000 C:\WINDOWS\SYSTEM32\NETUTILS.DLL
  00007FFD44280000-00007FFD44297FFF    18000 C:\WINDOWS\SYSTEM32\SAMCLI.DLL
  00007FFD4E370000-00007FFD4E39CFFF    2D000 C:\WINDOWS\System32\IMM32.DLL
  00007FFD493A0000-00007FFD49434FFF    95000 C:\WINDOWS\system32\uxtheme.dll
  00007FFD47AA0000-00007FFD47AC9FFF    2A000 C:\WINDOWS\SYSTEM32\dwmapi.dll
  00007FFD4E050000-00007FFD4E0EDFFF    9E000 C:\WINDOWS\System32\clbcatq.dll
  00007FFD08470000-00007FFD08697FFF   228000 C:\WINDOWS\System32\msxml3.dll
  00007FFD4A850000-00007FFD4A874FFF    25000 C:\WINDOWS\System32\bcrypt.dll
  00007FFD4E0F0000-00007FFD4E255FFF   166000 C:\WINDOWS\System32\MSCTF.dll
  00007FFD2F120000-00007FFD2F5A1FFF   482000 C:\WINDOWS\system32\explorerframe.dll
  000000006F780000-000000006F838FFF    B9000 C:\Program Files\ConEmu\ConEmu\ConEmuCD64.dll
  00007FFD420A0000-00007FFD42121FFF    82000 C:\WINDOWS\System32\TextInputFramework.dll
  00007FFD451A0000-00007FFD45471FFF   2D2000 C:\WINDOWS\System32\CoreUIComponents.dll
  00007FFD48A30000-00007FFD48B12FFF    E3000 C:\WINDOWS\System32\CoreMessaging.dll
  00007FFD472A0000-00007FFD473D8FFF   139000 C:\WINDOWS\SYSTEM32\wintypes.dll
  00007FFD49FF0000-00007FFD4A020FFF    31000 C:\WINDOWS\SYSTEM32\ntmarta.dll
  00007FFD47280000-00007FFD47294FFF    15000 C:\WINDOWS\SYSTEM32\usermgrcli.dll
  00007FFD303E0000-00007FFD30426FFF    47000 C:\WINDOWS\system32\dataexchange.dll
  00007FFD48B20000-00007FFD48C41FFF   122000 C:\WINDOWS\system32\dcomp.dll
  00007FFD48750000-00007FFD48A2EFFF   2DF000 C:\WINDOWS\system32\d3d11.dll
  00007FFD49B00000-00007FFD49BA3FFF    A4000 C:\WINDOWS\system32\dxgi.dll
  00007FFD49660000-00007FFD497CFFFF   170000 C:\WINDOWS\system32\twinapi.appcore.dll
  00007FFD47850000-00007FFD479E5FFF   196000 C:\WINDOWS\SYSTEM32\PROPSYS.dll
  00007FFD24850000-00007FFD249FAFFF   1AB000 C:\WINDOWS\system32\DUI70.dll
  00007FFD38130000-00007FFD381C2FFF    93000 C:\WINDOWS\system32\DUser.dll
  00007FFD45680000-00007FFD4582BFFF   1AC000 C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
  00007FFD2F0C0000-00007FFD2F116FFF    57000 C:\Windows\System32\thumbcache.dll
  00007FFD3FF30000-00007FFD400B7FFF   188000 C:\Windows\System32\Windows.Globalization.dll
  00007FFD42380000-00007FFD423E8FFF    69000 C:\Windows\System32\Bcp47Langs.dll
  00007FFD42A30000-00007FFD42A5FFFF    30000 C:\WINDOWS\SYSTEM32\globinputhost.dll
  00007FFD2EC00000-00007FFD2ECA0FFF    A1000 C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
  00007FFD35640000-00007FFD35683FFF    44000 C:\WINDOWS\SYSTEM32\edputil.dll
  00007FFD3E470000-00007FFD3E4DAFFF    6B000 C:\WINDOWS\system32\OLEACC.dll
  00007FFD2DC60000-00007FFD2DE24FFF   1C5000 C:\Windows\System32\uiautomationcore.dll
  00007FFD4AAF0000-00007FFD4AB89FFF    9A000 C:\WINDOWS\SYSTEM32\sxs.dll
  00007FFD35190000-00007FFD3519AFFF     B000 C:\WINDOWS\SYSTEM32\atlthunk.dll
  00007FFD3E880000-00007FFD3E920FFF    A1000 C:\WINDOWS\System32\StructuredQuery.dll
  00007FFD44850000-00007FFD44D55FFF   506000 C:\Windows\System32\Windows.StateRepository.dll
  00007FFD45040000-00007FFD450E3FFF    A4000 C:\Windows\System32\StateRepository.Core.dll
  00007FFD20AC0000-00007FFD20B89FFF    CA000 C:\WINDOWS\system32\Windows.Storage.Search.dll
  00007FFD4D7E0000-00007FFD4D850FFF    71000 C:\WINDOWS\System32\coml2.dll
  00007FFD43A80000-00007FFD43FB0FFF   531000 C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
  00007FFD351A0000-00007FFD351AFFFF    10000 C:\WINDOWS\SYSTEM32\LINKINFO.dll
  00007FFD36D70000-00007FFD36D8AFFF    1B000 C:\WINDOWS\SYSTEM32\MPR.dll
  00007FFD38120000-00007FFD3812AFFF     B000 C:\WINDOWS\System32\drprov.dll
  00007FFD49DF0000-00007FFD49E44FFF    55000 C:\WINDOWS\System32\WINSTA.dll
  00007FFD36D90000-00007FFD36DA5FFF    16000 C:\WINDOWS\System32\ntlanman.dll
  00007FFD34960000-00007FFD3497FFFF    20000 C:\WINDOWS\System32\davclnt.dll
  00007FFD377E0000-00007FFD377EBFFF     C000 C:\WINDOWS\System32\DAVHLPR.dll
  00007FFD45E20000-00007FFD45E35FFF    16000 C:\WINDOWS\System32\wkscli.dll
  00007FFD40520000-00007FFD40531FFF    12000 C:\WINDOWS\SYSTEM32\cscapi.dll
  00007FFD49260000-00007FFD492DDFFF    7E000 C:\WINDOWS\SYSTEM32\apphelp.dll
  00007FFD20800000-00007FFD20849FFF    4A000 C:\Windows\System32\dlnashext.dll
  00007FFD3EDA0000-00007FFD3EE0CFFF    6D000 C:\Windows\System32\PlayToDevice.dll
  00007FFD39770000-00007FFD3978DFFF    1E000 C:\Windows\System32\DevDispItemProvider.dll
  00007FFD30330000-00007FFD303B1FFF    82000 C:\Windows\System32\twinapi.dll
  00007FFD42710000-00007FFD42776FFF    67000 C:\WINDOWS\System32\MMDevApi.dll
  00007FFD49810000-00007FFD49837FFF    28000 C:\WINDOWS\System32\DEVOBJ.dll
  00007FFD28380000-00007FFD2841BFFF    9C000 C:\Windows\System32\PortableDeviceApi.dll
  00007FFD4D910000-00007FFD4DD4AFFF   43B000 C:\WINDOWS\System32\SETUPAPI.dll
  00007FFD4BCB0000-00007FFD4BD05FFF    56000 C:\WINDOWS\System32\WINTRUST.dll
  00007FFD4AD20000-00007FFD4AD30FFF    11000 C:\WINDOWS\System32\MSASN1.dll
  00007FFD4AE40000-00007FFD4B008FFF   1C9000 C:\WINDOWS\System32\CRYPT32.dll
  00007FFD32FD0000-00007FFD33005FFF    36000 C:\Windows\System32\EhStorShell.dll
  00007FFD262A0000-00007FFD262C4FFF    25000 C:\Windows\System32\EhStorAPI.dll
  00007FFD47820000-00007FFD47832FFF    13000 C:\Windows\System32\WTSAPI32.dll
  00007FFD2B240000-00007FFD2B2BEFFF    7F000 C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CoreSyncExtension\CoreSync_x64.dll
  00007FFD4A760000-00007FFD4A76AFFF     B000 C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL
  00007FFD2AC50000-00007FFD2B235FFF   5E6000 C:\Users\xlzqw\AppData\Local\Microsoft\OneDrive\17.3.6943.0625\amd64\FileSyncShell64.dll
  00007FFD3EE10000-00007FFD3F13DFFF   32E000 C:\WINDOWS\SYSTEM32\WININET.dll
  00007FFD3E870000-00007FFD3E878FFF     9000 C:\WINDOWS\SYSTEM32\WSOCK32.dll
  00007FFD4DEA0000-00007FFD4DF0BFFF    6C000 C:\WINDOWS\System32\WS2_32.dll
  00007FFD4A340000-00007FFD4A376FFF    37000 C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
  00007FFD319F0000-00007FFD31B16FFF   127000 C:\WINDOWS\system32\NetworkExplorer.dll
  00007FFD16530000-00007FFD1682DFFF   2FE000 C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesX64\Microsoft Office\Office16\GROOVEEX.DLL
  00007FFD3E100000-00007FFD3E115FFF    16000 C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
  00007FFD26200000-00007FFD2629BFFF    9C000 C:\WINDOWS\SYSTEM32\MSVCP140.dll
  00007FFD367D0000-00007FFD36BB3FFF   3E4000 C:\WINDOWS\SYSTEM32\msi.dll
  00007FFD28CA0000-00007FFD28CC3FFF    24000 C:\WINDOWS\system32\mssprxy.dll
  000001B1DE2E0000-000001B1DEB62FFF   883000 C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesX64\Microsoft Office\Office16\1033\GrooveIntlResource.dll
  00007FFD25750000-00007FFD257E6FFF    97000 C:\Users\xlzqw\AppData\Local\MEGAsync\ShellExtX64.dll
  00007FFD381D0000-00007FFD38294FFF    C5000 C:\WINDOWS\System32\cscui.dll
  00007FFD2C600000-00007FFD2C6D5FFF    D6000 C:\WINDOWS\SYSTEM32\ntshrui.dll
  00007FFD4ABC0000-00007FFD4ABEFFFF    30000 C:\WINDOWS\SYSTEM32\SspiCli.dll
  00007FFD3C8B0000-00007FFD3C8D5FFF    26000 C:\WINDOWS\SYSTEM32\srvcli.dll
  00007FFD40830000-00007FFD409F6FFF   1C7000 C:\WINDOWS\SYSTEM32\urlmon.dll
  00007FFD40D50000-00007FFD40FD9FFF   28A000 C:\WINDOWS\SYSTEM32\iertutil.dll
  00007FFD3E2D0000-00007FFD3E464FFF   195000 C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.15063.483_none_56eb200d4259be70\GdiPlus.dll

[jxskiss]

This issue also confuse me for days. Some feedback here. I'm running the latest windows 10 rs3 1709, with a fresh downloaded portable ConEmuPack.170807,

1. default cmd, works well, no extra space on command line
2. default bash invoked with either "bash.exe" or "wsl.exe", works well, no extra space.
3. zsh without oh-my-zsh invoked with "wsl.exe zsh", works well, no extra space.
4. zsh with oh-my-zsh invoked with "wsl.exe zsh", with oh-my-zsh enabled, THE EXTRA SPACE APPEARS., and behaves like the above comments.

Don't know where the problem is, just feedback.

[jxskiss]

Also, after tried bash-it, it also has this SPACE issue (bare bash session not).

[jxskiss]

https://github.com/robbyrussell/oh-my-zsh/issues/6007#issuecomment-299684982

KuromiAK commented on 7 May: After some testing (161206 stable), it appears that ConEmu is confused by character '➜' (arrow in robbyrussell), '' (powerline arrow) and '' (powerline branch symbol). The symbols are supposed to be 1 character wide but ConEmu advances cursor by 2 characters when they are inputed. ConEmu also only retracts by 1 character when these symbols are deleted.

I can confirm the issue only appears with oh-my-zsh theme enabled. Is there any plan to fix this?

As workaround, just copy the theme to custom directory, and drop or replace the characters fix this.

[Maximus5]

This looks like a bug in conhost.

@miniksa Can you check this, please?

[miniksa]

Filed internally as MSFT:14257822.

[kvnxiao]

@jxskiss Just FYI, the issue is not exclusive to oh-my-zsh themes being enabled. I am not using oh-my-zsh nor any of it's default provided themes. The matter is with the specific characters being inputted into the console.

[miniksa]

The issue is that you're using characters that have a variable column count depending on the font. We continuously make improvements to these sorts of things, but there are a lot of characters and fonts in the world. We'll get to looking at this.

[miniksa]

The same thing is happening for me with か in ConEmu. The cursor positions in the bottom right corner of ConEmu are skipping by 2 when using left and right arrow keys as is expected for two-column width fonts, but the drawing of the cursor in ConEmu seems misaligned.

Even when I set the console to the legacy console mode and with codepage 932 and paste in か characters, the cursor drawing in ConEmu seems misaligned even though the column count in the bottom right is correct and skipping by 2 as I use the left and right arrows.

I think this is a ConEmu issue in calculating the correct position for drawing the cursor. From what I can see, ConHost is reporting the correct number of columns for the characters when it can based on the font it has selected. It is also showing the cursor in the correct position in the underlying ConHost window when you open it with Ctrl+Win+Alt+Space.

[Maximus5]

https://conemu.github.io/blog/2017/12/03/Build-171203.html

Glyphs widths is a mess. ConEmu tries to draw glyph widths properly, but what about columns? My point is that StatusBar must show characters count instead of some abstract column indexes taking into account one, two or more cells they use.

How many times user have to press BS key or Left/Right key to move by one character? One time per character. How many symbols would be placed in the clipboard when user selects the "か"? One character.

So ConEmu shows cursor position in characters as normal text editors do.

But conhost API return "columns" and it's rather tricky to obtain proper cursor position.

[iamkissg]

Hi all,

I just came across the same issue: a hateful space between cursor and words.

After changing the theme (robbyrussel ->kennethreitz), however, the issue seems to get solved.

If you just wanna remove the space but don't care its cause, just try it.

[Maximus5]

@Engine-Treasure You didn't tell us ConEmu version

[yxliang01]

Problem still persists on 180114, Win10 1709 when executing zsh with oh-my-zsh in both CMD and Powershell. However, the cursor is at the right position in the real console.

[Maximus5]

when executing zsh with oh-my-zsh

zsh from which package: msys2/cygwin/wsl/else?

in both CMD and Powershell.

Do you run cmd.exe / powershell.exe in ConEmu and from their prompt run zsh.exe?

[yxliang01]

zsh executed by a bash under WSL environment. And the WSL environment was entered by executing bash under both (cmd.exe executed by powershell.exe) and (powershell.exe).

[Maximus5]

I said many times, that due to bugs in bash (WSL) the only correct way to run WSL in ConEmu is wslbridge.

[Maximus5]

However, I don't observe wrong cursor position after ConEmu64.exe -basic -run powershell.exe. Even if I don't run WSL via wslbridge (directly bash.exe from powershell prompt).

[yxliang01]

@Maximus5 I'm sorry that I didn't notice the newly invented tools. However, even in a zsh executed by the bash shell opened by the bash task (the one using connector), the problem still persists. Would you like to have additional information for this?

[yxliang01]

Oh By the way, I forgot to mention that this happens just these few days. I did do a Windows Update and I forgot whether this only happened after the update. @Maximus5 Are you using Win10 1709? I am thinking whether this is related to the update.

[Maximus5]

Yes. Win 10 1709.

I need the following

• About/SysInfo
• LogFiles and Screenshot of Info settings page when you observe cursor glitch

[jakara]

still have this issue on windows 10 1709. and looks like it happens on all powerline themes, not just ZSH in WSL, for example I'm using powershell+on-my-posh+agnoster theme. and this theme works fine in native powershell console.

Another interesting thing i've been notice is that, this happens when I set the "Language for non-unicode program" = zh_cn, if I change this value to enus, it works perfectly, but then the native powershell won't show chinese charactors any more, regardless any codepage, encoding settings ><

Dose anyone know how to make this Language for non-unicode program setting only set for ComEmu/cmder?

[Maximus5]

https://github.com/Maximus5/ConEmu/issues/1106#issuecomment-361411132

[Maximus5]

still have this issue on windows 10 1709.

No ConEmu version.

this happens when I set the "Language for non-unicode program" = zh_cn

It does not matter. Terminal should work properly in any OS settings.

if I change this value to enus, it works perfectly, but then the native powershell won't show chinese charactors any more, regardless any codepage, encoding settings ><

That's interesting, but I don't think it's related.

[jakara]

@Maximus5 I‘m using ConEmu 180206 [64] {ALPHA}, via cmder(portable).

I'm not sure whether this issue is related to system locale setting, but: in zh_cn: the cursor position is wrong, but native powershell: works fine!

in en_us: cmder works perfectly, but the native: wont show any chinese charactor

[Maximus5]

Only one question: why do you use old ConEmu build?

[sql-sith]

@jakara For Powershell to show Chinese characters, you may have to change your Powershell font. You can check by clicking the control box (the Powershell icon way up in the top-left corner of the Window) and choosing Properties and checking the font in there. I use a font I really like (Bitstream Vera Sans Mono) but I can't use it well for CJK characters. In this screenshot, I pasted in the character 皑:

However, if I go to Properties and just change the font to NSimSun (or any font with good CJK support) and the character appears properly. I didn't even have to re-type it. I think it may be possible that you are accidentally using a font that doesn't support the characters you need. Just a thought.

[Maximus5]

@jakara Don't you speak about native console window? But it does not relate to ConEmu and this issue, isn't it? This issue is opened too long, too many versions of Windows 10 and ConEmu were released and I still have not received information about actual state. If one observe cursor problem with current version of ConEmu, don't hesitate to create new issue (you may post link to this one) with information: versions, screenshots, output of ConEmuC -checkunicode and Abous/SysInfo.

[jeud]

Dear @jakara

I have found this guideline setting https://github.com/fredjoseph/cmder-powerline-prompt, unfortunately it's for Cmder.

I have installed some powerline fonts, and this is my current setting.

Unfortunately the prompt has no changes, please guide what should I do, because according to the guide line Cmder and ConEmu seem to have different folder structure I'm not sure it's about executing .lua files or not, so I have no ideas what further to go because most guideline I could find are about ConEmu with PowerShell or Cmder, but I intend to use the powerline font with MS-DOS prompt not PowerShell.

Please guide, thanks.

[villivateur]

Hi all, I just came across the same issue: a hateful space between cursor and words.

After changing the theme (robbyrussel ->kennethreitz), however, the issue seems to get solved.

If you just wanna remove the space but don't care its cause, just try it.

Thanks, but I want to know how to change the theme for cmder.

[bohrasd]

kennethreitz works well but still seeking for a solution with other themes.