vefatica May 12,976 172 Jun 26, 2015 #1 I may just never have tried this before, but ... Before pressing <tab> Code: do d in /s /d"c:\prog (cursor at end). After pressing <tab> Code: c:\> "Documents and Settings"\ d in /s /d"c:\prog (cursor after "...ings"\)
I may just never have tried this before, but ... Before pressing <tab> Code: do d in /s /d"c:\prog (cursor at end). After pressing <tab> Code: c:\> "Documents and Settings"\ d in /s /d"c:\prog (cursor after "...ings"\)
rconn Administrator May 13,075 196 Staff member Jun 26, 2015 #2 WAD. TCC doesn't know where you want your single double quote to match up - to the beginning of the line, or to the end of the line. Add another quote at the end before pressing tab, and everything will work as you expect.
WAD. TCC doesn't know where you want your single double quote to match up - to the beginning of the line, or to the end of the line. Add another quote at the end before pressing tab, and everything will work as you expect.
vefatica May 12,976 172 Jun 26, 2015 #3 OK, thanks. But if it so completes c:\programdata (as desired) if removes the quotes needed by DO's "/D". No big deal.
OK, thanks. But if it so completes c:\programdata (as desired) if removes the quotes needed by DO's "/D". No big deal.
rconn Administrator May 13,075 196 Staff member Jun 26, 2015 #4 vefatica said: OK, thanks. But if it so completes c:\programdata (as desired) if removes the quotes needed by DO's "/D". No big deal. Click to expand... It's behaved that way since LFNs first appeared. You could upgrade to the DWIM parser, or you could help out the parser and add the second ".
vefatica said: OK, thanks. But if it so completes c:\programdata (as desired) if removes the quotes needed by DO's "/D". No big deal. Click to expand... It's behaved that way since LFNs first appeared. You could upgrade to the DWIM parser, or you could help out the parser and add the second ".
vefatica May 12,976 172 Jun 26, 2015 #5 rconn said: It's behaved that way since LFNs first appeared. You could upgrade to the DWIM parser, or you could help out the parser and add the second ". Click to expand... Yes, that works. AS often as I do it, it really doesn't matter. But I still enjoy the enhancement to tab completion made a few versions ago ... that the thing you want to complete doesn't require a space before it. Code: %FUNCTION[bla<tab > is very convenient. So is the added space after completing the first word in a command line.
rconn said: It's behaved that way since LFNs first appeared. You could upgrade to the DWIM parser, or you could help out the parser and add the second ". Click to expand... Yes, that works. AS often as I do it, it really doesn't matter. But I still enjoy the enhancement to tab completion made a few versions ago ... that the thing you want to complete doesn't require a space before it. Code: %FUNCTION[bla<tab > is very convenient. So is the added space after completing the first word in a command line.