Author Topic: Windows CMD TAB auto-complete fix  (Read 2133 times)

0 Members and 1 Guest are viewing this topic.

Offline Kulverstukas

  • Administrator
  • Zeus
  • *
  • Posts: 6627
  • Cookies: 542
  • Fascist dictator
    • View Profile
    • My blog
Windows CMD TAB auto-complete fix
« on: September 10, 2011, 09:15:17 pm »
Well, sometimes Windows doesn't know what to do when TAB is pressed in a CMD. Usually it adds a giant space... hell I want to auto-complete the path you worthless piece of code! I know it sometimes happens to WinXP and Win7. Therefore I made this registry file to fix it. Just double click it and import the value. Now you can use TAB to complete paths once again!

Reg file: http://newage.ql.lt/projects/other/AutoCompleteFix.reg

Offline xzid

  • Knight
  • **
  • Posts: 329
  • Cookies: 41
    • View Profile
Re: Windows CMD TAB auto-complete fix
« Reply #1 on: September 10, 2011, 10:02:08 pm »
On win7 was set to 40h, had no troubles with tab completion in cmd.exe, never changed it..

I use powershell anyway..

Code: [Select]
PS C:\>cd 'HKLM:\SOFTWARE\Microsoft\Command Processor'
PS HKLM:\SOFTWARE\Microsoft\Command Processor>(gp .).CompletionChar
64
PS HKLM:\SOFTWARE\Microsoft\Command Processor>"0x{0:x}" -f (gp .).CompletionChar
0x40
PS HKLM:\SOFTWARE\Microsoft\Command Processor>sp . -name CompletionChar -value 9
PS HKLM:\SOFTWARE\Microsoft\Command Processor>(gp .).CompletionChar
9
PS HKLM:\SOFTWARE\Microsoft\Command Processor>sp . -name CompletionChar -value 64
PS HKLM:\SOFTWARE\Microsoft\Command Processor>"0x{0:x}" -f (gp .).CompletionChar
0x40

condensed:

Code: [Select]
PS C:\>sp 'HKLM:\SOFTWARE\Microsoft\Command Processor' -name CompletionChar -value 9

Offline Kulverstukas

  • Administrator
  • Zeus
  • *
  • Posts: 6627
  • Cookies: 542
  • Fascist dictator
    • View Profile
    • My blog
Re: Windows CMD TAB auto-complete fix
« Reply #2 on: September 10, 2011, 10:57:25 pm »
I only yesterday noticed this in my WinXP CMD. Weird shit, because I didn't have any trouble like that before either. My friend has Win7 and same problem appears for him.
For me it was set to 40 too.