FS-plugins and commands in command line

[DrShark]

When Total Commander panel path is some of FS-plugin (like \\\Cloud\),
in command line TC can't execute commands like c:\, or cd <something>, or cm_<something> (I'll call them "general commands" in the following text), although they are supported in buttons or when panel with real filesystem path. I guess it's because WFX plugins can execute their own commands in command line.

This situation is quite annoying, so I have a question: can TC detect if certain WFX plugin supports its own commands, and can it detect that when user enters FS-plugin path? If yes, I have two suggestions:
1. When user goes to FS-plugin path, detect if plugin doesn't have it's own commands support and then enable Total Commander handling of general commands in command line.
2. Although TC doesn't execute general commands in command line inside FS-plugins, the command line still offers a command line's command history (called by Ctrl+Down in command line). When TC will detect whether plugin has its own commands support (see §1), I suggest to use plugin-specific commands history for each of such FS-plugins. For other FS-plugins, TC should offer general commands history, or maybe the history should be disabled there if suggestion from §1 will not be implemented.

Alternative/complementary suggestions are welcome here.

[Dalai]

I guess it's because WFX plugins can execute their own commands in command line.

Correct.

This situation is quite annoying

Indeed it is, especially when the current directory is some WFX plugin and you want to switch to a UNC path...

so I have a question: can TC detect if certain WFX plugin supports its own commands, and can it detect that when user enters FS-plugin path?

No, it can't. When FsExecuteFile is implemented/exported by the WFX plugin, TC sends all commands to the plugin.

Regards
Dalai