When comparing KiTTY vs LilyTerm, the Slant community recommends KiTTY for most people. In the question“What are the best Linux terminal emulators?” KiTTY is ranked 14th while LilyTerm is ranked 22nd. 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 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 Can store login credentials
Uses Unicode for the best character compatibility.
Pro Support for tabbing
You can also color and reorder tabs, as well as manipulate tabs through keybindings.
Pro Transparency support improves usability
LilyTerm has true transparency support, making for better GUI usability.
Pro Change encoding on-the-fly
LilyTerm can change encoding on-the-fly. UTF-8 is the default encoding.
LilyTerm is a terminal emulator that aims to be as lightweight as possible. It requires minimal system resources and has very few dependencies.
Pro Fullscreen support
LilyTerm has fullscreen support which improves visibility.
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 Annoying behaviors
The default configuration may have some annoying behaviors (that can be removed by changing the default config). Such include asking for confirmation when reusing an existing window or when starting the terminal to launch a specific command.