1
Support and Feedback / Re: I can no longer move from a child directory into it's parent...
« on: May 25, 2023, 16:06:07 »
Sorry for the delay. Busy these days...
I had a chance to do a little more testing and the problem appears when MC is executed through a junction, a Windows directory symlink.
Here is what I found:
So imagine the path of the MC executable is in 'C:\usr\share\multicommander-12.8'. So I create a junction in the same parent directory and name it 'C:\usr\share\MC-J'.
Now imagine I execute MultiCommander.exe using the command line 'C:\usr\share\MC-J\MultiCommander.exe'...execute it through the junction.
From that point on, choosing the '..' entry in the directory 'C:\usr' in MC, using the mouse or keyboard, takes me to 'C:\usr\share\MC-J' instead of 'C:\' as it should.
This does not occur if I run MC through it's original path, such as 'C:\usr\share\multicommander-12.8\MultiCommander.exe'. It likewise does not occur if I use a symbolic link instead of a junction, nor does it happen using Windows shortcut files (which are, of course, NOT symlink-like at all). Only through a junction.
I'll leave it up to you to decide if it's worth spending your time on this. I can live with a symlink as my path shortener here. It should be noted however that with the now "sanctioned" use of NTFS symbolic links it could crop up more often. It originally happened to me because the '\usr' directory was on a different partition, forcing the use of a junction to achieve what I wanted with that storage layout. Not quite an edge case, that.
Thanks again for the great program.
I had a chance to do a little more testing and the problem appears when MC is executed through a junction, a Windows directory symlink.
Here is what I found:
So imagine the path of the MC executable is in 'C:\usr\share\multicommander-12.8'. So I create a junction in the same parent directory and name it 'C:\usr\share\MC-J'.
Now imagine I execute MultiCommander.exe using the command line 'C:\usr\share\MC-J\MultiCommander.exe'...execute it through the junction.
From that point on, choosing the '..' entry in the directory 'C:\usr' in MC, using the mouse or keyboard, takes me to 'C:\usr\share\MC-J' instead of 'C:\' as it should.
This does not occur if I run MC through it's original path, such as 'C:\usr\share\multicommander-12.8\MultiCommander.exe'. It likewise does not occur if I use a symbolic link instead of a junction, nor does it happen using Windows shortcut files (which are, of course, NOT symlink-like at all). Only through a junction.
I'll leave it up to you to decide if it's worth spending your time on this. I can live with a symlink as my path shortener here. It should be noted however that with the now "sanctioned" use of NTFS symbolic links it could crop up more often. It originally happened to me because the '\usr' directory was on a different partition, forcing the use of a junction to achieve what I wanted with that storage layout. Not quite an edge case, that.
Thanks again for the great program.