Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prompt: Display contains artifacts when browsing command history after Commit 4121fc3d73104765c18a93131d4eedf51c0710a0 #585

Closed
robi-wan opened this issue Mar 16, 2016 · 3 comments

Comments

@robi-wan
Copy link

First of all: thanks for this project - it is a great help!

ConEmu version 160313
Clink v0.4.5 (seems to have no influence to this issue)
Windows 7 64bit
Shell: cmd.exe (Default task)

When I enter a command which contains a backslash and later browse through command history via arrow up/down keys the prompt contains artifacts as soon as I hit this command with a backslash (example session):

$ vim test\my_test.ex
Edit file and quit vim.
Rename another file:
$ copy test\my_dumb_test.ex test\my_cool_test.ex
$ mix test
executes test
$
Now I want to go back to edit my testfile: I press arrow up:
$ mix test
Not quite there:
$ copy test\my_dumb_test.ex test\my_cool_test.ex
So another arrow up:
$ copy testvim test\my_test.ex

The prompt shows the text copy test in front of the actual command - it seems to be just a visual issue as copy test is not part of the command (when I hit enter key just vim test\my_test.ex is executed).

Reverting the change in Release/ConEmu/CmdInit.cmd in commit 4121fc3 fixes this issue.
Maybe the trailing $E\ causes this...

@Maximus5
Copy link
Owner

Why do you think that clink have no influence to this issue?

Clink has, and more, issue was filled (and closed) here and on clink project site.

@Maximus5
Copy link
Owner

gh-563

@robi-wan
Copy link
Author

Ok, sorry.
I had Clink 0.4.7 installed and reverted to Clink 0.4.5 - issue still existed. I edited the CmdInit.bat and issue was gone - therefore I thought, Clink had no influence on this issue.
Now I uninstalled Clink and (with the original/current CmdInit.bat script) it works as expected.

Thanks for the quick response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants