Differences
This shows you the differences between the selected revisions of the page.
| 2013-06-01 | 2013-07-18 | ||
| session setting => site setting (martin) | kitty + opening putty in the same directory (martin) | ||
| Line 29: | Line 29: | ||
| You can also set up WinSCP to //[[ui_pref_integration_app|Automatically open new sessions in PuTTY]]//. | You can also set up WinSCP to //[[ui_pref_integration_app|Automatically open new sessions in PuTTY]]//. | ||
| + | |||
| + | ==== [[putty_startup_directory]] Opening PuTTY in the Same Directory ==== | ||
| + | If you want PuTTY to open in the same directory as WinSCP, you need to replace its startup command using ''-m'' argument. The syntax of the startup command would differ with the remote environment, particularly with operating system and shell. | ||
| + | |||
| + | For example with Unix-like system and ''bash'' shell the command will be like (note the ''!/'' [[ui_pref_integration_app#client_path|pattern]] to pass current remote path): | ||
| + | |||
| + | <code> | ||
| + | cd "!/" ; /bin/bash -login | ||
| + | </code> | ||
| + | |||
| + | As PuTTY needs to have the startup command to be stored in a file, you need to make use of ''!`command`'' [[ui_pref_integration_app#client_path|pattern]] to store the above command into a temporary file. Also as use of ''-m'' switch implies a non-interactive terminal, you need to force an interactive terminal back using ''-t'' switch. | ||
| + | |||
| + | Complete PuTTY command line for this will be like (change the shell path according to your system and preferences): | ||
| + | |||
| + | <code> | ||
| + | %PROGRAMFILES%\PuTTY\putty.exe -t -m "%TEMP%\putty.txt" !`cmd.exe /c echo cd "!/" ; /bin/bash -login > "%TEMP%\putty.txt"` | ||
| + | </code> | ||
| ==== Download PuTTY ==== | ==== Download PuTTY ==== | ||
| For your convenience you can [[&download#putty|download PuTTY]] also from our download page. | For your convenience you can [[&download#putty|download PuTTY]] also from our download page. | ||
| + | |||
| + | ==== Using KiTTY Instead of PuTTY ==== | ||
| + | If you want to use KiTTY, instead of PuTTY, you need to configure path to KiTTY executable in [[ui_pref_integration_app|preferences]]. | ||
| + | |||
| + | When using KiTTY in registry (non-portable) mode, you also need to specify KiTTY registry key in preferences. | ||
| + | |||
| + | When using KiTTY in portable mode, you need to specify pattern ''!U@!@'' in terminal client path as an alternative way to pass hostname and username to KiTTY: | ||
| + | |||
| + | <code> | ||
| + | kitty.exe !U@!@ | ||
| + | </code> | ||
| + | |||
| + | To open KiTTY in the same directory as WinSCP, you can use either the same [[integration_app#putty_startup_directory|technique as with PuTTY]]; or use KiTTY's ''-cmd'' switch to avoid use of temporary file: | ||
| + | |||
| + | <code> | ||
| + | kitty.exe -cmd "cd ""!/""" !U@!@ | ||
| + | </code> | ||
| + | |||
| + | Opening PuTTY in the Same Directory | ||
| ===== External Editor ===== | ===== External Editor ===== | ||