Allow % variables in more places

[gregg]

Hello!

The variables available in some places like log file naming (%H=hostname, %S=session name, etc, etc) would be nice to have in other locations.

1. Local Shell; but first this needs to also allow passing command line parameters.

2. Logon Actions; expect (nice-to-have) and send (what i'm really interested in)

My reason: I'm trying to hack in mosh usage. With Win10 and WSL, you can set your local shell to bash.exe, and bash.exe supports "-c" which allows starting another app, aka:

C:\Windows\System32\bash.exe -c /usr/bin/mosh <hostname>

Ideally, <hostname> would be %H in this case. But putting any cli arguments in the Connection->Local Shell path causes SecureCRT to say "Local shell path is not a console application"

Ok, so abandoning that, I tried a Logon action.
Expect: <nothing/empty>
Send: /usr/bin/mosh %H

%H is sent as a literal and not the hostname.

Unfortunately, I do realize just adding %H support here directly is bad because it would break any existing logon actions that are already using % in this functionality and would require something like a checkbox (defaulted off) that said "variable expansion enable" - but that's an implementation detail to which I don't know the full ramifications of.

Also of note, I've been enjoying the latest 9.0.2 version. Thank you!

[berdmann]

Hi gregg,

I am happy to hear that you have been enjoying 9.0.2 thus far! I went ahead and captured 2 feature requests on your behalf. The first is to add the ability to pass command line arguments to a local shell session. The second is to add the ability to specify substitution variables in other configuration locations (such as logon actions).

We will be sure to post here if either of the aforementioned requests are implemented.

If you prefer direct email notification, send an email to support@vandyke.com and include "***Feature Request - Forum Thread #14547***" *in the subject line.