2
In my directory I have the files files
- x.dll
- x.lib
- x.pdb
- x.exp
- x.plugin
When I issue the command dir \*.*~
it should say 'File not found' as it does at my friend's laptop. But on my machine it lists the file x.plugin
.
Actually after a while of trying I found out that it lists all files with extension longer than 3 characters.
Anybody heard about this behavior before?
This is Windows 7 you are using? – Groo – 2012-10-19T09:12:58.310
yes it is. and it must be quite a new behavior, as it used to work correctly (means only files like x.bak~ being returned for the supplied wildcard) – rezna – 2012-10-19T09:18:50.333
Windows 7 extends the way you can use wildcards (check this answer). But adding a tilde (
– Groo – 2012-10-19T09:23:34.730~
) at the end doesn't seem supported, so the result may be undefined, as you're getting. Adding it at the beginning of the query should tell Win 7 to use DOS style syntax for wildcards (but the tilde itself will be ignored).@Groo: AQS does not seem to be supported at all by the dir command though. – Marcks Thomas – 2012-10-19T09:53:27.800
XP I just get file not found. Even when extension is over 3 char. And even when there are files starting with ~ , and even when there's a file with both features ~df.adfdfd it says File Not Found. What even caused you to do dir .~ ? – barlop – 2012-10-19T09:56:31.753