Re: Command line session - load with different Tab name
This request has been added to the tracker:
https://winscp.net/tracker/1373
https://winscp.net/tracker/1373
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- dazed19
Re: Command line session - load with different Tab name
Hi
Thanks for coming back on this - just wondered if I'd missed something.
If/when you get to consider this further, an alternative might be to (optionally?) display the actual retrieved hostname in the tab. When I use Putty in a similar (tunnelled) fashion the window name changes to "username@actualhostname".
Thanks for coming back on this - just wondered if I'd missed something.
If/when you get to consider this further, an alternative might be to (optionally?) display the actual retrieved hostname in the tab. When I use Putty in a similar (tunnelled) fashion the window name changes to "username@actualhostname".
- martin
Re: Command line session - load with different Tab name
No you cannot control session name from command-line.
Will consider adding such an option.
Will consider adding such an option.
- dazed19
Command line session - load with different Tab name
Hi
Is there a way to control the session tab name when launching winscp from the command line?
My use case is that I am using SSH Local port forwarding to a number of target hosts.
When I load via "winscp.exe scp://[email protected]:20010" all the tabs show "[email protected]" and don't show the port and therefore a user can't (easily) distinguished between.
I have worked round this by creating sessions for each of my target hosts in winscp e.g. "VM20010", "VM20011" to match the ports used, but I would prefer to interact with winscp dynamically and avoid advance setup.
Thanks
Is there a way to control the session tab name when launching winscp from the command line?
My use case is that I am using SSH Local port forwarding to a number of target hosts.
When I load via "winscp.exe scp://[email protected]:20010" all the tabs show "[email protected]" and don't show the port and therefore a user can't (easily) distinguished between.
I have worked round this by creating sessions for each of my target hosts in winscp e.g. "VM20010", "VM20011" to match the ports used, but I would prefer to interact with winscp dynamically and avoid advance setup.
Thanks