When comparing KiTTY vs CLink, the Slant community recommends KiTTY for most people. In the question“What are the best terminal emulators for Windows?” KiTTY is ranked 6th while CLink is ranked 35th. The most important reason people chose KiTTY is:
- Sessions filter - Shortcuts for pre-defined command - The session launcher - Automatic logon script - URL hyperlinks - Running a locally saved script on a remote session - Send to tray - Transparency - Quick start of a duplicate session - SSH Handler: Internet Explorer integration - pscp.exe and WinSCP integration - New command-line options
Ranked in these QuestionsQuestion Ranking
Pro Includes additional features over PuTTy
- Sessions filter
- Shortcuts for pre-defined command
- The session launcher
- Automatic logon script
- URL hyperlinks
- Running a locally saved script on a remote session
- Send to tray
- Quick start of a duplicate session
- SSH Handler: Internet Explorer integration
- pscp.exe and WinSCP integration
- New command-line options
Pro Can store login credentials
Ability to store passwords/passphrases locally.
Pro Source Code Available
Source code is available so you could modify or review changes.
Pro Startup sessions
Support start-up sessions which allow you to specify the window/tab layout, working directories, and programs to run on startup.
Pro True Color support
Supports True Color, so software like Vim can display a really nice pallet.
Pro Background image
Ability to overlay the terminal background with an image.
Pro Auto login script
Automatic processing of commands after conncetion was made.
Uses Unicode for the best character compatibility.
Pro Transforms cmd.exe into something bearable
Cmd.exe is still irreplaceable for many tasks on Windows. This makes the experience less painful.
Pro Can easily search in history
The user can search in history by simply pressing Ctrl+R.
Con No centralized configuration
Each session holds its own configuration of all features. This means that if one wants to change a configuration common to all sessions (say, the terminal font), it has to be changed in each stored session separately.
A better solution would be to have a default configuration and store only the changed elements for each session (both configurations would be merged, with e priority on the specific one).
Con No tabbed sessions.
No built in support for tabbed sessions. Requires an add on.
Con Supports cmd.exe not the successor platform
It's for cmd.exe which was abandoned by Microsoft in the favor of PowerShell. Using PowerShell is more effective than cmd.exe even with CLink, unfortunatelly.