WAD Executing rename.py -y trigger internal rename command

[char101]

Hi,

Executing

> rename.py -y

triggers the internal rename command (i.e. trying to rename ".y" to "-y") which results in "TCC: (Sys) The system cannot find the file specified." message.

I expect it to run the script rename.py in the current directory with -y as parameter, since there is no space between "rename" and ".py".

 

[rconn]

Executing

> rename.py -y

triggers the internal rename command (i.e. trying to rename ".y" to "-y") which results in "TCC: (Sys) The system cannot find the file specified." message.

I expect it to run the script rename.py in the current directory with -y as parameter, since there is no space between "rename" and ".py".

WAD - this is a CMD-compatibility issue. CMD does not require a space after an internal command name (i.e., "echo.", "dir\", etc.).

To force TCC/LE to use the script, enter:

.\rename.py -y

 

[char101]

Except it works fine with cmd.exe without using "\.".

cmd.exe> rename.py -h
usage: rename.py [-h] [-y]

optional arguments:
-h, --help show this help message and exit
-y, --yes

tcc.exe> rename.py -h
TCC: (Sys) The system cannot find the file specified.
"C:\.py"
0 files renamed

Also TCC/LE behavior is inconsistent since running

> rename.py

runs the "rename.py" script while

> rename. py -y

runs the internal rename command.

 

[Charles Dye]

There are a number of ways you could deal with this. Perhaps the simplest is to just

setdos /i-rename

Nobody ever uses RENAME, right? When REN does the exact same thing?

 

[char101]

Thanks, "setdos /i-rename" does the trick .

I still think that to be cmd.exe compatible, tcc/le need to give external command a priority over internal command when the command ".extension" is given in the command line.

 

[rconn]

Except it works fine with cmd.exe without using "\.".

That's because CMD has a different parser for every command. TCC(/LE) uses a single, consistent parser for all commands.