中国DOS联盟

Today I saw a post on the forum about dealing with malformed directories. I tried to create a malformed directory and open it, but found that pushd and explorer commands couldn't open it, but start could. Why is that????? Please explain.

The test code is as follows:
md d:\123..\&&pushd d:\123..\

md d:\124..\&&explorer d:\124..\

md d:\125..\&&start d:\125..\

Come here to discuss:
Non-empty, dot-shaped deformed directory

From the above question, I also found an interesting phenomenon. Please think about what the result is when entering the following commands in the command line??

md "d:\1_13..\"&&start "d:\1_13..\"

md d:\1_14..\&&start d:\1_14..\|(md d:\1_15..\&&start d:\1_15..\)

Oh, can't delete the created file. Depressed ah, what code oh, indeed it's strange - looking ah

The method of deletion, please refer to the post on the second floor.

We see that the originally displayed folder is missing a dot.

If you put a 123 in the same directory.
Then create a 123 directory.
When you access 123., you are actually accessing the 123 folder. So when looking at the size, it can display the size of the 123 directory. If there is no 123 directory, it is 0.

The system recognizes 123. as the attributes of 123... So you can't see the actual size, and the same reason you can't access it by double-clicking is this. After you create 123, it is equivalent to accessing the 123 folder.

You can also delete 123., and there is no error prompt, because it will delete the 123 directory.

PS:
I don't know if you can guess after reading the above?

Accessing a directory with a dot is not necessarily starting with start...

After knowing the above, it is easy to understand...
It should be original hehe. At least I didn't copy it from other places.

md 123..\
Accessing this directory is accessing that malformed directory with a dot, and the size and other things are all okay~

Supplement.
Look at the property directory and there should be a 123 directory.
Look at the property of 123...\ which is that of 123..\.

When deleting, all are to delete the 123 directory.

It seems a bit reasonable, and your method is a good one, but it still can't view the files in the malformed directory.

The test commands are as follows:

First, create two folders:

md d:\123..\&&md d:\123

echo %cmdcmdline%>d:\123..\11.txt&start d:\123..\

Opening the malformed directory with it shows no files.

The following commands can be used to open the text file in it:

start d:\123..\11.txt

type d:\123..\11.txt

Last edited by learner0 on 2008-3-2 at 12:36 PM ]

...This is a problem with the forum system oh.

When posting to another thread, it was clearly enlarged, and it's 123...\
3 dots...

You create an md 123...\

Do you see 11.txt when you double-click in the windows interface? And it can be run.


To see the directory of 123.., you need to create a directory with one more dot. You see that 123.. actually looks at the 123 directory, of course, there are no files.

Well, I understand already..

Uh, I understand.

It seems a bit reasonable, and yours is a good method, but it still can't view the files in the malformed directory

Originally posted by halby at 2008-4-15 00:30:
Seems a bit reasonable, yours is a good method, but still cannot view files in malformed directories

Too lazy to post relevant links, I didn't save... Can see files in n-level directories...
Well, not just see, but also access.

It seems like a high - level discussion, but I don't quite understand it yet.