Total Commander

Hi,

I hope this suggestion will be accepted by the developer:

- Add command line support to pass parameters to plugins. Mainly, the target is parse the PATH as a URL/URI, to not open the DIRECTOTY but the PLUGIN with the URL/URI as a parameter.

Example of the idea:

• $ TOTALCMD c:\windows (this works now)
  
  $ TOTALCMD sftp://user@server:/path (this opens the SFTP plugin with the specified URL)
  
  $ TOTALCMD webdav://user@server:/path (this opens the WebDAV plugin with the specified URL)
  
  etc.

I feel is a simple concept! Also, easy to implement if you add the option to parse a URL at the launch of the plugin, and if you can identify the plugin with the protocol or scheme name of the URL/URI.

Please, Ghisler, you agree?

Thank you!

I don't use sftp or webdav, but normally the path above the filesystem(plugin)panel can be used as parameter for TC.
e.g.: Regards
Holger

Yes, TC is able to pass path to FS plugin, but plugin must support such complex path.

Hi,

Thank you for your responses!

So, I check it and YES, TotalCMD can pass the directory to a Plug-in. I suggest to EXPLAIN this in the HELP, so at time isn't detailed anywhere.

Moreover, I don't find any info about HOW TO plugins receive/parse this parameter. My tests:

• * WebDAV plugin: You can access to saved sessions using "\\\WebDAV\_Session_Name_\" . But I don't have any info about how to pass a URL to "Quick connection".
  
  * SFTP pluging: You can only access to the plugin. If you call with the name of a session, you open the config window.

So, please, Ghisler, can you UPDATE the HELP do document this? Moreover, can you IMPROVE these plugins (perhaps others) to parse a URL/URI for quick connection?

My objective is call from a PuTTY session or other shell window to open the current session (using different protocols) inside the Total Commander. Using the way explained here this objective can be easy to achieve. Only a well documented plugin and minimal changes are required.

Thank you all for your time!

TC help says that you can pass path to open in panels. That is enough. If some plugin allows entering pseudo-path that will do some specific action, it is plugin help which should document it, not TC help. And you should ask plugin authors if plugin supports such quick connections.

MVV wrote:TC help says that you can pass path to open in panels. That is enough. If some plugin allows entering pseudo-path that will do some specific action, it is plugin help which should document it, not TC help. And you should ask plugin authors if plugin supports such quick connections.

Yes, I agree.
Nevertheless, the TC help don't say this: "If some plugin allows entering pseudo-path that will do some specific action" I suggest to add this to the help, and comment the correct sintax: "\\\_PLUGIN_NAME_"

Thank you!