In some cases, yes, it would be the same number of keystrokes (Ctrl+O
vs. Ctrl+L
or whatever a "normal" URL bar shortcut).
But I think my frustration lies in the fact that I can *see* the directory path but not interact with it. It's right there, but I can't edit it. So for example if I want to modify part of it (replacing one dir name with another somewhere in the path, for example) I can't just double-click the dir name like I can in (e.g.) Firefox's URL bar to change part of the URL.
I also think there's something (ergonomically/psychologically?) easier about being able to "edit in place", without having to open a separate dialog which takes you away from the main working area of the interface. It feels like better UX to follow the standard address bar paradigm IMO.
I guess I just feel like a read-only path is a bit of a weird/non-standard limitation and I don't really understand why it's implemented differently in the Explorer vs. Commander interfaces.
BTW if it helps you understand where I'm coming from, I do a lot of repetitive tasks on multiple servers using WinSCP. So basically changing directories, copy/pasting stuff etc. over
10 identical servers at a time. So points of friction like this become really noticeable.