unicode \u23CE ⏎ character preceding every prompt in fish in WSL #1402
Comments
What ConEmu version do you use exactly? One on the screenshot, another in the issue title. |
Moreover, the question is how do you run new console? |
Well, when I wrote the issue title, I was using 171109 - the latest version bundled with Cmder binary package, as seen hours ago (correct me if I'm wrong) - but on the second screenshot that was 180111. If the inconsistent versions are causing difficulty troubleshooting, I'll reproduce the problem using a 180111 portable build, with a new profile. Fish, Cygwin and wslbridge (built from source) installed hours ago. I don't really remember when I set up my WSL, but the Ubuntu version is 16.04. Running default {Bash:bash} task
Running default {Bash::CygWin bash} task
|
Seems like all correct, except I'm using wslbridge bundled with ConEmu. |
|
CygWin still gave me this after an upgrade. Only one cygwin1.dll exists in cygwin\bin.
|
Fresh cmder? It's a third-party bundle of various software. |
And by that I means I got everything old cleared (some setting went seriously wrong). |
Test result is here. Reinstalled Ubuntu from Microsoft Store.
Old self-buit wslbridge
The wslbridge came with ConEmu
|
Neither of your tests in prev comment are correct.
|
Sorry for the inconvenience; I followed the exact steps given above and here is (hopefully) the right result.
Meanwhile, SSHing from KiTTY inside ConEmu:
This is... unexpected. Maybe some more detailed version info could help? Windows
For testing purpose (and various fix for annoying wsl problems in stable release) I just grabbed the latest Windows 10 Insider from Microsoft, prior to making this post. ConEmuAs an unnecessary confirmation, the window title reads, "Settings [reg] ConEmu 180309 [64] {Preview}". UbuntuFrom Microsoft Store. Changelog says, "20170830.1 build of Ubuntu 16.04 LTS". Installed hours ago (and before that, I was using the old lxrun.exe distributed Ubuntu, exact version unknown). Fish
Miscellaneous settings
That is some weird issue to track. I would love to share some diagnostic data like a memory dump if helpful. |
KiTTY is ChildGui, it renders output internally The issue is really weird because it is not reproduced in my environment at all. Perhaps it depens on some fish or ubuntu settings, I don't know. LogFiles are required.
|
Also
Did you install fish manually? |
No, it's from the official PPA. The one from central apt repository is outdated and lacks some features like |
Please update to 180318 and execute from
the following
I'm interested in screenshots from your default codepage and |
Also I have changed the console font to an official variant of Iosevka before this. Hope this won't affect the results. |
Hm, results are expected. Waiting for log-files |
I need screenshot with the problem and visible StatusBar with TermInfo column. |
...turns out the |
Don't know what happened on your side. Sadly. It may be or may be not ConEmu problem, and without reproduction we can't be sure. |
That is definitely Microsoft conhost bug. The problem is that on CJK Windows versions conhost still behaves differently than on European versions. Conhost fills two cells with single-width glyph! Yeah, it sets the From my tests, a lot of glyphs are treated improperly as double-cell characters on CJK windows (at least all Russian and Greek letters). /cc @miniksa |
We should also consider the situation that ssh from windows to a remote server which used fish rather than windows local |
@Leoyzen What is your comment about? |
Versions
ConEmu build: 180111 x64
OS version: Windows 10 Professional x64 build 16299.192, Chinese (Simplified)
Used shell version: same as Windows
Problem description
Basically same as fish-shell/fish-shell#789, just in WSL instead of Cygwin; another related issue is cmderdev/cmder#1069. Behavior confirmed using a latest (180111) portable build fresh from the download page (a new profile is used, of course).
More precisely, here's the output starting a new task
bash ~ -c fish
(fish stylized with oh-my-fish so output may not match that of a clean install):Starting bash.exe in native console (i.e. cmd.exe) will not print that annoying
⏎
.Steps to reproduce
bash.exe
fish
⏎
.Actual results
Expected results
Additional files
For I just have deleted the downloaded portable version the screenshot was made in Cmder.
The text was updated successfully, but these errors were encountered: