This topic is for reference and discussion.
If you use the wildcard * for the filename when renaming/inplace renaming/moving/copying files, the filename extension is cut off.
This seems to be a leftover from the MS-DOS era before long filename support. I tested it with MS-DOS 6.22 and using COPY and REN does the same. But nowadays when you do the same in the Windows Command Prompt window (cmd.exe), * means full filename.
Is it still useful that when using * the filename extension is not included? Should it be changed or kept for compatibility reasons?
Wildcard * does not include extension when renaming and copying.
Moderators: Hacker, petermad, Stefan2, white
Re: Wildcard * does not include extension when renaming and copying.
For me, yes.white wrote: 2024-10-17, 14:25 UTC Is it still useful that when using * the filename extension is not included? Should it be changed or kept for compatibility reasons?
There are many cases in which a group of files need new names.
But why should the extensions changed ?
The files don't change their type, only in rare cases.
Windows 11 Home, Version 24H2 (OS Build 26100.3915)
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64