aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
* meson: bump version to 1.10.11.10.1Daniel Eklöf2021-11-22-1/+1
|
* changelog: prepare for 1.10.1Daniel Eklöf2021-11-22-6/+7
|
* Merge branch 'master' into releases/1.10Daniel Eklöf2021-11-22-240/+421
|\
| * Merge branch 'osc8-overwrite-2'Daniel Eklöf2021-11-22-101/+190
| |\ | | | | | | | | | | | | Closes #801 Closes #804
| | * term: print: reset ‘col’ after padding the right marginDaniel Eklöf2021-11-21-0/+1
| | |
| | * Revert "term: print: erase URI range when printing right-margin padding"Daniel Eklöf2021-11-21-3/+0
| | | | | | | | | | | | This reverts commit bb967fd2f927d90e881ed2b05db1fa6946033580.
| | * term: print: erase URI range when printing right-margin paddingDaniel Eklöf2021-11-21-0/+3
| | |
| | * term: print: re-order col/row/cell assigmentsDaniel Eklöf2021-11-21-10/+9
| | |
| | * changelog: osc-8 data not being cleared when cell is overwrittenDaniel Eklöf2021-11-21-0/+2
| | |
| | * grid: refactor grid_row_uri_range_erase()Daniel Eklöf2021-11-21-43/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The old algorithm always created a new URI, followed by (maybe) removing the existing URI, when an URI needed to be modified. That is, if e.g. the tail of an URI was being erased, the old algorithm would create a new URI for the part of the URI that should remain, and then removed the old URI. This isn’t very effective. The new algorithm instead identifies all possible overlap cases, and handles each one differently: * URI ends *before* erase range starts - continue with the next URI without further checks * URI starts *after* the erase range ends - return, we’re done * Erase range erases the entire URI - remove the URI * Erase range erases a part in the middle - split the URI * Erase range erases the head of the URI - adjust the URI’s start * Erase range erases the tail of the URI - adjust the URI’s end
| | * grid: row_uri_range_erase(): assume caller has checked row->extra != NULLDaniel Eklöf2021-11-21-2/+1
| | |
| | * term: erase_cell_range(): check if row->extra != NULLDaniel Eklöf2021-11-21-1/+2
| | |
| | * term: tail-call optimize calls to grid_row_uri_range_erase()Daniel Eklöf2021-11-21-2/+8
| | |
| | * term: call grid_row_uri_range_erase() when printing cellsDaniel Eklöf2021-11-21-19/+34
| | |
| | * grid: add grid_row_uri_range_erase()Daniel Eklöf2021-11-21-78/+155
| |/ | | | | | | | | | | | | | | | | This function handles erasing of an URI range. That is, a range of the row is being either erased, or overwritten (from the URI perspective, these two are the same thing). We handle both partial overwrites (split up, or truncate URI), as well as complete overwrites (remove URI).
| * changelog: pipe-* key bindings not being parsed correctlyDaniel Eklöf2021-11-21-0/+3
| |
| * config: argv_compare(): change parameters to ‘struct argv *’Daniel Eklöf2021-11-21-40/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | Instead of passing raw char** pointers to argv_compare(), pass pointers to ‘struct argv’. This lets argv_compare() handle both argv’s being NULL, or one of them being NULL. That is, the caller no longer needs to check that both argv’s are non-NULL before calling argv_compare(). Furthermore, update has_key_binding_collisions() to require the pipe argv to match, in addition to matching the ‘action’, when allowing a key collision.
| * config: pipe_argv_from_value(): plug memory leakDaniel Eklöf2021-11-21-22/+18
| | | | | | | | | | | | When parsing a key binding with a pipe-argv, we failed to free the argv vector (or to be precise, the strdup:ed entries in the array) when failing to parse the remainder of the binding.
| * Merge branch 'fix-809'Daniel Eklöf2021-11-21-6/+2
| |\ | | | | | | | | | Closes #809
| | * Fix parsing key-bindings config to not read past the end of the string.Arnavion2021-11-21-6/+2
| | | | | | | | | | | | | | | | | | | | | pipe_argv_from_value itself stripped the cmd-to-exec from ctx->value, so the callers should not be doing that themselves. Fixes #809
| * | Merge branch 'remove-unreachable'Craig Barnes2021-11-21-27/+4
| |\ \
| | * | config: Simplify render-timer option handlingXiretza2021-11-20-23/+4
| | | |
| | * | config: Remove some "UNREACHABLE" UB footgunsXiretza2021-11-20-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Every branch of these long if/else if/else chains returns, so the compiler can figure out on its own that the last line is never reached. If, for some reason, one of the branches does not return (as was the case after 205f1f7, fixed by b22322b), this would usually result in a compiler error ("control reaches end of non-void function"), but adding UNREACHABLE transforms this into silent undefined behaviour.
| * | | Merge branch 'theme-papercolor'Daniel Eklöf2021-11-21-0/+56
| |\ \ \
| | * | | Comment out `selection-*` for consistencySoc Virnyl Silab Estela2021-11-20-4/+4
| | | | | | | | | | | | | | | | | | | | - Changes in PaperColor Themes
| | * | | Add PaperColor theme variantsSoc Virnyl Silab Estela2021-11-17-0/+56
| | |/ / | | | | | | | | | | | | - color palettes taken from https://github.com/NLKNguyen/papercolor-theme
| * | / config: create a copy of the section nameDaniel Eklöf2021-11-21-2/+9
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The parsing context keeps a pointer to the current section name. This is used when logging errors. However, the pointer was into a buffer allocated by getline(). This buffer are often re-used in the next call to getline(), or free:d. Regardless, the section name pointer is invalid after the next call to getline(), which meant all error messages were logging a correct section name.
| * | Merge branch 'cell-color-source'Daniel Eklöf2021-11-20-26/+34
| |\ \
| | * | term: track cell color sourceDaniel Eklöf2021-11-20-26/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Each cell now tracks it’s current color source: * default fg/bg * base16 fg/bg (maps to *both* the regular and bright colors) * base256 fg/bg * RGB Note that we don’t have enough bits to separate the regular from the bright colors. These _shouldn’t_ be the same, so we ought to be fine...
| * | | config: use stack allocation for temporary buffer in value_to_enum()Craig Barnes2021-11-20-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | The maximum size required for the string buffer is relatively small, known at compile-time and not likely to ever grow beyond 512 bytes. Therefore we may as well just use the stack.
| * | | config: fix memory leak in value_to_enum()Craig Barnes2021-11-20-0/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | This could be triggered by running, for example: foot -o tweak.render-timer=invalid For some reason LeakSanitizer was only detecting this leak when the option value was invalid, even though it was occuring in either case.
| * | ci: one more text-shaping -> grapheme-shaping+run-shapingDaniel Eklöf2021-11-20-1/+1
| | |
| * | ci: fcft: replace text-shaping with grapheme-shaping+run-shapingDaniel Eklöf2021-11-20-13/+13
| |/
| * Merge branch 'letter-spacing-regression'Daniel Eklöf2021-11-15-1/+6
| |\
| | * config: letter-spacing: add missing ‘return’Daniel Eklöf2021-11-15-1/+6
| |/ | | | | | | | | | | | | | | | | The missing return caused us to fall through to the bottom of the function, where we ended with an error message: [main].letter-spacing: 0: not a valid option: letter-spacing Closes #795
| * Merge branch 'footclient-xdg-desktop'Daniel Eklöf2021-11-15-2/+14
| |\
| | * footclient.desktop: new XDG desktop file, for footclientDaniel Eklöf2021-11-15-2/+14
| |/
| * meson: add -Dthemes=false|trueDaniel Eklöf2021-11-14-1/+14
| | | | | | | | | | | | | | This adds a new meson option that controls whether the example theme files should be installed or not. The default is true. Previously, themes were gated by the -Ddocs option.
| * changelog: add new ‘unreleased’ sectionDaniel Eklöf2021-11-14-0/+11
| |
| * Merge branch 'releases/1.10'Daniel Eklöf2021-11-14-5/+12
| |\ | |/ |/|
* | meson: bump version to 1.10.01.10.0Daniel Eklöf2021-11-14-1/+1
| |
* | changelog: prepare for 1.10.0Daniel Eklöf2021-11-14-4/+11
|/
* Merge branch 'user-notification-cleanup'Daniel Eklöf2021-11-14-44/+25
|\
| * user-notification: config: various small cleanupsCraig Barnes2021-11-14-44/+25
|/ | | | | | | * Rename user_notification_add() to user_notification_add_fmt() * Add new user_notification_add() helper function * Use xvasprintf() to replace user_notification_add_va() * Make better use of helper functions in config.c
* config: remove options that were deprecated in 1.8.xDaniel Eklöf2021-11-14-82/+3
| | | | | | | * [main].bell * [main].jump-label-letters * [main].url-launch * [main].osc8-underline
* changelog: fix minor grammatical mistakeCraig Barnes2021-11-14-1/+1
|
* themes: solarized-dark: add commented out selection fg/bg colorsDaniel Eklöf2021-11-13-18/+23
|
* themes: add solarized-dark-normal-brightsDaniel Eklöf2021-11-13-0/+31
| | | | | | | | | | | This is a custom version of solarized-dark, where the bright colors have been generated by increasing the regular colors’ luminance by 20%. In other words, this version does *not* have the solarized colors that normally occupy the bright colors. Thus, if you want the full solarized experience in e.g. editors, make sure to use editor-specific 24-bit themes.
* Merge branch 'configurable-dim-colors'Daniel Eklöf2021-11-13-9/+91
|\ | | | | | | Closes #776
| * config: add [colors].dim0-7Daniel Eklöf2021-11-13-9/+91
|/ | | | | | | | | | | | | | | | | | | | | | | | | This allows you to configure custom colors to be used when colors are being dimmed (`\E[2m`). It is implemented by color matching (just like bold-text-in-bright=palette-based); the color-to-be-dimmed is matched against the current color palette. If it matches one of the regular colors (colors 0-7), the corresponding “dim” color will be used. If it matches one of the bright colors (colors 8-15), the corresponding “regular” color will be used (but *only* if the “dim” color has been set). Otherwise, the color is dimmed by reducing its luminance. The default behavior, i.e. when dim0-7 hasn’t been configured, is to dim by reducing luminance for *all* colors. I.e. we don’t do any color matching at all. In particular, this means that dimming a bright color will *not* result in the corresponding “regular” color. Closes #776
* doc: foot.ini: try to clear up the meaning of (AA)RRGGBBDaniel Eklöf2021-11-13-30/+39
|
* config: scrollback.indicator.text: use value_to_wchars()Daniel Eklöf2021-11-13-13/+2
|
* Merge branch 'modify-other-keys-mode-2'Daniel Eklöf2021-11-13-32/+90
|\
| * input: add support for modifyOtherKeys=2Daniel Eklöf2021-11-13-32/+90
|/ | | | | | | | | | | | | | | | Similar to modifyOtherKeys=1 (foot’s default, and only, mode), except that: * All modifiers (and not just Ctrl) generate \E[27;m;n~ escapes * Regular keys (with modifiers) also generate \E[27;m;n~ escapes (for example, C-h no longer generates ^H, but \E[27;5;104~) For our keymap based lookups, this is handled by adding MOD_MODIFY_OTHER_KEYS_STATE<N> variants. For “generic” keys, we simply adjust the conditions for when to emit a \E[27;m;n~ escape - the only requirement is that at least one modifier is active.
* Merge branch 'no-scrollback-multiplier-on-alt-screen'Daniel Eklöf2021-11-13-4/+13
|\ | | | | | | Closes #787
| * input: don’t apply [scrollback].multiplier when alt screen is in useDaniel Eklöf2021-11-13-4/+13
|/ | | | Closes #787
* Merge branch 'config-refactor'Daniel Eklöf2021-11-13-803/+708
|\
| * changelog: boolean optionsDaniel Eklöf2021-11-13-0/+4
| |
| * config: value_to_wchars(): free the target variableDaniel Eklöf2021-11-13-34/+11
| |
| * config: appease compilerDaniel Eklöf2021-11-13-1/+1
| | | | | | | | | | | | | | | | ../../foot/config.c:154:50: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] log_msg(log_class, LOG_MODULE, file, lineno, formatted_msg); ^~~~~~~~~~~~~ ../../foot/config.c:154:50: note: treat the string as an argument to avoid this log_msg(log_class, LOG_MODULE, file, lineno, formatted_msg)
| * config: drop all warning logs from the tweak sectionDaniel Eklöf2021-11-13-53/+19
| |
| * config: value_to_enum(), return conversion success/failure as a boolDaniel Eklöf2021-11-13-79/+91
| | | | | | | | | | | | | | Result is set through a pointer passed as an argument. Note that we assume enums are 32-bit, and explicitly cast them to int*. Static asserts have been added to ensure this invariant holds.
| * config: parse_section_main(): explicit return from each branchDaniel Eklöf2021-11-13-25/+27
| | | | | | | | Add UNREACHABLE() at the bottom
| * config: add value_to_dimensions()Daniel Eklöf2021-11-13-14/+15
| |
| * config: add {str,value}_to_uint{16,32}()Daniel Eklöf2021-11-13-106/+92
| | | | | | | | | | This allows us to pass the final pointer directly to the conversion functions, as well as allowing us to print outside-range errors.
| * config: add value_to_str()Daniel Eklöf2021-11-13-18/+17
| | | | | | | | Takes a pointer to a char*, free:s it, and strdups the current value.
| * config: value_to_bool: return success/failDaniel Eklöf2021-11-13-26/+49
| | | | | | | | | | Write boolean value to a pointer passed as argument, return conversion success/failure
| * config: add value_to_enum()Daniel Eklöf2021-11-13-103/+107
| |
| * config: let value_to_double() log errorsDaniel Eklöf2021-11-13-13/+14
| |
| * config: let value_to_ulong() log errorsDaniel Eklöf2021-11-13-29/+16
| |
| * config: add LOG_CONTEXTUAL_{ERR,WARN,ERRNO}Daniel Eklöf2021-11-13-288/+163
| | | | | | | | | | | | These work like LOG_AND_NOTIFY_* but add contextual information: path of the conf file, line number, section name, key/option name and the value.
| * config: first argument to log_and_notify() is now a ‘struct context’Daniel Eklöf2021-11-13-139/+119
| |
| * config: rename str_to_spawn_template() -> value_to_spawn_template()Daniel Eklöf2021-11-13-20/+11
| |
| * config: rename str_to_fonts() -> value_to_fonts()Daniel Eklöf2021-11-13-10/+8
| |
| * config: rename str_to_wchars() -> value_to_wchars()Daniel Eklöf2021-11-13-19/+13
| |
| * config: rename str_to_double() -> value_to_double()Daniel Eklöf2021-11-13-28/+22
| | | | | | | | | | * str_to_double() -> value_to_double() * str_to_pt_or_px() -> value_to_pt_or_px()
| * config: rename str_to_ulong() -> value_to_ulong()Daniel Eklöf2021-11-13-47/+73
| | | | | | | | | | | | * str_to_ulong() -> value_to_ulong() * str_to_color() -> value_to_color() * str_to_two_colors() -> value_to_two_colors()
| * config: value_to_bool(): fixupDaniel Eklöf2021-11-13-1/+1
| |
| * config: rename str_to_bool() -> value_to_bool()Daniel Eklöf2021-11-13-19/+19
| | | | | | | | Change argument to a ‘struct context’ pointer
| * config: pass aggregated struct to top-level section handlersDaniel Eklöf2021-11-13-53/+138
|/
* main: improve handling of setlocale(3) return valueCraig Barnes2021-11-10-2/+6
| | | | | | | | | There's no need to call setlocale() twice, since the first call returns the same value as the second. We also handle a NULL return value explicitly and show a distinct error message for that case, since it typically indicates a misconfigured locale and not just a non-UTF8 locale.
* wayland: guard XDG startup notification with HAVE_XDG_ACTIVATIONDaniel Eklöf2021-11-09-0/+2
| | | | Fixes compilation on systems with “too old” wayland-protocols
* PKGBUILD: dropDaniel Eklöf2021-11-07-83/+11
| | | | | The bundled PKGBUILD has been pretty much identical to the one in the AUR package “foot-git” for a long time now.
* doc: foot.ini: mention “xkbcli interactive-wayland”Daniel Eklöf2021-11-07-0/+2
|
* Merge branch 'error-out-on-too-old-wl-seat-interface'Daniel Eklöf2021-11-07-0/+7
|\ | | | | | | Closes #779
| * wayland: error out if there aren’t any seats availableDaniel Eklöf2021-11-07-0/+7
|/ | | | | | | | | | | | If there aren’t any seats available, input is not possible (neither keyboard nor mouse input). Note that this is not the same thing as e.g. no keyboard being plugged in. In this case, there will be a seat, but without the keybaord capability. Input may not be possible _right now_, but may be later, if the user plugs in a keyboard. Closes #779
* Merge branch 'xdga-launch'Daniel Eklöf2021-11-03-11/+51
|\
| * foot/client: implement xdga client activationRonan Pigott2021-11-01-11/+51
|/ | | | | | | | | | | This is an application of the xdg activation protocol that will allow compositors to associate new foot toplevels with the command that launched them. footclient receives an activation token from the launcher which the compositor can use to track application startup. It passes the token to the foot server, which then activates the new window with the token to complete the startup sequence.
* config: format all (well, most) error messages in the same wayDaniel Eklöf2021-10-31-127/+120
| | | | path:lineno: [section].key: value: message desribing what’s wrong with value
* config: use "[section].key" syntax when logging errorsDaniel Eklöf2021-10-31-55/+55
|
* config: improve error messages for invalid section keysDaniel Eklöf2021-10-31-9/+18
|
* install: remove text describing obsolete differences between PKGBUILDsDaniel Eklöf2021-10-31-9/+3
|
* readme: add GitHub Sponsors linkDaniel Eklöf2021-10-31-0/+6
|
* Merge branch 'client-sendall'Daniel Eklöf2021-10-31-7/+28
|\
| * client: use MSG_NOSIGNAL in send(3)Daniel Eklöf2021-10-30-1/+1
| | | | | | | | | | | | | | MSG_NOSIGNAL Requests not to send the SIGPIPE signal if an attempt to send is made on a stream-oriented socket that is no longer connected. The [EPIPE] error shall still be returned.
| * client: handle partial writes in send(3)Daniel Eklöf2021-10-29-7/+28
|/
* Merge branch 'csd-border'Daniel Eklöf2021-10-29-8/+97
|\
| * render: csd_part: we don’t use the ‘src’ pixman imageDaniel Eklöf2021-10-29-3/+0
| |
| * foot.ini: csd.border-color: <color> -> <csd.color>Daniel Eklöf2021-10-29-1/+1
| |
| * csd: add support for a visible borderDaniel Eklöf2021-10-27-7/+99
|/ | | | | | | | | | | | | | | | | | | | | | | | When we’re using CSDs, we’ve up until now rendered a 5px invisible border. This border handles interactive resizing. I.e. hovering it changes the mouse cursor, and mouse button events are used to start an interactive resize. This patch makes it possible to color part of (or the entire) border, with a configurable color. To facilitate this, two new options have been added: * csd.border-width * csd.border-color border-width defaults to 0, resulting in the look we’re used to. border-color defaults to the title bar color. If the title bar color hasn’t been set, it defaults to the default foreground color (just like the title bar color does). This means that, setting border-width but not border-color, results in a border that blends with the title bar.