aboutsummaryrefslogtreecommitdiff
path: root/doc/foot.1.scd (follow)
Commit message (Collapse)AuthorAgeLines
* main/client: add --class, an alias for --app-idDaniel Eklöf2026-06-20-0/+3
| | | | | | | | | | | | | | | This is to help e.g. scripts that wants to launch terminal instances in a terminal agnostic way. Many terminals were originally for X11, where the '--class' choice was obvious. When they were ported to Wayland, it made sense for them to keep the '--class' command line option, but have it set the application ID instead (since "class" is not a thing on Wayland). Let's add the alias, but minimally documented. We don't want to _encourage_ its use after all. Closes #2368
* Spawning new terminal with --config from parent instanceStéphane Klein2026-03-02-0/+3
| | | | | Reference: https://codeberg.org/dnkl/foot/issues/1622 Signed-off-by: Stéphane Klein <contact@stephane-klein.info>
* config: add [colors-dark] and [colors-light], replacing [colors] and [colors2]Daniel Eklöf2025-12-20-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The main reason for having two color sections is to be able to switch between dark and light. Thus, it's better if the section names reflect this, rather than the more generic 'colors' and 'colors2' (which was the dark one and which was the light one, now again?) When the second color section was added, we kept the original name, colors, to make sure we didn't break existing configurations, and third-party themes. However, in the long run, it's probably better to be specific in the section naming, to avoid confusion. So, add 'colors-dark', and 'colors-light'. Keep 'colors' and 'colors2' as aliases for now, but mark them as deprecated. They WILL be removed in a future release. Also rename the option values for initial-color-theme, from 1/2, to dark/light. Keep the old ones for now, marked as deprecated. Update all bundled themes to use the new names. In the light-only themes (i.e. themes that define a single, light, theme), use colors-light, and set initial-color-theme=light. Possible improvements: disable color switching if only one color section has been explicitly configured (todo: figure out how to handle the default color theme values...)
* doc: remove duplicated ctrl+shift+w in foot(1)Whyme Lyu2025-12-01-3/+0
|
* config: add toplevel-tag=TAGDaniel Eklöf2025-11-12-0/+5
| | | | | | | | | | | Add support for the new xdg-toplevel-tag-v1 Wayland protocol, by exposing a new config option, `toplevel-tag`, and a corresponding command option, `--toplevel-tag` (in both `foot` and `footclient`). This can help the compositor with session management, or custom window rules. Closes #2212
* server/client: add support for sending SIGUSR to footclientDaniel Eklöf2025-08-01-3/+3
| | | | | | | | | | | This patch adds the IPC infrastructure necessary to propagate SIGUSR1/SIGUSR2 from a footclient process to the server process. By targeting a particular footclient instance, only that particular instance changes theme. This is different from when targeting the server process, where all instances change theme. Closes #2156
* doc: foot: document SIGUSR1/SIGUSR2Daniel Eklöf2025-07-30-0/+15
|
* config: add search-bindings.delete-to-{start,end} key bindingsAdrian fxj9a2025-03-05-0/+6
| | | | | | Defaults to ctrl+u and ctrl+k respectively. Closes #1972
* docs: document more default bindings in search scrollback mode.Mark Stosberg2024-10-25-1/+55
| | | | These were introduced by #1496 but not fully documented then.
* doc: foot: simplify example where we run a non-default commandDaniel Eklöf2024-04-20-1/+1
| | | | | To reduce the risk of people mistakenly believing you have to/should use "sh -c".
* Add support for opening an existing PTYAlyssa Ross2024-03-14-0/+7
| | | | | | | | | | | | | | | | | Virtual machine monitor programs (e.g. QEMU, Cloud Hypervisor) expose guest consoles as PTYs. With this patch, foot can access these guest consoles. Usually, the program used for accessing these PTYs is screen, but screen is barely developed, doesn't support resizing, and has a bunch of other unrelated stuff going on. It would be nice to have a terminal emulator that properly supported opening an existing PTY. The VMM controls the master end of the PTY, so to the other end (in this case foot), it just behaves like any application running in a directly-opened PTY, and all that's needed is to change foot's code to support opening an existing PTY rather than creating one. Co-authored-by: tanto <tanto@ccc.ac>
* config: map Control+wheel to font increase/decreaseDaniel Eklöf2024-02-15-3/+14
| | | | | | This is in addition to the already existing keyboard shortcuts. Also add missing default keyboard/mouse bindings to readme + foot(1).
* Don't use fancy Unicode quotes, stick to ASCIIDaniel Eklöf2024-02-06-11/+11
|
* readme, doc/foot.1: document shell-integration:command-output trackingDaniel Eklöf2024-02-06-0/+32
|
* slave: don't skip setting environment variables when using a custom environmentDaniel Eklöf2024-01-11-3/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When launching footclient with -E,--client-environment the environment variables that should be set by foot, wasn't. Those variables are: * TERM * COLORTERM * PWD * SHELL and all variables defined by the user in the [environment] section in foot.ini. In the same way, we did not *unset* TERM_PROGRAM and TERM_PROGRAM_VERSION. This patch fixes it by "cloning" the custom environment, making it mutable, and then adding/removing the variables above from it. Instead of calling setenv()/unsetenv() directly, we add the wrapper functions add_to_env() and del_from_env(). When *not* using a custom environment, they simply call setenv()/unsetenv(). When we *are* using a custom environment, add_to_env() first loops all existing variables, looking for a match. If a match is found, it's updated with the new value. If it's not found, a new entry is added. del_from_env() loops all entries, and removes it when a match is found. If no match is found, nothing is done. The mutable environment is allocated on the heap, but never free:d. We don't need to free it, since it's only allocated after forking, in the child process. Closes #1568
* Update documentation regarding systemd unitsMax Gautier2023-07-21-6/+6
|
* doc: foot: add default key binding for unicode inputDaniel Eklöf2023-07-10-0/+3
|
* doc: foot: update default key binding for URL modeDaniel Eklöf2023-07-10-1/+1
|
* bind control-shift-u to unicode-input, move urls to oAntoine Beaupré2023-07-10-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Having a keybinding to invoke arbitrary unicode characters is very useful. It's often used as a method of last resort to communicate with people outside of your main language. For example, if you want to type the last letter of my real name, you can invoke the latin-1 character 0xe9 or unicode 0x00e9. You can also use this to type special characters, for example, unicode U+1F4A9 is of course, the infamous PILE OF POO, which is sure to produce million laughs everywhere you go. In foot, there's no keybinding by default to invoke the very useful unicode-input command. There is no "standard" (as in "ISO") keybinding this either. But there *is* a de-facto standard currently deployed by *both* GTK and Qt (a rare feat) *and* Chrome OS (an even rarer feat) and it's control-shift-u. Alternatives include Control-x 8 (emacs), Control V u (vim), Alt (Windows, LibreOffice), or Option (Mac). I doubt we want to adopt any of those. So let's use control-shift-u for this. Unfortunately, it's currently assigned to show-urls-launch, which is unfortunate, but insurmountable. We can reassign this keybinding elsewhere. I have picked control-shift-o in my configuration, because "o" is a good mnemonic for "open URLs". Others have suggested "m" instead. Closes: #1183
* input: add basic support for touchscreen inputCismonX2023-07-05-0/+12
| | | | Closes #517
* .desktop: remove StartupWMClass from server, use distinct StartupWMClass for foot and footclientjdevdevdev2023-05-22-1/+1
| | | | | | | | | | | | | | | For this to work, the default app-id of footclient has been changed from ‘foot’ to ‘footclient’. By using distinct StartupWMClasses, the compositor can connect a running foot/footclient instance to the correct .desktop-file. This ensures the correct icon is being used in e.g. docks, and that actions like “open another window” works correctly. Note that the user can override the app-id, either by setting app-id in foot.ini, or with the -a,--app-id command line option. Closes #1355
* slave: unset TERM_PROGRAM{,_VERSION}Daniel Eklöf2023-05-18-11/+0
| | | | | | | | | | | | | | | | | | | | | Foot’s policy is to not set environment variables that identifies it (except the well-known and established `TERM` variable). We encourage applications to use terminfo to determine capabilities, or terminal queries, when available. Or, at least use terminal queries to detect the terminal and its version. Setting environment variables is a bad idea since they are inherited by all applications started by the terminal (which is the whole point). But, this includes other terminal emulators, making it very possible a terminal emulator gets mis-detected just because it was started from another terminal. Since there are a couple of terminal emulators that _do_ set TERM_PROGRAM and TERM_PROGRAM_VERSION, unset these environment variables to avoid being misdetected. Closes #1349
* slave: set $TERM_PROGRAM and $TERM_PROGRAM_VERSION environment variablesCraig Barnes2023-03-20-0/+11
| | | | | | | | | | | | | These are already being set by iTerm2, WezTerm, tmux and likely some others. Even though using yet more environment variables seems rather questionable, if we don't set these we run the risk of inheriting them from other terminals. See also: * https://gitlab.com/gnachman/iterm2/-/blob/97a6078df8e822da165e91737a01c0b9e115dd16/sources/PTYSession.m#L2568-2570 * https://github.com/tmux/tmux/blob/1d0f68dee9f71c504e03616fa472a408a6caa49b/environ.c#L263-L264 * https://github.com/search?q=TERM_PROGRAM&type=code
* doc: foot: add PWD to list of env vars set in child processDaniel Eklöf2022-12-04-0/+3
|
* readme/foot.1: mention that we now need “-d info” to get log outputDaniel Eklöf2022-11-23-1/+1
|
* change default log level to WARNINGAntoine Beaupré2022-11-22-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The default foot output looks like this, in Debian testing "bookworm" at the time of writing: anarcat@angela:pubpaste$ foot true info: main.c:421: version: 1.13.1 +pgo +ime +graphemes -assertions info: main.c:428: arch: Linux x86_64/64-bit info: main.c:440: locale: fr_CA.UTF-8 info: config.c:3003: loading configuration from /home/anarcat/.config/foot/foot.ini info: fcft.c:338: fcft: 3.1.5 +graphemes -runs +svg(nanosvg) -assertions info: fcft.c:377: fontconfig: 2.13.1, freetype: 2.12.1, harfbuzz: 5.2.0 info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Regular.otf: size=8.00pt/8px, dpi=75.00 info: wayland.c:1353: eDP-1: 2256x1504+0x0@60Hz 0x095F 13.32" scale=2 PPI=205x214 (physical) PPI=136x143 (logical), DPI=271.31 info: wayland.c:1509: requesting SSD decorations info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Bold.otf: size=24.00pt/32px, dpi=96.00 info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Regular.otf: size=24.00pt/32px, dpi=96.00 info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Bold.otf: size=24.00pt/32px, dpi=96.00 info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Regular.otf: size=24.00pt/32px, dpi=96.00 info: terminal.c:700: cell width=19, height=39 info: terminal.c:588: using 16 rendering threads info: wayland.c:859: using SSD decorations info: main.c:680: goodbye anarcat@angela:pubpaste$ That's 17 lines of output that are *mostly* useless for most use cases. I might understand having this output during the project's startup, when it's helpful for diagnostics, but now Foot just mostly works everywhere, and I've never had a use for any of that stuff in the (arguably short) time I've been using Foot so far. And if I do, there's the `--log-level` commandline option to tweak this. At first, I looked at tweaking the log level through the config file. But as explained in this issue: https://codeberg.org/dnkl/foot/issues/1142 ... there's a chicken and egg problem there that makes it hard to implement and possibly confusing for users as well. There's also the possibility for users to change the shortcut with which they start foot, for example a `.desktop` file so that menu systems that support those start foot properly. But that only works in that environment, and not through the so many things that will just call `foot` and hope it will do the right thing. In my case, I have `foot` hardcoded in a lot of places now, between sway and waybar, and this is only going to grow. Others have suggested adding the flag to a $TERMINAL global variable, but that won't help .desktop users. So, instead of playing whack-a-mole with the log levels, just make it so that, by default, foot is silent. This is actually one of the [basics of UNIX philosophy][1]: > Rule of Silence: When a program has nothing surprising to say, it > should say nothing. And yes, I am aware I am severely violating that principle by writing a way too long commit log for a one-line patch, but there you go, I figured it was good to document the why of this properly. [1]: https://web.archive.org/web/20031102053334/http://www.faqs.org/docs/artu/ch01s06.html
* osc: add support for OSC 133;A (prompt markers)Daniel Eklöf2022-06-16-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the OSC-133;A sequence, introduced by FinalTerm and implemented by iTerm2, Kitty and more. See https://iterm2.com/documentation-one-page.html#documentation-escape-codes.html. The shell emits the OSC just before printing the prompt. This lets the terminal know where, in the scrollback, there are prompts. We implement this using a simple boolean in the row struct ("this row has a prompt"). The prompt marker must be reflowed along with the text on window resizes. In an ideal world, erasing, or overwriting the cell where the OSC was emitted, would remove the prompt mark. Since we don't store this information in the cell struct, we can't do that. The best we can do is reset it in erase_line(). This works well enough in the "normal" screen, when used with a "normal" shell. It doesn't really work in fullscreen apps, on the alt screen. But that doesn't matter since we don't support jumping between prompts on the alt screen anyway. To be able to jump between prompts, two new key bindings have been added: prompt-prev and prompt-next, bound to ctrl+shift+z and ctrl+shift+x respectively. prompt-prev will jump to the previous, not currently visible, prompt, by moving the viewport, ensuring the prompt is at the top of the screen. prompt-next jumps to the next prompt, visible or not. Again, by moving the viewport to ensure the prompt is at the top of the screen. If we're at the bottom of the scrollback, the viewport is instead moved as far down as possible. Closes #30
* doc: document the new ‘environment’ config sectionDaniel Eklöf2022-06-13-2/+5
|
* config: use $HOME instead of getpwuid() to retrieve users’s home dirDaniel Eklöf2022-05-25-1/+5
| | | | | When searching for foot.ini, use $HOME instead of getpwuid() to retrieve the user’s home directory.
* config: add ctrl+shift+v and XF86 paste to SEARCH_CLIPBOARD_PASTEDaniel Eklöf2022-04-26-1/+1
| | | | | | | | | | | | | We now bind ctrl+v, ctrl+shift+v, ctrl+y and XF86Paste to pasting from the clipboard into the scrollback search buffer. Why all these? Because we can, and because all are common shortcuts for pasting: * ctrl+v: “normal” apps use this by default * ctrl+shift+v: used in terminals (including foot) * ctrl+y: Emacs * XF86Paste: special keyboard key, for pasting
* doc + meson.build: update information about foot.ini, small cleanupMerlin Büge2022-04-22-18/+27
| | | | | | | | | | | | | | | | | | | - foot.ini.5: mention location of example config file - foot.1: replace outdated (or incomplete) information about the location of the config file with references to foot.ini.5 - foot.1 and foot.ini.5: conform to scdoc specification, thus surround each header with (at least) one blank line. additionally consistently use exactly one line before/after each header (was sometimes two before) - foot.1: some parts of the keybindings had their own section, move into KEYBOARD SHORTCUTS section - foot.1: move EXIT STATUS section to the end where it is commonly found - foot.1: copy information about config file handling from the beginning of foot.ini.5 into the CONFIGURATION section of foot.1 - INSTALL.md: foot.ini is no longer included in the documentation - meson.build: do not bundle foot.ini with documentation anymore, see also https://codeberg.org/dnkl/foot/pulls/1015 Closes #1002
* doc: fix some small typosMerlin Büge2022-04-06-5/+5
|
* Document socket activation featureMax Gautier2022-02-26-1/+14
| | | | - Particular mention to included systemd user units
* doc: foot.1: describe how to search for the previous search stringDaniel Eklöf2022-01-29-2/+4
|
* doc: foot.1: shortcuts: mention that there are more actions than listed hereDaniel Eklöf2022-01-29-4/+3
|
* doc: foot.1: add missing ‘*’Daniel Eklöf2022-01-27-1/+1
|
* doc: foot.1: use tab for indentationDaniel Eklöf2022-01-27-1/+1
|
* doc: foot.1: add URL mode bindings to the list of default keyboard shortcutsDaniel Eklöf2022-01-27-0/+9
|
* doc: foot.1: add “enter URL mode” shortcutDaniel Eklöf2022-01-27-0/+4
|
* doc: foot.1: add the new XF86{Copy,Paste} key bindingsDaniel Eklöf2022-01-27-2/+2
|
* doc: foot.1: XTGETTCAPDaniel Eklöf2022-01-14-0/+47
|
* doc: foot.1: reporting bugs: move “search existing issues”Daniel Eklöf2021-10-16-2/+4
|
* doc: foot.1: reporting bugs: re-order and tweakDaniel Eklöf2021-10-16-5/+8
| | | | | * Tell people to search existing bugs first (open + closed) * Re-order instructions: most important ones first
* main/client: add no-op "-e" command-line optionCraig Barnes2021-09-18-0/+10
|
* meson: terminfo install location now defaults to $datadir/terminfoDaniel Eklöf2021-08-30-30/+0
| | | | | | | | | | | | | | | | | | | | | | | | | The meson command line option -Dcustom-terminfo-install-location has been changed in the following ways: * If unset, $datadir/terminfo is used, and TERMINFO is *not* exported * If set, that value (relative to $prefix) is used, and TERMINFO *is* exported. * The special value ‘no’ is removed. -Ddefault-terminfo now also changes the terminfo names generated when -Dterminfo=enabled. Furthermore, the documentation for the TERMINFO environment variable has been removed from the foot.1 and footclient.1 man pages (but as mentioned above, foot *will* still set it if -Dcustom-terminfo-install-location has been used). INSTALL.md has been updated to now recommend using ncurses’ terminfo definitions, if available. But also to document the other alternatives; installing the terminfo definitions in a custom location, or installing them with a diferent name. It also describes the general problem, and the disadvantages of each alternative (but without going into too much depth).
* doc: how to pass TERMINFO through ‘doas’Daniel Eklöf2021-08-27-5/+12
| | | | See #692
* doc: foot{,,client}: document TERMINFODaniel Eklöf2021-08-27-0/+23
| | | | Closes #691
* terminfo: install to $datadir/foot/terminfo by default, append to TERMINFO_DIRSDaniel Eklöf2021-08-17-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As of 2021-07-31, ncurses ships its own version of foot’s terminfo. Since: * It doesn’t have the non-standard Sync,Tc,setrgbf,setrgbb capabilities. * It doesn’t set hs,fsl,dsl (statusbar). * We want to be able to update our termminfo without waiting for an ncurses release. * Foot should be installable and usable on Linux systems that doesn’t have the latest ncurses. we still want to ship our own version. We can however not install it to the default terminfo location (e.g. /usr/share/terminfo), since it will collide with the ncurses provided files. Our options are to either rename our terminfo to something else, or to keep the name, but install our terminfo files somewhere else. The first option would be the easy one. However, I think it makes sense to use the same name. For example, a user that SSH’s into a remote system that does *not* have our own version installed, but *does* have the ncurses one, will gracefully fall back to that one, which is better than manually having to set e.g. TERM=xterm-256color. Now, if we want to use the same name, we need to install it somewhere else. But where? And how do we ensure our version is preferred over the ncurses one? I opted to $datadir/foot/terminfo (e.g. /usr/share/foot/terminfo) by default. It makes it namespaced to foot (i.e. we’re not introducing a new “standard” terminfo location), thus guaranteeing it wont collide with ncurses. To enable applications to find it, we export TERMINFO_DIRS. This is a list of *additional* directories to search for terminfo files. If it’s already defined, we *append* to it. The nice thing with this is, if there’s no terminfo in that location (e.g. when you SSH into a remote), the default terminfo location is *also* searched. But only *after* having searched through TERMINFO_DIRS. In short: our version is preferred, but the ncurses one (or an older version of our terminfo package!) will be used if ours cannot be found. To enable packagers full control over the new behavior, the existing meson command line options have been modified, and a new option added: -Dterminfo=disabled|enabled|auto: *build* and *install* the terminfo files. -Dcustom-terminfo-install-location=<path>: *where* the terminfo files are expected to be found. This *needs* to be set *even* if -Dterminfo=disabled. For example, if the packaging script builds and packages the terminfo files separate from the regular foot build. The path is *relative to $prefix*, and defaults to $datadir/foot/terminfo. This is the value that will be appended to TERMINFO_DIRS. Note that you can set it to ‘no’, in which case foot will *not* set/modify TERMINFO_DIRS. Only do this if you don’t intend to package foot’s terminfo files at all (i.e. you plan on using the ncurses ones only). -Ddefault-terminfo=foot. Allows overriding the default TERM value. This should only be changed if the target platform doesn’t support terminfo files. Closes #671
* doc: fix typo in foot man pageBen Brown2021-07-08-1/+1
|
* log: add LOG_CLASS_NONE and use as initializer for log_levelCraig Barnes2021-06-26-1/+1
| | | | | | | | | | | | This means that logging will be completely disabled until log_init() has been called, which is useful to prevent log spam when running UNITTEST{} blocks in debug builds. Note that this doesn't change the default log level at runtime, which was already being set to LOG_CLASS_INFO in main.c and client.c. The new log level is also exposed to the command-line interface as `--log-level=none`, which allows disabling logging entirely.
* doc: foot.1: remove trailing space, add ‘=’ between option name and its valueDaniel Eklöf2021-06-23-2/+2
|
* Override options from command lineRyan Farley2021-06-12-0/+4
| | | | | | | | | Allow any configuration option to be overridden with -o/--override 'section.key=value' arguments, as suggested in #554 update completitions for override slight refactoring to ease footclient support
* doc: foot{,client}: updates from feedback from @craigbarnesDaniel Eklöf2021-06-02-4/+4
|
* doc: foot.1: -t,--term: add references to ENVIRONMENT and TERMINFO sectionsDaniel Eklöf2021-06-02-1/+2
|
* doc: foot.1: add TERMINFO sectionDaniel Eklöf2021-06-02-0/+33
|
* doc: add ENVIRONMENT section to foot(1) and footclient(1) man pagesCraig Barnes2021-05-30-0/+43
| | | | Closes #556
* config: bind ctrl+c to "cancel" in search/url mode by defaultCraig Barnes2021-05-25-1/+1
| | | | Closes #544
* readme/doc: update details for IRC channelCraig Barnes2021-05-19-1/+1
|
* doc: foot.1 footclient.1: document exit statusDaniel Eklöf2021-05-04-1/+8
|
* Merge branch 'working-dir-command-line-option'Daniel Eklöf2021-02-14-1/+5
|\ | | | | | | Closes #347
| * doc: foot.1: add -D,--working-directory=DIRDaniel Eklöf2021-02-12-0/+4
| |
| * doc: foot.1: add missing short option to --login-shellDaniel Eklöf2021-02-12-1/+1
| |
* | doc: foot.1: mention that the key sequence alphabet can be configuredDaniel Eklöf2021-02-13-2/+2
|/
* doc: foot.1: document -d,--log-levelDaniel Eklöf2021-02-09-0/+4
|
* doc: foot.1: document the new URL modeDaniel Eklöf2021-02-07-0/+25
|
* main: remove deprecated "--geometry" optionCraig Barnes2021-01-13-3/+0
| | | | Closes #287
* doc: foot.1: add IRC channelDaniel Eklöf2020-11-27-0/+4
|
* doc: foot.1: no need to say foot.ini twiceDaniel Eklöf2020-11-26-1/+1
|
* foot/footclient: add short options to all command line optionsDaniel Eklöf2020-11-23-5/+5
| | | | | | | | | | | e81388336750a20a2da98a57e9726c8ba1b481e3 added “missing” short command line options to footclient. Except they weren’t missing; they were intentionally missing short options and only supported long options. This commit makes the new/missing short options “official”, by adding documentation, zsh completions and including them in usage().
* readme/doc:foot.1: document the (new) keypad behaviorDaniel Eklöf2020-11-11-0/+17
|
* search: add {clipboard,primary}-paste key bindingsDaniel Eklöf2020-11-01-0/+6
| | | | | | | | | | These bindings copy from the clipboard or primary selection into the search buffer. Default bindings: * clipboard-paste: ctrl+v, ctrl+y * primary-paste: shift+insert
* readme/doc: add shift+insert to list of default key bindingsDaniel Eklöf2020-10-10-0/+3
|
* doc: foot.1: remove ‘--’ from example command lineDaniel Eklöf2020-10-08-1/+1
|
* Add -W,--window-size-chars, and foot.ini:initial-window-size-charsDaniel Eklöf2020-09-08-1/+7
| | | | | | | | | | | * Add -W,--window-size-chars command line option * Add initial-window-size-chars foot.ini option * Add -w,--window-size-pixels command line option * Add initial-window-size-pixels foot.ini option * Deprecate -g,--geometry command line option in favor of -w,--window-size-pixels * Deprecate geometry option in foot.ini in favor of initial-window-size-pixels
* doc: rename footrc.5 to foot.ini.5, and update referencesDaniel Eklöf2020-08-27-4/+5
|
* doc: foot.1: move DESCRIPTION up before OPTIONSDaniel Eklöf2020-08-13-10/+10
|
* doc: foot.1: don't talk about using '--' on the command lineDaniel Eklöf2020-08-12-3/+2
| | | | This used to be necessary, but isn't anymore.
* server/client: use $WAYLAND_DISPLAY instead of $XDG_SESSION_ID in default socket pathDaniel Eklöf2020-08-02-4/+4
| | | | | | | | | Foot is a Wayland client and cannot be run outside of a Wayland session. As such, it makes more sense to use $WAYLAND_SESSION instead of $XDG_SESSION_ID in the default socket path since this makes it clearer which Wayland session we belong to. Closes #55.
* doc: foot.1: fix default path in -s,--serverDaniel Eklöf2020-08-02-4/+13
| | | | | | | | | | | | | | | | | | | The documentation incorrectly stated that the default path is $XDG_RUNTIME_DIR/foot.sock. The correct default path is * $XDG_RUNTIME_DIR/foot-$XDG_SESSION_ID.sock * $XDG_RUNTIME_DIR/foot-no-session.sock * /tmp/foot.sock Depending on whether XDG_RUNTIME_DIR and XDG_SESSION_ID has been set or not. This also removes the '<>' from the default when XDG_SESSION_ID is not set. Closes #53.
* doc+readme: make it clear(er) that RMB can be hold-and-draggedDaniel Eklöf2020-07-31-1/+3
|
* main: add --check-config command line optionDaniel Eklöf2020-07-29-0/+4
|
* doc: rename foot.5 -> footrc.5Daniel Eklöf2020-07-27-3/+3
|
* Correct the location of footrc in manpageJonas 'cherti' Große Sundrup2020-07-25-1/+1
|
* Fix typosbirger2020-07-25-2/+2
|
* main/client: be POSIXLY_CORRECT when parsing command lineDaniel Eklöf2020-05-08-3/+3
| | | | | | | | | | | | | | | | | | | | This means command line parsing stops when it encounters the first nonoption argument. The result is that one no longer need to use '--' to ensure arguments are passed to the shell/command, instead of parsed by foot. That is, instead of foot -- sh -c true one can now do foot sh -c true Arguments to foot *must* go before the command: foot --fullscreen sh -c true
* doc: foot.1: list what a bug report should containDaniel Eklöf2020-04-04-0/+9
|
* doc: foot.1: add link to issue reportingDaniel Eklöf2020-04-04-0/+4
|
* doc: foot.1: right mouse button extends current selectionDaniel Eklöf2020-04-04-0/+3
|
* doc: foot/footclient: fix highlighting of TITLE argument to --titleDaniel Eklöf2020-04-01-1/+1
|
* conf: add 'title' conf option and --title command line optionDaniel Eklöf2020-04-01-0/+3
|
* conf: add app-id config option and --app-id command line optionDaniel Eklöf2020-04-01-1/+5
|
* foot: add --maximized and --fullscreen command line optionsDaniel Eklöf2020-03-26-0/+8
|
* doc: foot.1: document ctrl+shift+nDaniel Eklöf2020-03-17-0/+5
|
* doc: foot.1: mention default value for '--log-colorize'Daniel Eklöf2020-03-17-1/+2
|
* doc: foot.1: fix typo - this isn't yambarDaniel Eklöf2020-03-17-1/+1
|
* doc/foot.1: keyboard shortcuts: add pointer to foot(5)Daniel Eklöf2020-03-09-2/+4
|
* config: change default geometry from 800x600 -> 700x500Daniel Eklöf2020-02-29-1/+1
| | | | | | | | If the display resolution *is* 800x600, using this size is bad since there will typically be panels and other things on the screen too. Not that 800x600 is something we expect to see in real life, but may happen on virtual displays.
* main: geometry defaults to 800x600 pixelsDaniel Eklöf2020-02-25-1/+1
|
* keymap: align backspace escapes with XTermDaniel Eklöf2020-02-21-0/+11
| | | | | | | | | | | | | | | Backspace now emits DEL for all non-ctrl modifier combos, and BS for all ctrl modifier combos. The alt modifier prefixes DEL/BS with ESC. This also removes my own hack of mapping ctrl+backspace to alt+backspace. Describe backspace behavior in both the README and the man page. TODO: implement DECBKM to allow applications to toggle the backspace behavior.
* doc: add --login-shellDaniel Eklöf2020-02-20-0/+3
|