aboutsummaryrefslogtreecommitdiff
path: root/config.h (follow)
Commit message (Collapse)AuthorAgeLines
...
* enhanced bell configurationRyan Farley2021-05-07-6/+7
| | | | | | | | | | Add a separate section for bell configuration, with a bell-specific command option and a setting to allow that command to run without regard to keyboard focus (for those of us who enjoy being beeped at at all times, for example). The actions are also no longer mutually exclusive; this is primarily anticipating urgency support which cannot be replicated outside the process (in server mode anyway) and would thus be complementary to any notification or arbitrary command.
* config: add ‘beam-thickness’ optionDaniel Eklöf2021-04-30-0/+1
| | | | | | | | | | | * Rename cursor.style value ‘bar’ to ‘beam’. ‘bar’ remains recognized, but should eventually be deprecated and then removed. * Add ‘cursor.beam-thickness’ option, a pt-or-px value specifying the thickness of the beam cursor. Defaults to 1.5pt. * Rename (and export) pt_or_px_as_pixels() to term_pt_or_px_as_pixels() * Change term_pt_or_px_as_pixels() to round point values instead of truncating them.
* config: bold-text-in-bright: add ‘palette-based’ as a special valueDaniel Eklöf2021-04-17-1/+5
| | | | | | | | | When ‘bold-text-in-bright’ is set ‘to palette-based’, colors matching one of the 8 regular palette colors are brightened by using the corresponding bright palette color. Other colors, or all colors if ‘bold-text-in-bright’ is set to ‘yes|true’, are brightened by increasing the luminance.
* config: add box-drawings-uses-font-glyphs=no|yes optionDaniel Eklöf2021-04-09-0/+2
| | | | | | | | | When disabled, we render box drawing characters ourselves. This is the default. When enabled, we instead use font glyphs. I.e. no special treatment. Closes #430
* config/terminal: refactor: remove “default_*” color members from terminal structDaniel Eklöf2021-04-07-2/+1
| | | | Access the original colors in the configuration instead.
* term: increase/decrease custom line-height with font size changesDaniel Eklöf2021-03-21-6/+0
| | | | | | | | When the user has set a custom line-height, we now adjust it when increasing/decreasing (“zooming”) the font size at run-time. Previously, the line-height was fixed at the size specified in foot.ini.
* add option to detach the client process from the terminal instanceFelipe Trzaskowski2021-03-13-0/+1
|
* config: reuse HAVE_TERMINFO via DEFAULT_TERMChloe Kudryavtsev2021-02-26-0/+6
| | | | | add detection in --help output also make it more easily accessible for other locations to change
* urls: OSC-8 URLs can now optionally be underlined outside of url-modeDaniel Eklöf2021-02-21-0/+5
| | | | | | | | | | | | | | | | | | | | | This patch adds a new configuration option, ‘osc8-underline=url-mode|always’. When set to ‘url-mode’, OSC-8 URLs are only highlighted (i.e. underlined) in url-mode, just like auto-detected URLs. When set to ‘always’, they are always underlined, regardless of mode, and regardless of their other attributes. This is implemented by tagging collected URLs with a boolean, instructing urls_render() and urls_reset() whether they should update the cells’ ‘url’ attribute or not. The OSC-8 collecter sets this based on the value of ‘osc8-underline’. Finally, when closing an OSC-8 URL, the cells are immediately tagged with the ‘url’ attribute if ‘osc8-underline’ is set to ‘always’.
* config: add jump-label-letters optionDaniel Eklöf2021-02-13-0/+1
|
* key-bindings: refactor: use a single type for all key bindingsDaniel Eklöf2021-02-08-25/+12
| | | | | | | | | | | | | | | | Up until now, the various key binding modes (“normal”, “search” and “url”) have used their own struct definitions for their key bindings. The only reason for this was to have a properly typed “action” (using the appropriate “action” enum). This caused lots of duplicated code. This patch refactors this to use a single struct definition for the “unparsed” key bindings handled by the configuration, and another single definition for “parsed” bindings used while handling input. This allows us to implement configuration parsing, keymap translation and so on using one set of functions, regardless of key binding mode.
* config: use a bitfield for flags tracking whether to use custom colors for CSD or notDaniel Eklöf2021-02-07-4/+4
|
* config: add colors.jump_labels and colors.urlsDaniel Eklöf2021-02-07-0/+8
| | | | | | | | | | * colors.jump_labels configures the foreground and background colors used when rendering URL jump labels. Defaults to “regular0 regular3” (i.e. black on yellow). * colors.urls configures the color to use when highlighting URLs in URL mode. Note that we aren’t currently doing any highlighting... Defaults to regular3 (i.e. yellow).
* config: use a packed bitfield for “use custom color” flagsDaniel Eklöf2021-02-07-1/+4
|
* config: add ‘url-launch’ option, defaulting to “xdg-open ${url}”Daniel Eklöf2021-02-07-4/+7
|
* config: add infrastructure to handle URL mode specific key bindingsDaniel Eklöf2021-02-07-0/+9
| | | | | | * Add “show-urls” action to regular key bindings * Add url-bindings section to foot.ini * Add “cancel” action to URL mode key bindings
* config: promote tweak.resize-delay-ms to a real, supported optionDaniel Eklöf2021-01-26-1/+1
|
* render: delay TIOCSWINSZ while doing an interactive resizeDaniel Eklöf2021-01-26-0/+1
| | | | | | | | | | | | | | | | | | | Instead of disabling content centering, delay the TIOCSWINSZ (a.k.a delay sending the new dimensions to the client) by a small amount while doing an interactive resize. Non-interactive resizes are still immediate. For now, force a resize when the user stops the interactive resize. This ensures the client application receives the new dimensions immediately. It still works without the last, forced, resize, but there typically be a small delay until the client application receives the final dimensions. Closes #301 Closes #283
* config: add ‘none’ as a possible value for ‘selection-target’Daniel Eklöf2021-01-23-0/+1
| | | | | | | When ‘selection-target’ is set to ‘none’, selecting text does not copy the text to _any_ clipboard. This patch also refactors the value parsing to be data driven.
* config: add new option ‘selection-target’Daniel Eklöf2021-01-23-0/+5
| | | | | This option controls the clipboard target that selected text should be copied to.
* config: add temporary(?) tweak option for box drawing line thicknessDaniel Eklöf2021-01-12-0/+1
|
* config: pt_or_px cannot be a unionDaniel Eklöf2021-01-11-5/+5
|
* config: fix comment: -1 is a valid ‘px’ valueDaniel Eklöf2021-01-11-1/+1
|
* config: line-height, letter-spacing: values are in pt by default, but we allow pxDaniel Eklöf2021-01-11-4/+10
| | | | | | | | If the value is specified without a unit, then the value is assumed to be in points, subject to DPI scaling. The value can optionally have a ‘px’ suffix, in which case the value is treated as a raw pixel count.
* config: add line-height, letter-spacing, {horizontal,vertical}-letter-offsetDaniel Eklöf2021-01-11-0/+8
|
* config: add optional ‘center’ argument to ‘pad’Daniel Eklöf2021-01-06-0/+1
| | | | | | | | | | When set, the grid contents is centered in the window. I.e. the left/right and top/bottom margins are equal (+- 1px). This causes the content to “jump” while doing an interactive resize, but may still be preferred in e.g. a tiling WM. Closes #273
* fonts: size fonts using the scaling factor when output scaling is enabledDaniel Eklöf2020-12-17-1/+1
| | | | | | | | | | | | | | | | | | | This extends the new ‘dpi-aware’ option with a new default value, ‘auto’. When set to ‘auto’, fonts are sized using monitors’ DPI when output scaling is disabled. When output scaling is enabled, fonts are instead sized using the scaling factor. The reasoning here is that a user that has enabled output scaling is obviously *not* relying on DPI scaling. Output scaling can also be a way to compensate for different viewing distances, in which case we do *not* want to break that by using DPI scaling. Users can still force DPI-only font sizing by setting ‘dpi-aware=yes’, or disable it completely by setting ‘dpi-aware=no’.
* config_font_parse(): return fail/successDaniel Eklöf2020-12-15-1/+1
|
* config: add ‘notify’ to possible values for ‘bell’ in foot.iniDaniel Eklöf2020-12-10-1/+5
| | | | | When `bell=notify`, foot will trigger a desktop notification when it receives a BEL in an unfocused window.
* osc: implement urxvt’s “OSC 777;notify”Daniel Eklöf2020-12-09-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | OSC 777 is URxvt’s generic escape to send commands to its perl extensions. The first parameter is the name of the extension, followed by its arguments. OSC 777;notify is a, if not well established, at least a fairly well known escape sequence to request a (desktop) notification. The syntax is: \e]777;notify;<title>;<body>\e\\ Neither title nor body is escaped in any way, meaning they should not contain a ‘;’. Foot will split title from body at the *first* ‘;’. Any remaining ‘;’ characters are treated as part of ‘body’. Instead of adding built-in support for the freedesktop notification specification (which would require us to link against at least dbus), add a new config option to foot.ini: ‘notify’. This option specifies the command to execute when a notification is received. ‘${title}’ and ‘${body}’ can be used anywhere, in any combination, and as many times as you want, in any of the command arguments. The default value is ‘notify-send -a foot -i foot ${title} ${body}’
* config: replace union in config struct with simple width/height membersCraig Barnes2020-11-30-10/+2
|
* config: add ‘dpi-aware’ option, defaulting to enabledDaniel Eklöf2020-11-19-0/+1
| | | | | | | | | | When disabled, foot no longers uses outputs’ DPI to scale the font. Instead, it uses the outputs’ scaling factor. That is, instead of appending “:dpi=123” to the fontconfig string, modify the “:pixelsize” or “:size” attribute. Closes #206
* config: add default.bold-text-in-bright optionDaniel Eklöf2020-11-14-0/+1
|
* config: add support for pipe-* actions in mouse bindingsDaniel Eklöf2020-11-06-0/+5
| | | | Closes #183
* config: add font-bold, font-italic and font-bold-italic optionsDaniel Eklöf2020-10-20-1/+2
| | | | | | | | | | These options lets the user configure custom fonts and styles, to use with the bold and italic cell attributes. By default, they are unset, meaning we use the bold/italic variants of the regular font. Closes #169.
* csi: implement ‘CSI ? 1042 h/l’ - enable/disable bell-is-urgentDaniel Eklöf2020-10-11-1/+1
|
* conf: csd.preferred can now be set to ‘none’Daniel Eklöf2020-10-10-1/+1
| | | | | | | | | | | When csd.preferred == none, we will request CSDs from the compositor, but internally render as if we are using SSDs. That is, we don’t render any window decorations at all. Note that some compositors may ignore our request to use CSDs, and still render SSDs for us. Closes #163
* config: add ‘[default].word-delimiters’Daniel Eklöf2020-10-09-0/+1
| | | | | | | | | | This option lets the user configure which characters act as word delimiters when selecting text. This affects both “double clicking”, and ‘ctrl-w’ in scrollback search mode. Closes #156
* bell: optionally render margins in red when receiving BELDaniel Eklöf2020-10-08-0/+2
| | | | | | | | | | | Add anew config option, ‘bell=none|set-urgency’. When set to ‘set-urgency’, the margins will be painted in red (if the window did not have keyboard focus). This is intended as a cheap replacement for the ‘urgency’ hint, that doesn’t (yet) exist on Wayland. Closes #157
* config: add mouse.alternate-scroll-mode optionDaniel Eklöf2020-09-15-0/+1
| | | | | This option controls the initial state of the Alternate Scroll Mode, and defaults to ‘enabled’.
* config: add tweak.scaling-filterDaniel Eklöf2020-09-13-0/+1
| | | | | | | | Use the new fcft_set_scaling_filter() API to use a non-default scaling filter. By default, we use lanczo3, the ‘best’ filter. This overrides the default in fcft, which is ‘cubic’ filtering.
* Add -W,--window-size-chars, and foot.ini:initial-window-size-charsDaniel Eklöf2020-09-08-3/+21
| | | | | | | | | | | * 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
* config: add tweak.damage-whole-windowDaniel Eklöf2020-09-06-0/+1
| | | | | | | | | | When enabled, foot will ‘damage’ the entire window, instead of just the modified/updated rows. This will force the compositor to redraw/blend the whole window. This can be used to workaround an issue with fractional scaling in Gnome, where random thin lines may appear.
* render: optionally enable heuristics that deal with private usage area charsDaniel Eklöf2020-09-03-0/+1
| | | | | | | | | | | | | | Try to detect double-width *glyphs* for single-width *characters*, and allow them to overflow into the next cell. This is only done for single-width chars with a glyph width that is at least 1.5 cells wide, but at most 3 cells. The feature is gated by the new ‘tweak.allow-overflowing-double-width-glyphs’, and is disabled by default. Closes #116
* config: key/mouse bindings: refactor: less parsing in keyboard_enter()Daniel Eklöf2020-08-13-7/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This simplifies the handling of mouse and keyboard bindings. Before, the bindings where parsed *both* when loading the configuration, and then on every keyboard enter event. This was done since keys require a keymap to be decoded. Something we don't have at configuration time. The idea was that at config time, we used a default keymap just to verify the key combo strings were valid. The following has changed: * The bindings in the config struct is now *one* key combo per entry. Previously, it was one *action* per entry, and each entry had one or more key combos. Doing it this way makes it easier when converting the binding in the keyboard enter event (which previously had to expand the combos anyway). * The bindings in the config struct no longer contains any unparsed strings. A key binding contains a decoded 'modifier' struct (which specifies whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the binding to be used). It also contains a decoded XKB keysym. * A mouse binding in the config struct is similar to a key binding, except it contains the button, and click count instead of the XKB key sym. * The modifiers in the user-specified key combo is decoded at config time, by using the pre-defined XKB constants XKB_MOD_NAME_<modifier>. The result is stored in a 'modifiers' struct, which is just a collection of booleans; one for each supported modifier. The supported modifiers are: shift, ctrl, alt and meta/super. * The key sym is decoded at config time using xkb_keysym_from_name(). This call does *not* depend on a keymap. * The mouse button is decoded at config time using a hardcoded mapping table (just like before). * The click count is currently hard-coded to 1. * In the keyboard enter event, all we need to do is pre-compute the xkb_mod_mask_t variable for each key/mouse binding, and find all the *key codes* that map to the (already decoded) symbol. For mouse bindings, the modifiers are the *only* reason we convert the mouse bindings at all. In fact, on button events, we check if the seat has a keyboard. If not, we use the mouse bindings from the configuration directly, and simply filter out those with a non-empty set of modifiers.
* config: wip: add support for modifiers in mouse bindingsDaniel Eklöf2020-08-13-3/+8
| | | | | | | Mouse bindings can now include modifiers. They are specified in pretty much the same way as in keyboard bindings: Control+BTN_LEFT
* config: add tweak.render-timer optionDaniel Eklöf2020-08-13-0/+2
| | | | | | | | | This can be set to 'none' (the default), 'osd', 'log' or 'both'. When 'osd' is enabled, we'll render the frame rendering time to a sub-surface after each frame. When 'log' is enabled, the frame rendering time is logged on stderr.
* config: make selection foreground/background colors configurableDaniel Eklöf2020-08-12-0/+3
| | | | | | | | | The default is still to inverse the regular foreground/background colors. If the user sets *both* of the new options, selection-foreground and selection-background, those colors will *always* be used for selected cells, instead of inverting the regular foreground/background colors.
* config: move cursor.hide-when-typing to mouse.hide-when-typingDaniel Eklöf2020-08-04-1/+4
|
* config: add scrollback.multiplier optionDaniel Eklöf2020-08-03-0/+1
| | | | | | | This option is used to multiply the mouse scroll amount for mouse and trackpad based scrollback scrolling. Closes #54.
* config: add 'hide-when-typing'Daniel Eklöf2020-07-31-0/+1
| | | | | | When enabled, the mouse cursor is hidden when the user types in the terminal. It is un-hidden when the user moves the mouse, or when the window loses keyboard focus.
* config: configuration errors are no longer fatalDaniel Eklöf2020-07-31-1/+1
| | | | | Instead of refusing to start foot on configuration errors, we start and print a user-notification.
* user-notification: 'productify' the user-warning systemDaniel Eklöf2020-07-30-1/+2
| | | | | | | | * Rename user_warning to user_notification * Add warning and error types (in addition to the existing deprecated) * Simplify logic when emitting a user notification after forking; we don't need to copy the notification data since we're in a new process and have total control over that memory.
* config: tokenize key bindings' pipe command when loading the configurationDaniel Eklöf2020-07-30-1/+4
| | | | | | This allows us to detect syntax errors early on, and is also more efficient since we don't have to re-tokenize the command line every time the binding is executed.
* term: add capability to print warnings *inside* the terminalDaniel Eklöf2020-07-29-0/+2
| | | | | This is intended to be used to print e.g. deprecation warnings inside the terminal, *before* the shell is started.
* config: add free-form text variant to 'scrollback-indicator-format'Daniel Eklöf2020-07-28-1/+4
| | | | And make the empty string the new default.
* config: rename scrollback-indicator-style to scrollback-indicator-positionDaniel Eklöf2020-07-27-4/+4
|
* config: scrollback-indicator-format: percent -> percentageDaniel Eklöf2020-07-26-1/+1
|
* config: rename scrollback-indicator-style value 'static' to 'fixed'Daniel Eklöf2020-07-25-1/+1
|
* config: rename scrollback-indicator-style value 'moving' to 'relative'Daniel Eklöf2020-07-25-1/+1
|
* config: rename scrollback-indicator to scrollback-indicator-styleDaniel Eklöf2020-07-25-3/+16
| | | | | | | | And turn it from a boolean to an enum. It can be set to: * `none` - disables the indicator * `static` - always rendered near the top of the window * `moving` - position reflects the scrollback position
* config: add 'scrollback-indicator-format' optionDaniel Eklöf2020-07-24-0/+1
| | | | | The value of this option must be either 'percent', or 'line', and determines _how_ we render the scrollback indicator.
* config: rename show-scrollback-position to scrollback-indicatorDaniel Eklöf2020-07-24-1/+1
|
* config: add 'show-scrollback-position' option to footrcDaniel Eklöf2020-07-24-0/+1
|
* conf: bindings: allow several mappings for the same actionDaniel Eklöf2020-07-15-5/+15
| | | | | If the bindings has different pipe command associated with them, treat them as different actions.
* config: add support for appending a 'spawn' argument to key bindingsDaniel Eklöf2020-07-15-0/+2
| | | | | | | | | | | | A key binding may now have an optional ':<cmd>' string appended to the key. This is intended to be used like so: pipe-scrollback:sh -c "cat > file"=Print TODO: we still only allow one *action*. Meaning you still cannot specify multiple pipe-scrollback bindings, for example.
* term: don't use deprecated fcft_size_adjust()Daniel Eklöf2020-07-07-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | When resizing the font on-the-fly, we now do a complete font-reload (this is basically what fcft_size_adjust() did anyway). To get the correct size, we maintain the current size ourselves. We get the initial size from the user-provided font pattern, by converting the string to an FcPattern, and using FcPatternGet() to retrieve both the FC_SIZE and FC_PIXEL_SIZE attributes. These attributes are then removed from the pattern, and the pattern is converted back to a string. The terminal struct maintains a copy of the font sizes. These are initially set to the sizes from the config. When the user resizes the font, the terminal-local sizes are adjusted. To ensure the primary and user-configured fallback fonts are resizes equally much, convert any pixel sizes to point sizes at this point. When the font size is reset, we reload the font sizes from the config (thus once again returning actual pixel-sizes, if that's what the user has configured).
* config: add 'blink' option to cursor section in footrcDaniel Eklöf2020-06-30-0/+1
| | | | | This option controls whether the default cursor should blink or not. The default is to *not* blink.
* conf: add 'title' conf option and --title command line optionDaniel Eklöf2020-04-01-0/+1
|
* conf: add app-id config option and --app-id command line optionDaniel Eklöf2020-04-01-0/+1
|
* Merge branch 'master' into scroll-damage-performanceDaniel Eklöf2020-03-27-0/+1
|\
| * config: add 'startup-mode' optionDaniel Eklöf2020-03-26-0/+1
| | | | | | | | | | This option controls the initial window mode: windowed, maximized or fullscreen. The default is windowed.
* | shm: make max pool size user configurable (via a 'tweak' setting)Daniel Eklöf2020-03-25-0/+1
|/
* search: replace hard-coded key bindings with "user configurable" onesDaniel Eklöf2020-03-18-1/+1
| | | | | | | | They aren't really user configurable. At least not yet. However, with this, we now handle raw key codes just like the normal key bindings. Meaning, e.g. ctrl+g, ctrl+a, ctrl+e etc now works while searching with e.g. a russian layout.
* conf: make delayed rendering timeouts configurableDaniel Eklöf2020-03-17-0/+5
| | | | | | | | | | | This adds an undocumented 'tweak' section to footrc, with two new options: * delayed-render-lower * delayed-render-upper Both takes an integer value, representing the lower/upper timeout values (in nano seconds) for delayed rendering.
* config/input: implement mouse bindingsDaniel Eklöf2020-03-12-1/+1
| | | | | | | | | | * New config section, "mouse-bindings", where bindings are defined on the form "action=BTN_<name> * pointer_button() handler now scans the bindings list instead of hardcoding primary-paste to BTN_MIDDLE. * The implementation handles single- double- and triple clicks in the bindings, but there is currently no way to define anything but a single-click binding in the configuration.
* wip: initial framework for dealing with key/mouse bindings in different modesDaniel Eklöf2020-03-08-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds initial support for defining key and mouse bindings that are applied in different terminal modes/states. For example, there are two arrays dealing with key and mouse bindings in the "normal" mode. Most bindings will go here. There's also an array for "search" mode. These bindings will be used when the user has started a scrollback search. In the future, there may be a model selection mode as well. Or maybe "search" and "modal selection" will be combined into a single "keyboard" mode. We'll see. Since the keyboard bindings depend on the current XKB keymap, translation from the user specified key combination string cannot be done when loading the configuration, but must be done when we've received a keymap from the wayland server. We should explore if it's possible to load some kind of default keymap just to be able to verify the validity of the key combination strings at configuration load time, to be able to reject the configuration at startup. A couple of key bindings have been added as proof of concept. Mouse bindings aren't handled at all yet, and is likely to be re-written. For example, we can probably translate the configuration strings at configuration load time.
* config: CSD borders are always invisibleDaniel Eklöf2020-03-03-2/+0
| | | | | That is, remove all configuration options and always draw them fully transparent.
* csd: initial implementation of minimize/maximize/close buttonsDaniel Eklöf2020-03-02-0/+7
|
* config: make CSD user configurableDaniel Eklöf2020-03-02-0/+14
| | | | | | | | | | | | | | The user can now configure the following: * Whether to prefer CSDs or SSDs. But note that this is only a hint to the compositor - it may deny our request. Furthermore, not all compositors implement the decoration manager protocol, meaning CSDs will be used regardless of the user configuration (GNOME/mutter being the most prominent one). * Title bar size and color, including transparency * Border size and color, including transparency Also drop support for rendering the CSDs inside the main surface.
* config: add 'login-shell' optionDaniel Eklöf2020-02-20-0/+1
|
* config: add 'pad' option, default to 2Daniel Eklöf2020-02-15-0/+2
|
* Implement --holdDaniel Eklöf2020-02-03-0/+1
| | | | When specified, we don't exit when the slave/client process exits.
* wayland: optionally use the presentation time protocol to measure input lagDaniel Eklöf2019-12-31-1/+1
| | | | | | | | | | | | | | | | | | | This adds a flag, -p,--presentation-timings, that enables input lag measuring using the presentation time Wayland protocol. When enabled, we store a timestamp when we *send* a key to the slave. Then, when we commit a frame for rendering to the compositor, we request presentation feedback. We also store a timestamp for when the frame was committed. The 'presented' callback then looks at the input and commit timestamps, and compares it with the presented timestamp. The delay is logged at INFO when the delay was less than one frame interval, at WARN when it was one frame interval, and at ERR when it was two or more frame intervals. We also update statistic counters that we log when foot is shut down.
* config: enable user to specify path to configuration fileDaniel Eklöf2019-12-17-1/+1
|
* config: add 'server_socket_path' and set a default valueDaniel Eklöf2019-12-14-0/+2
|
* fcft: use fcft instead of local copy of font.c/font.hDaniel Eklöf2019-12-01-1/+2
|
* add config + command line option for setting initial window width/heightDaniel Eklöf2019-08-23-0/+3
|
* render: replace all usage of cairo with pixmanDaniel Eklöf2019-08-16-1/+1
|
* Add background alpha supportDaniel Eklöf2019-08-15-0/+1
|
* conf: make number of scrollback lines configurableDaniel Eklöf2019-08-01-0/+2
|
* font: add support for fallback fontsDaniel Eklöf2019-07-30-1/+2
| | | | | | | | | | | | | | | A top-level font now has a list of fallback fonts. When a glyph cannot be found, we try each fallback font in turn, until we either find one that has the glyph, or until we've exhausted the list. To make this actually work in practise (read: to make performance acceptable), the cache is re-worked and is now populated on demand. It also supports non-ASCII characters, by using the 4-byte unicode character as index instead. Since having an array that can be indexed by a 4-byte value isn't really viable, we now have a simple hash table instead of an array.
* wip: initial multithreaded rendererDaniel Eklöf2019-07-29-0/+2
|
* conf: allow the user to configure a fixed cursor colorDaniel Eklöf2019-07-23-0/+4
| | | | | | | | | | | | | | | | | | | The default is to reverse the foreground/background colors in the cell with the cursor. But, if the user configures a specific set of cursor colors, those will always be used, regardless of other cell attributes (dim, reverse etc). The cursor color is specified as two color values, 'text' and 'cursor'. The block cursor uses the 'cursor' color as background, and the 'text' color for the glyph. All other cursor styles uses the 'cursor' color for the cursor, but uses the cell's foreground color for the glyph (meaning, dim/reverse/etc applies).
* conf: make cursor's default style configurableDaniel Eklöf2019-07-22-0/+6
|
* conf: config now provides the colors (though still only hardcoded colors)Daniel Eklöf2019-07-21-0/+8
|
* conf: TERM can now be set in footrcDaniel Eklöf2019-07-18-0/+1
|
* conf: improve configuration file parsingDaniel Eklöf2019-07-17-1/+3
| | | | | | | * Strip whitespaces from keys and values * Detect (and ignore) comments * Detect syntax errors (no value specified etc) * Error out on syntax errors and invalid keys
* conf: get user's shellDaniel Eklöf2019-07-17-0/+1
|
* conf: initial support for configuration fileDaniel Eklöf2019-07-16-0/+8
* Look for configuration file in (in this order): - XDG_CONFIG_HOME/footrc - ~/.config/footrc * Currently supports setting the font