||2 years ago|
|completions||2 years ago|
|doc||2 years ago|
|scripts||2 years ago|
|subprojects||2 years ago|
|.gitignore||2 years ago|
|.gitlab-ci.yml||2 years ago|
|.gitmodules||2 years ago|
|LICENSE||2 years ago|
|PKGBUILD||2 years ago|
|README.md||2 years ago|
|async.c||2 years ago|
|async.h||2 years ago|
|base64.c||2 years ago|
|base64.h||2 years ago|
|client.c||2 years ago|
|commands.c||2 years ago|
|commands.h||2 years ago|
|config.c||2 years ago|
|config.h||2 years ago|
|csi.c||2 years ago|
|csi.h||2 years ago|
|fdm.c||2 years ago|
|fdm.h||2 years ago|
|foot.desktop||2 years ago|
|foot.info||2 years ago|
|footrc||2 years ago|
|generate-version.sh||2 years ago|
|grid.c||2 years ago|
|grid.h||2 years ago|
|input.c||2 years ago|
|input.h||2 years ago|
|keymap.h||2 years ago|
|log.c||2 years ago|
|log.h||2 years ago|
|main.c||2 years ago|
|meson.build||2 years ago|
|misc.c||2 years ago|
|misc.h||2 years ago|
|osc.c||2 years ago|
|osc.h||2 years ago|
|render.c||2 years ago|
|render.h||2 years ago|
|search.c||2 years ago|
|search.h||2 years ago|
|selection.c||2 years ago|
|selection.h||2 years ago|
|server.c||2 years ago|
|server.h||2 years ago|
|shm.c||2 years ago|
|shm.h||2 years ago|
|slave.c||2 years ago|
|slave.h||2 years ago|
|terminal.c||2 years ago|
|terminal.h||2 years ago|
|tokenize.c||2 years ago|
|tokenize.h||2 years ago|
|vt.c||2 years ago|
|vt.h||2 years ago|
|wayland.c||2 years ago|
|wayland.h||2 years ago|
foot is a fast Wayland terminal emulator.
- What does not work?
- Server mode
- Fast (TODO insert benchmark results here)
- Wayland native
- DE agnostic
- User configurable font fallback
- Scrollback search
- Color emoji support
- "Server" mode (one master process, many windows)
This is a non-exhaustive list of things some people might consider being important features (i.e. "must-haves"), that are unlikely to ever be supported by foot.
- Graphical elements (menu, buttons etc)
What does not work?
This is a list of known, but probably not all, issues:
Unicode combining characters
Examples: á, 👪🏼 (may not be displayed correctly in your browser/editor)
Reflow text on window resize
GNOME; might work, but without window decorations.
Strictly speaking, foot is at fault here; all Wayland applications must be able to draw their own window decorations (but foot is not).
However, most people want a uniform look and feel on their desktop, including the window decorations. For this reason, a Wayland application can request Server Side Decorations (SSD). GNOME will reply with a "I hear you, but sorry, I wont do that".
foot supports all fonts that can be loaded by freetype, including bitmap fonts and color emoji fonts.
Foot uses fontconfig to locate and configure the font(s) to use. Since fontconfig's fallback mechanism is imperfect, especially for monospace fonts (it doesn't prefer monospace fonts even though the requested font is one), foot allows you, the user, to configure the fallback fonts to use.
This also means you can configure each fallback font individually; you want that fallback font to use this size, and you want that other fallback font to be italic? No problem!
If a glyph cannot be found in any of the user configured fallback fonts, then fontconfig's list is used.
At the moment, all shortcuts are hard coded and cannot be changed. It is not possible to define new key bindings.
shift+page up/page down
Scroll up/down in history
Copy selected text to the clipboard
Paste from clipboard
Start a scrollback search
While doing a scrollback search, the following shortcuts are available:
Search backward for next match
Search forward for next match
Extend current selection (and thus the search criteria) to the end of the word, or the next word if currently at a word separating character.
Same as ctrl+w, except that the only word separating characters are whitespace characters.
Cancel the search
Finish the search and copy the current match to the primary selection
left - single-click
Drag to select; when released, the selected text is copied to the primary selection. Note that this feature is normally disabled whenever the client has enabled mouse tracking, but can be forced by holding shift.
left - double-click
Selects the word (separated by spaces, period, comma, parenthesis etc) under the pointer. Hold ctrl to select everything under the pointer up to, and until, the next space characters.
left - triple-click
Selects the entire row
Paste from primary selection
Scroll up/down in history
When run normally, foot is a single-window application; if you want another window, start another foot process.
However, foot can also be run in a server mode. In this mode, one process hosts multiple windows. Note that this is nothing like tabs. When first started in server mode, no windows are available.
You open new windows by running
footclient. This is a small process
that instructs the foot server to open a new terminal window. The
client process remains running until the terminal window is
closed. The exit value of the client process is that of the shell that
was running in the terminal window.
The point of this mode is a) reduced memory footprint - all terminal windows will share fonts and glyph cache, and b) reduced startup time - loading fonts and populating the glyph cache takes time, but in server mode it only happens once.
The downside is a performance penalty; all windows' input and output are multiplexed in the same thread (but each window will have its own set of rendering threads). This means that if one window is very busy with, for example, producing output, then other windows will suffer.
And of course, should the server process crash, all windows will be gone.
Typical usage would be to start the server process (
when starting your Wayland compositor (i.e. logging in to your
desktop), and then run
footclient instead of
foot whenever you
want to launch a new terminal.
- wayland (client and cursor libraries)
- tllist, unless built as a subproject
- fcft, unless built as a subproject
In addition to the dev variant of the packages above, you need:
- wayland protocols
Note that it will do a profiling-guided build, and that this requires a running wayland session since it needs to run an intermediate build of foot.
Foot uses meson. If you are unfamiliar with it, the official tutorial might be a good starting point.
I also recommend taking a look at the bundled Arch PKGBUILD file, to see how it builds foot.