3
I unfortunately need to work with cmd.exe from time to time and it usually doesn't bug me too much except when I am editing a file in vim and then try to run that file with tab-completion.
If I have the file foo.py
open in vim, .foo.py.swp
also exists in the directory. The behavior I see is:
C:\foo> f[TAB]
C:\foo> .foo.py.swp[TAB]
C:\foo> foo.py
This is rather infuriating and I'm wondering if there is any way to prevent this behavior short of a complete workaround like changing my swap file naming or using PowerShell. I did notice PowerShell does not emulate this behavior, but I really don't want to use it.
Why are you so opposed to using PowerShell? – Sasha Chedygov – 2010-09-13T00:22:22.183
I found it less useful than helpful... It's counter-intuitive to both cmd.exe and bash. – djs – 2010-09-19T00:35:42.663
1
There is now an excellent solution to this problem: clink provides bash readline functionality in a native cmd.exe window.
– djs – 2013-05-01T04:36:16.857