Total Commander

AntonyD,

But why?

Because you explicitly disabled the option to treat the file in a special way. I can imagine users wanting to work with the descript.ion files directly. E.g. somebody wants to delete all comments for all files on his hard disk. So search for descript.ion files and delete them. With your wish this would be impossible.
Or e.g. searching comments is faster when searching for descript.ion files containing some text. Searching all files and using "tc - comment - contains - text" is very slow, in comparison.

IS this is so un-logical?

In the context of TC showing and working with what is truly on disk, and not working with "Libraries" feature of Windows, or "Virtual folders" (e.g. Desktop), or translated folder names, it is simply a design decision.

Roman

With your wish this would be impossible.

Possible - we just must have an appropriate code for that logic.
IF selection of some descript.ion was done and after that command DELETE was called - we apply this command on the internal content of this spec.file. BUT - IF after command execution the size of such spec.file has reached 0 - then we can safely fully erase and the file itself from the disk.

AntonyD,
This would make special handling of descript.ion even more special. I don't really see a benefit to this approach, personally, I like TC's idea of showing files as files and treating them specially only when explicitly instructed to do so. But, sure, you can make a suggestion and see if you get support.

Roman