Total Commander

1. cd C:\Windows
2. cd ::
3. cm_OpenNetwork
4. cd ::{450D8FBA-AD25-11D0-98A8-0800361B1103}
5. cd ::{D20EA4E1-3957-11d2-A40B-0C5020524153}
6. cd ::{} or cd ::{BLABLA} >>> 1.

It's expected that there will be no path change in case of an error.

Agreed, but then there should be an error displayed: "directory not found!" - currently the loading of the last physical directory, gives an indication that there has been a fault.

If I execute cd C:\path\nopath, then it will open C:\path, there will be no indication of an error.
If I specify a non-existent drive (cd W:\blabla), then also no windows will appear.

Fla$her wrote: ↑2024-02-03, 01:04 UTC If I execute cd C:\path\nopath, then it will open C:\path, there will be no indication of an error.
If I specify a non-existent drive (cd W:\blabla), then also no windows will appear.

That's easy: Then don't do either of those things.

Really: Who does something like that?

And if he does, he will immediately notice his own mistake...

TC is a GUI file manager...

2JOUBE
This is a section about bugs, not about who and what can/wants to do or not do here.

JOUBE wrote: ↑2024-02-03, 02:36 UTCAnd if he does, he will immediately notice his own mistake...

So you approve of my counterargument? >>>

petermad wrote: ↑2024-02-03, 00:52 UTC... there should be an error displayed: "directory not found!"

>>>

Fla$her wrote: ↑2024-02-03, 01:04 UTC ... there will be no indication of an error.

2Fla$her

If I specify a non-existent drive (cd W:\blabla), then also no windows will appear.

That depends on the setting of IgnoreDirErrors.
With IgnoreDirErrors=1 I get a dialog box:

--------------------------------------
ERROR!
--------------------------------------
Drive not found W:
Please chose another: [ ]
[OK] [Cancel]
--------------------------------------

And if I perform cd: W: - and W: does not exist. I get a the same dialog box if I am in the root of a drive. If I am in a subdirectory
I get a message in the file panel saying: <Read error!>

2petermad
Good. So, in this case, your wish should be related to the non-default value of 1 of the given key.
I think this would have been provided for without our meddling.

cd ::INVALID
returns to the last local directory. Currently there are no plans to change this behavior.

Moderator message

2ghisler(Author)
What is the reason for the choice of such unexpected behavior by users?
Why leave such a mismatch with cd <INVALID DRIVE>:\... ?

Total Commander always needs to show a valid directory. When a cd command fails, TC returns to the last local directory it knows. Since virtual folders can be anything, including network folders, it's not guaranteed that you can return to it when trying to go to a different virtual folder fails.

The option IgnoreDirErrors=1 only supports directories with a path (drive letter or UNC), not virtual folders. Making it work with virtual folders isn't easy, it would take weeks to make it work properly.

Look at what I wrote:

Fla$her wrote: ↑2024-02-02, 23:44 UTC It's expected that there will be no path change in case of an error.

This is the current behavior after cd <INVALID DRIVE>:\. I didn't suggest trying to go back to the virtual folder. I'm asking you to remove the discrepancy by eliminating the need to search and navigate to a local folder.

PS: I think the bugs section is more appropriate for inconsistencies.

No path change is currently only supported in a regular directory, not in a virtual folder, sorry.

Don't you think it's strange what you wrote? Logically, regular folders should be a priority for users and the file manager.
But that's not the point. From the point of view of usability, why go to the previous local folder in case of an error, if it's much better to leave the current one, whatever it is?

Fla$her wrote: ↑2024-02-05, 10:40 UTC From the point of view of usability, why go to the previous local folder in case of an error, if it's much better to leave the current one, whatever it is?

Fully agree.
TC should stay where it was before trying the failed path.
There should be an error message in this case to warn the user.

if it's much better to leave the current one, whatever it is?

I agree - but if no folder change is taking place - I still think a message about not being able to go to the dir would be a good idea - otherwise you might end up trying to change the directory several times before you realize it is prevented by TC.