aboutsummaryrefslogtreecommitdiff
path: root/config.c (follow)
Commit message (Collapse)AuthorAgeLines
* key-binding: new API, for handling sets of key bindingsDaniel Eklöf2022-04-17-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Up until now, our Wayland seats have been tracking key bindings. This makes sense, since the seat’s keymap determines how the key bindings are resolved. However, tying bindings to the seat/keymap alone isn’t enough, since we also depend on the current configuration (i.e. user settings) when resolving a key binding. This means configurations that doesn’t match the wayland object’s configuration, currently don’t resolve key bindings correctly. This applies to footclients where the user has overridden key bindings on the command line (e.g. --override key-bindings.foo=bar). Thus, to correctly resolve key bindings, each set of key bindings must be tied *both* to a seat/keymap, *and* a configuration. This patch introduces a key-binding manager, with an API to add/remove/lookup, and load/unload keymaps from sets of key bindings. In the API, sets are tied to a seat and terminal instance, since this makes the most sense (we need to instantiate, or incref a set whenever a new terminal instance is created). Internally, the set is tied to a seat and the terminal’s configuration. Sets are *added* when a new seat is added, and when a new terminal instance is created. Since there can only be one instance of each seat, sets are always removed when a seat is removed. Terminals on the other hand can re-use the same configuration (and typically do). Thus, sets ref-count the configuration. In other words, when instantiating a new terminal, we may not have to instantiate a new set of key bindings, but can often be incref:ed instead. Whenever the keymap changes on a seat, all key bindings sets associated with that seat reloads (re-resolves) their key bindings. Closes #931
* url-mode: add a key binding that enables “persistent” URL modeDaniel Eklöf2022-04-17-1/+2
| | | | | | | This is an alternative to ‘show-urls-launch’, where we stay in URL mode after activating an URL. Closes #964
* config: add [csd].hide-when-maximized=yes|noDaniel Eklöf2022-04-16-0/+4
| | | | | | | When enabled, the CSD titlebar will be hidden when the window is maximized. Closes #1019
* fix some small typosMerlin Büge2022-04-13-5/+5
|
* config: config_free(): pass conf struct by pointer, not by-valueDaniel Eklöf2022-04-12-26/+26
|
* config: simplify lookup of foot.iniDaniel Eklöf2022-04-12-144/+31
| | | | | | | | The old, complex, way of using a dynamic list to hold each path component made _some_ sense before, when we needed to support both ~/.config/foot.ini and ~/.config/foot/foot.ini. But now, it just over complicates things.
* config: use fallback when XDG_CONFIG_{HOME,DIRS} is set, but emptyDaniel Eklöf2022-04-07-2/+2
|
* config: fallback to /etc/xdg if XDG_CONFIG_DIRS is unsetDaniel Eklöf2022-04-07-2/+4
| | | | Closes #1008
* config: add tweak option to allow disabling sixelsjvoisin2022-04-06-0/+4
| | | | Closes #950
* config/input: add scrollback-home|end key bindings (unbound by default)Daniel Eklöf2022-02-23-0/+2
|
* config: do key binding collision handling in overridesDaniel Eklöf2022-02-16-18/+17
| | | | | This ensures we detect, and handle, collisions also for key-bindings specified as overrides.
* wip: map key combos to custom text strings (including escapes)Daniel Eklöf2022-02-16-3/+112
| | | | | | | | | | | | | With this, it is now possible to map key combos to custom escapes. The new bindings are defined in a new section, “text-bindings”, on the form “string=key combo”. The string can consist of printable characters, or \xNN style hex digits: [text-bindings] abcd = Control+a \x1b[A = Control+b Control+c Control+d # map ctrl+b/c/d to UP
* config: rename csd.color.close -> quitDaniel Eklöf2022-02-09-1/+1
| | | | | | | | | | | This fixes a compilation error on FreeBSD: ../../foot/render.c:2055:45: error: no member named 'epoll_shim_close' in 'struct config::(anonymous at ../../foot/config.h:254:9)' conf_color = &term->conf->csd.color.close; ~~~~~~~~~~~~~~~~~~~~~ ^ /usr/local/include/libepoll-shim/epoll-shim/detail/common.h:8:15: note: expanded from macro 'close': #define close epoll_shim_close
* config: ‘pipe’ is now optional ‘aux’ data in the key-binding structDaniel Eklöf2022-02-09-52/+74
| | | | | This allows us to add helper functions that e.g. compare bindings’ aux data in a generic way.
* config: rename enum config_key_binding_type -> key_binding_typeDaniel Eklöf2022-02-09-2/+2
|
* config: font->name may be NULLDaniel Eklöf2022-02-06-2/+6
| | | | | If it is, fallback to the font pattern instead, like we used to do before fcft-3.
* fcft: adapt to API changes in fcft-3.xDaniel Eklöf2022-02-05-43/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fcft no longer uses wchar_t, but plain uint32_t to represent codepoints. Since we do a fair amount of string operations in foot, it still makes sense to use something that actually _is_ a string (or character), rather than an array of uint32_t. For this reason, we switch out all wchar_t usage in foot to char32_t. We also verify, at compile-time, that char32_t used UTF-32 (which is what fcft expects). Unfortunately, there are no string functions for char32_t. To avoid having to re-implement all wcs*() functions, we add a small wrapper layer of c32*() functions. These wrapper functions take char32_t arguments, but then simply call the corresponding wcs*() function. For this to work, wcs*() must _also_ be UTF-32 compatible. We can check for the presence of the __STDC_ISO_10646__ macro. If set, wchar_t is at least 4 bytes and its internal representation is UTF-32. FreeBSD does *not* define this macro, because its internal wchar_t representation depends on the current locale. It _does_ use UTF-32 _if_ the current locale is UTF-8. Since foot enforces UTF-8, we simply need to check if __FreeBSD__ is defined. Other fcft API changes: * fcft_glyph_rasterize() -> fcft_codepoint_rasterize() * font.space_advance has been removed * ‘tags’ have been removed from fcft_grapheme_rasterize() * ‘fcft_log_init()’ removed * ‘fcft_init()’ and ‘fcft_fini()’ must be explicitly called
* config: s/of the form/on the form/Daniel Eklöf2022-02-05-1/+1
|
* config: use getline idiomaticallyPranjal Kole2022-02-05-66/+72
| | | | | | getline(3) contains an example program at the end, showing its usage. A few other changes have also been made.
* config: don't pass null strings to *printf()Pranjal Kole2022-02-05-18/+61
| | | | | | | | | | | | | musl and glibc's *printf() convert NULL strings to "(null)" [0][1], but this is undefined behaviour. context.value has to be set to two backspaces, so that the extra colon is removed. context.key is set to one backspace, so that the extra dot is removed. context.section is now set to "main" by default, so it is never NULL. [0]: https://git.musl-libc.org/cgit/musl/tree/src/stdio/vfprintf.c#n593 [1]: https://sourceware.org/git/?p=glibc.git;a=blob;f=stdio-common/vfprintf-internal.c;hb=HEAD#l1011
* config: support Copy and Paste keycodes by defaultMark Stosberg2022-01-25-0/+2
| | | | | | | | | | | | These work as expected and don't interfere with anything else. They are useful on the increasing number of keyboards with custom firmware. The keycodes enable using the same key combination for terminals as other apps. For example: by holding down a layer-switching key with a thumb, the Copy and Paste key codes can be assigned to the C and V keys on a secondary layer, making for a natural universal copy/paste key combination.
* config: convert tweak.render_timer to an enumDaniel Eklöf2022-01-13-15/+7
|
* Add irc:// to default URL schemesSimon Ser2021-12-27-0/+2
|
* config: update most parse_section_*() functions to return in each if-branchDaniel Eklöf2021-12-25-28/+20
|
* config: scrollback: add missing return for ‘lines’Daniel Eklöf2021-12-25-1/+1
| | | | The missing return meant failures were not reported correctly.
* config: csd.border_width now always reflects the full/total widthDaniel Eklöf2021-12-22-0/+6
|
* config: error out on empty key- or mouse bindingDaniel Eklöf2021-12-18-0/+6
| | | | Closes #851
* config: NOINLINE modifiers_to_str()Daniel Eklöf2021-12-11-1/+1
|
* config: resolve collisions: argv_compare() returns -1,0,+1, not a boolDaniel Eklöf2021-12-11-1/+4
|
* config: resolve collisions: return ‘false’ on failureDaniel Eklöf2021-12-11-0/+2
|
* config: use “(default)” as path in log message, if path is NULLDaniel Eklöf2021-12-11-1/+2
|
* config: remove unneeded function prototypeDaniel Eklöf2021-12-11-4/+0
|
* config: unify key- and mouse bindingsDaniel Eklöf2021-12-11-397/+211
| | | | | | | | | | | | | | With this patch, key- and mouse-bindings structs (the non-layout specific ones) are unified into a single struct. The logic that parses, and manages, the key- and mouse binding lists are almost identical. The *only* difference between a key- and a mouse binding is that key bindings have an XKB symbol, and mouse bindings a button and click-count. The new, unified, struct uses a union around these, and all functions that need to know which members to use/operate on now takes a ‘type’ parameter.
* config: do mouse binding collision detection after loading the confDaniel Eklöf2021-12-11-206/+214
|
* config: value_to_key_combos(): reset modifiers in bindingDaniel Eklöf2021-12-11-0/+1
|
* config: do key binding collision detection after loading the confDaniel Eklöf2021-12-11-199/+244
| | | | | | | | | | | | | | | | | | | | | | | | | | This allows the user to write, to swap two key bindings: [key-bindings] show-urls-launch=Control+Shift+r search-start=Control+Shift+u instead of: [key-bindings] search-start=none show-urls-launch=Control+Shift+r search-start=Control+Shift+u This should simplify the configuration for people who replace a lot of the default key bindings. This also simplifies the parsing somewhat, since we no longer has to parse a key-binding into a temporary list, ensure it doesn’t have any collisions, and then copy it into the actual key binding list. _While_ parsing a key-binding, we still need a temporary array (at least for the time being), but that temporary array is no longer visible outside the parsing function that allocates it.
* config: remove struct key_combo, use config_key_binding insteadDaniel Eklöf2021-12-11-179/+146
|
* config: improve error reporting when selection-override-modifiers conflict with mouse bindingsfeeptr@codeberg.org2021-12-04-7/+54
|
* config: move button_map out of value_to_mouse_combos for reusefeeptr@codeberg.org2021-12-02-17/+17
| | | | this mapping is only available here or in libevdev (libevdev_event_code_get_name) and it's simpler to factor it out here
* config, doc, changelog: move selection-override-modifiers to [mouse-bindings] and validate other ↵feeptr@codeberg.org2021-12-02-7/+31
| | | | | | case specifically, check for conflicts both when mouse bindings are set and when the selection-override-modifiers setting itself is set
* config: parse 'none' as empty modifiers valuefeeptr@codeberg.org2021-12-02-0/+5
|
* config, input: allow configuring select-override modifiersfeeptr@codeberg.org2021-12-02-10/+76
|
* config: add tweak.grapheme-width-method=maxDaniel Eklöf2021-11-23-1/+1
| | | | | | ‘max’ is a new value for ‘tweak.grapheme-width-method’. When enabled, the width of a grapheme cluster is that of the cluster’s widest codepoint.
* 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.
* | | config: create a copy of the section nameDaniel Eklöf2021-11-21-2/+8
| |/ |/| | | | | | | | | | | | | | | | | | | | | 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.
* | 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.
* config: letter-spacing: add missing ‘return’Daniel Eklöf2021-11-15-1/+1
| | | | | | | | | 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
* user-notification: config: various small cleanupsCraig Barnes2021-11-14-13/+8
| | | | | | | * 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/+0
| | | | | | | * [main].bell * [main].jump-label-letters * [main].url-launch * [main].osc8-underline
* config: add [colors].dim0-7Daniel Eklöf2021-11-13-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* config: scrollback.indicator.text: use value_to_wchars()Daniel Eklöf2021-11-13-13/+2
|
* 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-50/+18
|
* 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-12/+13
|
* config: add {str,value}_to_uint{16,32}()Daniel Eklöf2021-11-13-92/+78
| | | | | 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-287/+161
| | | | | | 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
|
* 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
|
* csd: add support for a visible borderDaniel Eklöf2021-10-27-2/+27
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* config: add [key-bindings].noop actionDaniel Eklöf2021-10-27-0/+1
| | | | | | | Key combinations assigned to this action will not be sent to the application. Closes #765
* config: error out on invalid grapheme-width-method valuesDaniel Eklöf2021-10-21-0/+7
|
* config: enable grapheme shaping by defaultDaniel Eklöf2021-10-13-4/+6
| | | | | | | | This changes the default value of tweak.grapheme-shaping to “yes”, thus enabling grapheme shaping by default. It also changes the default value of tweak.grapheme-width-method to “wcswidth”, for maximum compatibility with terminal applications.
* config, render: scrollback indicator: allow configuring scrollback indicator colorsfeeptr@codeberg.org2021-10-09-0/+13
|
* notify: add the notify-focus-inhibit config optionMitja Horvat2021-10-06-0/+5
| | | | | | | | | | | | | | | foot doesn't show desktop notifications (via OSC777) if the current terminal has keyboard focus. This is probably a sane default, but there are use cases where showing a notification regardless of the focus status may be desired. For example, a completion notification of a long running task inside a non-focused tmux window. This PR adds the notify-focus-inhibit option which can be used to disable inhibition of notifications when the window has focus. The default value is `yes`, which retains the old behavior.
* config: add comments to default_color_table[] about color channel valuesCraig Barnes2021-09-25-0/+2
|
* config: simplify initialization of color table in config_load()Craig Barnes2021-09-25-46/+31
|
* config: codespell: setting has only two ‘t’Daniel Eklöf2021-08-31-1/+1
|
* main: verify primary font is monospaced at startupDaniel Eklöf2021-08-31-0/+52
| | | | | | | | | | Load a couple of ASCII glyphs and check if their advance widths matches. If not, warn the user that the font is probably not monospaced. This can be disabled by setting tweak.font-monospace-warn=no. Closes #704.
* 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
* config: add url.uri-charactersDaniel Eklöf2021-08-09-0/+35
| | | | | | | | | | | | This option specifies the characters allowed in the auto-detected URLs. Any character not in this set constitutes an URL delimiter, and will never be included in auto-detected URLs. This option does not affect OSC-8 URLs. Closes #654
* config: include: use xasprintf() instead of two calls to snprintf()Daniel Eklöf2021-07-30-3/+1
|
* config: include: handle get_user_home_dir() returning NULLDaniel Eklöf2021-07-30-2/+9
|
* config: include: add support for ~-expansionDaniel Eklöf2021-07-30-1/+15
| | | | Closes #659
* config: add csd.font optionDaniel Eklöf2021-07-24-15/+83
|
* render: Allow cells to bleed into their neighborTimur Celik2021-07-17-12/+5
| | | | | | | | | | | | | | | | This patch adds a `confined` flag to each cell to track if the last rendered glyph bled into it's right neighbor. To keep things simple, bleeding into any other neighbor cell than the immediate right one is not allowed. This should cover most use cases. Before rendering a row we now do a prepass and mark all cells unclean that are affected by a bleeding neighbor. If there are consecutive bleeding cells, the whole group must be re-rendered even if only a single cell has changed. The patch also deprecates both old overflowing glyph options *allow-overflowing-double-width-glyphs* and *pua-double-width* in favor of a single new one named *overflowing-glyphs*.