Autocomplete with backslash on paths?

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Mar 21, 2011
30
0
#1
Is it possible to have TCC/LE autocomplete with backslashes on paths, like in bash?

I tried searching the forum but could not find anything.

Cheers
 
Mar 21, 2011
30
0
#3
Type OPTION and press Enter; you'll get a configuration dialog. Select the "Command Line" tab. The lower-left portion of this page has several options affecting filename completion; you want the third one down.
Oh that's great. I was not actually expecting a positive reply on this. It looks like there are a lot of interesting options to explore.

Could you tell me if it is possible to stop CD from autocompleting files, like CMD does? It seems stupid for it to autocomplete irrelevant stuff.

Thanks.
 
D

drrob1

Guest
#7
On 04/17/2011 12:07 PM, Charles Dye wrote:

> ---Quote (Originally by David Marcus)---
> In Option> Command Line> Filename Completion> Options, I have "cd cdd rd:dirs".
> ---End Quote---
> MD and PUSHD might make sense there, too.
As long as we are on the subject of file name completion, is it possible
to have file name completion at the prompt also include files other than
.exe or .btm? For example, I like using executible extensions so I do
this a lot:
taxes.xls

and excel will start w/ taxes.xls loaded. But I cannot use tab to
autocomplete here.

Can I set it up so that <tab> at a command prompt will include
executable extension files for MS-office?

Thanks
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
3,376
39
Albuquerque, NM
prospero.unm.edu
#8
As long as we are on the subject of file name completion, is it possible
to have file name completion at the prompt also include files other than
.exe or .btm? For example, I like using executible extensions so I do
this a lot:
taxes.xls

and excel will start w/ taxes.xls loaded. But I cannot use tab to
autocomplete here.
<tab>
If you set up .XLS as an executable extension, then tab completion will offer Excel files:

Code:
set .xls=excel.exe /e
If you want to complete some filename for which you don't have an executable extension set, type a space before it. Then your filename isn't at the very start of the command line, so the special rules don't apply.

</tab>
 
D

drrob1

Guest
#9
thanks.

On 04/17/2011 02:17 PM, Charles Dye wrote:

> If you set up .XLS as an executable extension, then tab completion will offer Excel files:
>
>
> Code:
> ---------
> set .xls=excel.exe /e
> ---------
> If you want to complete some filename for which you don't have an executable extension set, type a space before it. Then your filename isn't at the very start of the command line, so the special rules don't apply.
>
> </tab>
>
> Charles Dye
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#10
If you're talking about autocomplete, there's
nothing to complete yet if you're making a directory. So MD and MKDIR
wouldn't accomplish much.

-Scott

David Marcus <> wrote
on 04/17/2011 12:24:15 PM:


>
> Originally Posted by Charles Dye [image removed]
> MD and PUSHD might make sense there, too.
>
> Looks like mkdir needs to be listed too.
>
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#13
Yeah I realized that *after* I hit send.
:)

-Scott

Charles Dye <> wrote
on 04/17/2011 10:10:56 PM:


> Originally Posted by samintz [image removed]
> If you're talking about autocomplete, there's
> nothing to complete yet if you're making a directory. So MD and MKDIR
> wouldn't accomplish much.
>
> Ah, but sometimes you create a directory inside another directory.

> (But you never create a subdirectory inside a file....)
>