Deleting characters is buggy in git-bash on Windows 10

[jiangfengming]

This occurs when deleting too fast. Only in git-bash, powershell has no problem.

[jiangfengming]

It also effects Bash on Ubuntu on Windows.

[levsthings]

Having the same problems with git-bash. Deleting characters with backspace or traversing back and forth with arrow keys is very buggy.

[LancelotLewis]

Having the same problem in win10

[Aetherall]

Same problem over here !

Deleting characters with backspace or traversing back and forth with arrow keys is very buggy!

Where does it comes from?
Someone has an idea about how to fix it ?

Using git-bash on Windows 10

[ivalkenburg]

Same problem, also using git-bash

[drazik]

Yes, same here. git-bash on Windows 10 too.

[celestialorb]

Same problem here using cygwin on Windows 10.

[P403n1x87]

Same using git-bash on win10

[shayaShav]

Tried em all.. git-bash, cmder and Ubuntu bash on win 10. All buggy. Impossible to work with :(

[P403n1x87]

The steps at jeremyramin#15 (comment) seem to have "fixed" the problem in my case

[grig0ry]

Try disabling Cursor Blink option.

[clayms]

same problem.

Disabling Cursor Blink option does not fix.

Windows 10 Enterprise x64
Atom 1.25.0 x64
platformio-atom-ide-terminal 2.8.1
git version 2.14.3.windows.1

Shell Override - C:\Program Files\Git\bin\bash.exe

[Onfire7]

Same issue when using cmd.exe as the shell...

Windows 10 X64
Atom 1.28.2
Platformio-ide-terminal 2.8.3

Enabling legacy mode on the command prompt fixes this issue...

[the-j0k3r]

@Onfire7 well 23 people had the issue fixed by this jeremyramin#15 (comment) which is what #575 proposes, yet the majority 90 people say this has no effect.

Its interesting results I think YMMV really

[P403n1x87]

It would be good to have a fix for this as the legacy more seems to break WSL. Perhaps the tech details here could be useful.

[the-j0k3r]

I agree but this project is no longer under active development, If someone submits a fix I dont mind pinging people to try get attention to it.

I wouldn't use WSL any and all malicious code bypasses all security if it comes via WSL.

[Onfire7]

@the-j0k3r Interesting... I would point out though, that people are FAR more likely to downvote something that isn't working, then to upvote something that is, so I would tend to believe that that leans more towards working for at least 50% of people. That said, 90+ is still a lot of people, so something else is definately going on...

I'm rather inclined to believe that those people that it didn't fix the issue for have 2+ seperate issues going on though... Mainly because it's known to cause the exact same issue with several other terminals... I guess the real question isn't so much "Will enabling legacy mode fix my terminal problems?" but rather "Is legacy mode required for my terminal to work on a fully up to date Windows 10 system, while using an alternate shell?" To answer that question:

TL;DR:

Does anyone have a fully up to date Windows 10 system with legacy mode disabled, and an alternate shell setup in platformio-atom-ide-terminal that is working without the caret bugs? If so, what shell (with version, preferably) is it using?

[the-j0k3r]

Does anyone have a fully up to date Windows 10 system with legacy mode disabled, and an alternate shell setup in platformio-atom-ide-terminal

Yes, me for instance, Ive tried using bash, cmd.com several times and cant duplicate this issue.

I cant duplicate 99% of issues reported, there are a couple of issues I have that are related to platformio-ide-terminal showing old text form a large interactive git rebase that clogs up the terminal view.

In any case, legacy console doesn't fix it, and like @P403n1x87 pointed out it breaks WSL (Windows subsystem for Linux)

I think people that have most of these issues I cant duplicate would do well in trying fresh Atom configurations like described in Atom debugging page, or start by disabling non core packages one by one testing in between and close reopen a terminal to see if issue persists, until the issue is gone, or you run out of external extension to disable,

TL;DR:
This project is no longer under active development (read #543 if you haven't already), and unless a more robust code is submitted by someone via PR, bugs that are caused by external packages or some Atom configuration or by some conflict with some external package, or because Atom doesn't fully support XYZ we are all SOL.

[P403n1x87]

I think at some point I have got something "working" by using the method described in the ConEmu documentation:

set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & %ConEmuBaseDirShort%\conemu-cyg-64.exe --wsl -cur_console:pm:/mnt

If it wasn't this then it must have been wslbridge. One way or the other I've got Bash from WSL working, but I couldn't use the arrows to scroll through the history, so not much use.
I would have a look at the code myself to see if there's anything that can be done, but at the minute I'm busy with other projects.

[ujeshurun]

Same issue on my pc. Windows 10, Git Bash. This is a great tool. Would love to see it work properly.

[marcusnewton]

Bump. Still happening with Git Bash on windows. If anyone knows of an alternate atom package for using Git Bash shells in atom hit me up

[the-j0k3r]

Please retest again with platformio-atom-ide-terminal 2.9.0.
These type issues all so far seem fixed with this release due to using node-pty-prebuilt instead unmaintained and outdated pty.js