You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using clink within cmder. I think the problem is in the clink.
To illustrate the problem, let's assume that I executed the following commands in sequence:
dir
pushd c:\temp
cd ..\Tools\
dir /w
popd
Now I want to execute one of the previous commands again. To do this, I press the up arrow key (on the keyboard).
After first pressing the button I see the popd command. For now everything is fine.
After second pressing the button I see the dir /w command. Still all right.
After third pressing the button I see the dcd ..\Tools\ command. Wrong! The first letter of the previous command (letter "d") is displayed before the actual command.
From now on, each subsequent command is preceded by this additional letter (d), for example: dpushd c:\temp, ddir, etc.
If I press Esc, the whole command is deleted, except for this additional letter d.
This additional letter at the beginning is only virtual. For example, if I see a ddir and execute this command, then I will execute the dir command - as if this additional letter was not there at the beginning.
You can live with it, but it's annoying and it interferes with your working comfort.
At first I did not have such problems. It happened at some point. I did not change any settings in the program. I didn't notice anything special that could change this behavior.
Environment: Windows 10 Enterprise ver. 1909
The text was updated successfully, but these errors were encountered:
It's because of a combination of things. There are many posts about it in the Cmder issues list with more information, including how to change the lambda character.
The lambda character that's part of the prompt is represented as different widths in different fonts.
Cmder is using a different font than the OS expects to be used, and the two fonts have different widths for the lambda.
Since this was posted, Clink from chrisant996/clink introduced a change that should compensate for the mismatched font problem, and at least make characters show up in the right spots, although sometimes there will be extra spaces between characters or a line might not fit as many characters as it looks like should fit.
I'm using clink within cmder. I think the problem is in the clink.
To illustrate the problem, let's assume that I executed the following commands in sequence:
dir
pushd c:\temp
cd ..\Tools\
dir /w
popd
Now I want to execute one of the previous commands again. To do this, I press the up arrow key (on the keyboard).
popd
command. For now everything is fine.dir /w
command. Still all right.dcd ..\Tools\
command. Wrong! The first letter of the previous command (letter "d") is displayed before the actual command.d
), for example:dpushd c:\temp
,ddir
, etc.d
.This additional letter at the beginning is only virtual. For example, if I see a
ddir
and execute this command, then I will execute thedir
command - as if this additional letter was not there at the beginning.You can live with it, but it's annoying and it interferes with your working comfort.
At first I did not have such problems. It happened at some point. I did not change any settings in the program. I didn't notice anything special that could change this behavior.
Environment: Windows 10 Enterprise ver. 1909
The text was updated successfully, but these errors were encountered: