Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing xterm vs Guake, the Slant community recommends Guake for most people. In the question“What are the best terminal emulators for UNIX-like systems?” Guake is ranked 11th while xterm is ranked 13th. The most important reason people chose Guake is:
You can hit F12 (by default, though it's customizable) to open a terminal overlay, Quake-style, as a drop-down from the top of the screen.
Question Ranking
Pros
Pro Lightweight
Xterm is a very lightweight terminal. It requires few resources, allowing it to run well even on lower-end machines.
Pro Used in almost every Linux distribution
If you master xterm, you won't have to learn another tty, since it is in almost every Linux distribution.
Pro Stable, well-tested
Pro Standard with X Window system
Xterm is installed as standard software with the X Window system, and is there even when installing other terminal emulators.
Pro Supports sixel images
Pro Shows full characters for wide fallback fonts
Many terminal emulators that deal with wider fallback fonts (i.e. double-wide characters in CJK fonts) truncate display of wide characters, show Unicode "missing glyph" characters, or simply fail to display the characters at all. XTerm is "smart" enough to simply take up the extra space needed to show such wide characters.
Pro In about 30 years, it had only one issue, and that was fixed quickly
Pro It is fast and responsive
See this.
Pro Many modern terminals emulate xterm
Many terminal applications, such as OS X's Terminal.app and iTerm2 (among others), all claim xterm or xterm- variants as their $TERM and aim for support of xterm's escape sequences. Many command-line applications will assume or even hard-code escape-sequences and behavior for xterm and those terminals emulating it.
Pro Configurable via Xresources
X Toolkit resources and xrdb predates what is currently called "theme". Although one needs to read man, mitigates most listed cons
Pro Drop-down terminal
You can hit F12 (by default, though it's customizable) to open a terminal overlay, Quake-style, as a drop-down from the top of the screen.
Pro Supports transparency
Transparency is particularly useful for when you need to refer to the information displayed by application under Guake window.
Pro Hotkey support
Guake is very fast and easy to open with a customizable hotkey, meaning there's no fiddling with menus or icons.
Pro Extremely customizable
Guake's appearance is very customizable: from the transparency to the width and height of the window. You can also choose which key to use for toggling the terminal window.
Pro Available in many popular distro repositories
Guake is available in a lot of repositories for the most popular distros. This makes it very easy to obtain and install on almost any system.
Pro Shortcut key F12 can be used to toggle
The global shortcut key, F12, can be used to easily toggle the terminal window.
Pro Tabs support
Guake supports tabs, while working with them is very easy.
Pro Can choose byobu as shell
You can choose byobu as shell, by adding a line to /etc/shells : " /usr/bin/byobu"
and get guake with byobu ... sweet!
Cons
Con No native transparency
Xterm does not natively support transparency (though it can be emulated if needs be).
Con Bad defaults
Very small default size. No way to know to how to configure size.
Con No tabs
Con It blinks
If it blinks for you too, you can try this: man xterm and then press Shift+G.
Con Has few dependencies
Has dependencies like xbitmaps.
Con Historical source code
The stories behind terminal emulation beyond their classical representatives (of which xterm is simply the most long-lived) are somewhere inbetween subtly irritating to downright surreal.
Con Not cross-platform
Linux only, and additionally targeting GTK3.
Con Not very responsive
Occasionally, Guake slows down and is not very responsive.
Con No font ligature
Guake uses vte for its terminal emulation, and vte simply doesn't support font ligature (yes, it's 2019). This is what its maintainer thinks about it.
He really thinks supporting font ligature breaks terminal's grid, like he doesn't understand a font that's monospace is a monospace no matter if it has ligature or not.
