aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
| * osc/notify: add support for OSC-99, kitty desktop notificationsDaniel Eklöf2024-07-23-15/+322
|/ | | | | | | | | | | | | | | | | | | | | | | | | | This adds limited support for OSC-99, kitty desktop notifications[^1]. We support everything defined by the "protocol", except: * 'a': action to perform on notification activation. Since we don't trigger the notification ourselves (over D-Bus), we don't know a) which ID the notification got, or b) when it is clicked. * ... and that's it. Everything else is supported To be explicit, we *do* support: * Chunked notifications (d=0|1), allowing the application to append data to a notification in chunks, before it's finally displayed. * Plain UTF-8, or base64-encoded UTF-8 payload (e=0|1). * Notification identifier (i=xyz). * Payload type (p=title|body). * When to honor the notification (o=always|unfocused|invisible), with the following quirks: - we don't know when the window is invisible, thus it's treated as 'unfocused'. - the foot option 'notify-focus-inhibit' overrides 'always' * Urgency (u=0|1|2) [^1]: https://sw.kovidgoyal.net/kitty/desktop-notifications/
* input: allow mouse selections to start inside the marginsDaniel Eklöf2024-07-19-59/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before this, margins were special cased: * The mouse cursor was always a pointer, and never an I-beam (thus signaling selections cannot be made). * The internal mouse coords where set to -1 when the cursor was inside the margins, causing: - text selections from being made - mouse events being passed to mouse grabbing applications In particular, even with a one-pixel margin, making selections was unnecessarily hard in e.g. fullscreen mode, where you'd expect to be able to throw the cursor into the corner of the screen and then start a selection. With this patch, the cursor is treated as if it was in the first/last column/row, when inside the margin(s). An unintended side-effect of this, initially, was that auto-scrolling selections where way too easy to trigger, since part of its logic is checking if the cursor is inside the margins. That problem has been reduced by two things: * auto-scrolling does not occur unless a selection has been started. That is, just holding down the mouse in the margins and moving up/down doesn't cause scrolling. You have to first select at least one cell in the visible viewport. * A selection isn't fully started (i.e. a cell is actually selected) unless the cursor is inside the actual grid, and *not* in the margins. What does the last point mean? We now allow a selection to be _started_ when clicking in the margin. What this means internally is we set a start coordinate for a selection, but *not* and end coordinate. At this point, we don't have an actual selection. Nothing is selected, and no cells are highlighted, graphically. This happens when we set an end coordinate. Without the last bullet point, that would happen as soon as the cursor was _moved_, even if still inside the margins. Now, we require the cursor to leave the margins and touch an actual cell before we set an end coordinate. Closes #1702
* csi: in-band window resize notifications, private mode 2048Daniel Eklöf2024-07-19-0/+60
| | | | | | | | | | | | | This implements https://gist.github.com/rockorager/e695fb2924d36b2bcf1fff4a3704bd83, in-band window resize notifications. When user enables private mode 2048 (in-band resize notifications), *always* send current size, even if the mode is already active. This ensures applications can rely on getting a reply from the terminal.
* wayland: #ifdef guard code related to wl_shm_release()Daniel Eklöf2024-07-18-0/+6
|
* foot.info: add setal (colored underlines)Daniel Eklöf2024-07-18-0/+1
| | | | | This is an alias to Setulc. Upstream (ncurses) terminfo uses setal instead of Setulc :/
* meson/pgo: fix PGO build errors with recent meson(?) versionsDaniel Eklöf2024-07-18-2/+8
| | | | | | The back-reference to 'tokenize.c' in the parent directory causes PGO build failures, where gcc can't find the PGO data. Likely due to path/naming issues caused by meson's generated build directories.
* log: respect the NO_COLOR environment variableDaniel Eklöf2024-07-18-1/+10
| | | | | | http://no-color.org/ Closes #1771
* wayland: use wl_shm v2 if availableDaniel Eklöf2024-07-18-3/+17
|
* themes: catppuccin: replace with updated flavorsabs3nt2024-07-18-26/+135
| | | | Pulled from https://github.com/catppuccin/foot
* input: don't map wheel events to BTN_{BACK,FORWARD}Daniel Eklöf2024-07-13-27/+59
| | | | | | | | | | | | | | | | | | | | BTN_BACK and BTN_FORWARD are separate buttons. The scroll wheel don't have any button mappings in libinput/wayland, so make up our own defines. This allows us to map them in mouse bindings. Also expose BTN_WHEEL_{LEFT,RIGHT}. These were already defined, and used, internally, to handle wheel tilt events. With this, they can also be used in mouse bindings. Finally, fix encoding used for BTN_{BACK,FORWARD} when sending mouse button events to the client application. Before this, they were mapped to buttons 4/5. But, button 4/5 are for the scroll wheel, and as mentioned above, BTN_{BACK,FORWARD} are not the same as scroll wheel "buttons". Closes #1763
* changelog: remove entry for change that hasn't yet been mergedDaniel Eklöf2024-07-13-2/+0
|
* render: hollow-cursor: use correct cursor colorDaniel Eklöf2024-07-13-1/+4
|
* render: cursor: use default fg/bg if cell fg/bg are the sameDaniel Eklöf2024-07-13-0/+14
| | | | | | | When deciding which colors to use for the cursor, and the cursor text and background colors are the same, use the default fg/bg instead. Closes #1761
* themes: add nvim-dark and nvim-light themesNicolas Kolling Ribas2024-07-09-0/+64
| | | | | Both based on the new "Nvim branded" default color scheme in Neovim 0.10.
* doc: foot.ini: line-height: add warning about runtime font size changesDaniel Eklöf2024-07-07-0/+6
|
* osc: extend damage-cells-by-color to default fg/bg as wellDaniel Eklöf2024-07-03-51/+102
| | | | | | | | | | | | | | | When changing part of the color palette, through either OSC-4, or OSC-10 and OSC-11 (and the corresponding reset OSCs: 104, 110 and 111), only dirty affected cells. We've always done this, but only for OSC-4. This patch breaks out that logic, and extends it to handle default fg/bg too. It also fixes a bug where cells with colored underlines were not dirtied if the underline was the only part of the cell that was affected by a OSC-4 change.
* Merge branch 'color-stack'Daniel Eklöf2024-07-03-68/+159
|\ | | | | | | Closes #856
| * csi: redraw margins after restoring the paletteDaniel Eklöf2024-07-03-0/+1
| |
| * osc: 10/11/12/17/19: don't apply overly much damageDaniel Eklöf2024-07-03-2/+5
| |
| * changelog: XTPUSHCOLORS, XTPOPCOLORS and XTREPORTCOLORSDaniel Eklöf2024-07-03-0/+4
| |
| * doc: foot-ctlseq: document XTPUSHCOLORS, XTPOPCOLORS and XTREPORTCOLORSDaniel Eklöf2024-07-03-0/+13
| |
| * csi: implement XTPUSHCOLORS+XTPOPCOLORS+XTREPORTCOLORSDaniel Eklöf2024-07-03-10/+105
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The documentation of these sequences are vague and lacking, as is often the case with XTerm invented control sequences. I've tried to replicate what XTerm does (as of xterm-392). The stack represents *stashed/stored* palettes. The currently active palette is *not* stored on the stack. The stack is dynamically allocated, and starts out with zero elements. Now, XTerm has a somewhat weird definition of "pushing" and "popping" in this context, and the documentation is somewhat misleading. What a push does is this: it stores the current palette to the stack at the specified slot. If the specified slot number (Pm) is 0, the slot used is the current slot index incremented by 1. The "current" slot index is then set to the specified slot (which is current slot + 1 if Pm == 0). Thus, "push" (i.e. when Pm == 0 is used) means store to the "next" slot. This is true even if the current slot index points into the middle of stack. Pop works in a similar way. The palette is restored from the specified slot index. If the specified slot number is 0, we use the current slot index. The "current" slot index is then set to the specified slot - 1 (current slot - 1 if Pm == 0). XTREPORTCOLORS return the current slot index, and the number of palettes stored on the stack, on the format CSI ? <slot index> ; <palette count> # Q When XTPUSHCOLORS grows the stack with more than one element (i.e. via a 'CSI N # P' sequence), make sure *all* new slots are initialized (to the current color palette). This avoids uninitialized slots, that could then be popped with XTPOPCOLORS. Closes #856
| * osc: merge OSC 10/11/12/17/19 handlingDaniel Eklöf2024-07-03-58/+33
|/ | | | | | | | | | 10/11/17/19 were already merged, so this patch just stops special casing 12 (cursor color). In preparation for XTPUSHCOLORS/XTPOPCOLORS, the cursor colors are moved from their own struct, into the 'colors' struct. Also fix a bug where OSC 17/19 queries returned OSC-11 data.
* csi: implement SGR 21, double underlinesDaniel Eklöf2024-07-03-1/+10
|
* render: fix "maybe-uninitialized" error in draw_styled_underline()Craig Barnes2024-07-03-2/+3
| | | | | | | | | | | | | | | | | | Reproducer: CFLAGS='-Og -g' meson setup --buildtype=debug bld ninja -C bld Error message: ../render.c: In function ‘draw_styled_underline’: ../render.c:490:19: error: ‘y_ofs’ may be used uninitialized [-Werror=maybe-uninitialized] 490 | const int top = y + y_ofs; | ^~~ ../render.c:405:9: note: ‘y_ofs’ was declared here 405 | int y_ofs; | ^~~~~
* doc: foot-ctlseq: add missing "E" to DECRQSS sequenceCraig Barnes2024-07-03-1/+1
| | | | This omission seems to have been a typo in commit add530e66d770954.
* Rename various uses of "curly" in the source code with "underline"Craig Barnes2024-07-01-169/+169
| | | | | Since "curly" could make it seem as if all underline styles are curled (to people unfamiliar with the codebase), whereas in reality only 1 is.
* dcs: DECRQSS: styled+colored underlinesDaniel Eklöf2024-07-01-12/+46
|
* render: cursor color: remove assertion that both cursor fg/bg be setDaniel Eklöf2024-07-01-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | Before this patch, we asserted both the cursor foreground, and background colors had been set. This is true in most cases; the config system enforces it. It is however possible to set only the cursor background color, while leaving the foreground (text) color unset: * Use a foot config that does *not* configure the cursor colors. This means foot will invert the default fg/bg colors when rendering the cursor. * Override the cursor color using an OSC-12 sequence. OSC-12 only sets the background color of the cursor, and there is no other OSC sequence to set the cursor's text color. To handle this, remove the assertion, and simply split the logic for the cursor backgound and foreground colors: * Use the configured background color if set (either through config or OSC-12), otherwise use the default foreground color. * Use the configured foreground color if set (through config), otherwise use the default background color.
* Merge branch 'curly-underlines'Daniel Eklöf2024-07-01-213/+911
|\ | | | | | | Closes #828
| * reaadme: add styled and colored underlines to the feature listDaniel Eklöf2024-06-27-0/+1
| |
| * grid: merge reflow_{uri,curly}_range_start(), and reflow_{uri,curly}_range_end()Daniel Eklöf2024-06-27-41/+47
| |
| * render: draw_styled_underline(): respect main.underline-thicknessDaniel Eklöf2024-06-27-4/+19
| | | | | | | | | | Also refactor a bit, and break out early to draw_underline() for legacy underlines.
| * render: underlines: improve the appearance of the 'dotted' styleDaniel Eklöf2024-06-27-6/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Try to make the 'dotted' style appear more even, and less like each cell is rendered separately (even though they are). Algorithm: Each dot is a square; it's sides are that of the font's line thickness. The spacing (gaps) between the dots is initially the same width as the dots themselves. This means the number of dots per cell is the cell width divided by the dots' length/width, divided by two. At this point, there may be "left-over" pixels.I.e. the widths of the dots and the gaps between them may not add up to the width of the cell. These pixels are evenly (as possible) across the gaps. There are still visual inaccuracies at small font sizes. This is impossible to fix without changing the way underlines are rendered, to render an entire line in one go. This is not something we want to do, since it'll make styled underlines, for a specific cell/character, look differently, depending on the surrounding context.
| * grid: refactor: replace {uri,curly}_range_append() with range_append()Daniel Eklöf2024-06-26-49/+70
| | | | | | | | | | Also add range_append_by_ref(), with replaces uri_range_append_no_strdup().
| * grid: row_range_put(): use correct type in call to range_delete()Daniel Eklöf2024-06-26-1/+1
| |
| * grid: refactor: remove union range_data_for_insertionDaniel Eklöf2024-06-26-51/+33
| | | | | | | | | | | | | | | | | | This union is identical to row_range_data, except the URI char pointer is const. Let's ignore that, and re-use row_range_data, casting the URI pointer when necessary. Also remove uri_range_insert() and curly_range_insert(), and use the generic version of range_insert() everywhere.
| * grid: grid_row_{uri,curly}_range_put(): share codeDaniel Eklöf2024-06-26-130/+114
| | | | | | | | | | | | | | | | grid_row_uri_range_put() and grid_row_curly_range_put() now share the same base logic. Range specific data is passed through a union, and range specific checks are done through switched functions.
| * foot.info: add 'Setulc' (set underline color) capabilityDaniel Eklöf2024-06-26-0/+1
| |
| * foot.info: add 'Su' (Styled Underlines) boolean capabilityDaniel Eklöf2024-06-26-0/+1
| |
| * csi: sgr_reset(): avoid using memset()Daniel Eklöf2024-06-26-3/+2
| | | | | | | | | | This _should_ be what the compiler does anyway (i.e. it _should_ replace the memset() with inline MOVs). But let's be sure.
| * render: underlines: minor perf-tweak: early break outDaniel Eklöf2024-06-26-0/+3
| | | | | | | | | | When looking up the extender underline range, break out early if we see that there can't possibly be any ranges matching the current column.
| * changelog: styled + colored underlinesDaniel Eklöf2024-06-26-1/+2
| |
| * doc: foot-ctlseq: add 58/59 (styled + colored underlines)Daniel Eklöf2024-06-26-3/+7
| |
| * term: performance: use a bitfield to track which ascii printer to useDaniel Eklöf2024-06-26-13/+63
| | | | | | | | | | | | | | | | | | | | | | The things affecting which ASCII printer we use have grown... Instead of checking everything inside term_update_ascii_printer(), use a bitfield. Anything affecting the printer used, must now set a bit in this bitfield. This makes term_update_ascii_printer() much faster, since all it needs to do is check if the bitfield is zero or not.
| * term: term_fill(): only set OSC-8 + styled hyperlinks when use_sgr_attrs is setDaniel Eklöf2024-06-26-3/+4
| |
| * terminal: term_fill(): fix osc8 erase bug + handle styled underlinesDaniel Eklöf2024-06-26-2/+16
| | | | | | | | | | | | | | | | Only clear OSC-8 hyperlinks at the target columns if we don't have an active OSC-8 URI. This corresponds to normal VT attributes; the currently active attributes are set, and all others are cleared. Handle styled underlines in the same way
| * render: resize: copy styled underlines to temporary gridDaniel Eklöf2024-06-26-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | When doing an interactive resize, we create a small grid copy of the current viewport, and then do a non-reflow resize. When the interactive resize is done, we do a proper reflow. This is for performance reasons. When creating the viewport copy, we also need to copy the styled underlines. Otherwise, styled underlines will be rendered as plain underlines *while resizing*.
| * grid: reflow: handle styled underlinesDaniel Eklöf2024-06-26-38/+128
| |
| * render: styled underlinesDaniel Eklöf2024-06-26-1/+118
| | | | | | | | | | | | | | | | This was originally contributed by @kraftwerk28 in https://codeberg.org/dnkl/foot/pulls/1099 Here, we re-use the rendering logic only, as attribute tracking has been completely rewritten.
| * csi: remove debug logDaniel Eklöf2024-06-26-1/+0
| |
| * foot.info: add smulx (styled underlines)Daniel Eklöf2024-06-26-0/+1
| |
| * csi: wip: styled underlinesDaniel Eklöf2024-06-26-66/+371
| | | | | | | | | | | | | | | | | | | | | | | | | | This is work in progress, and fairly untested. This adds initial tracking of styled underlines. Setting attributes seems to work (both color and underline style). Grid reflow has *not* been tested. When rendering, style is currently ignored (all styles are rendered as a plain, legacy underline). Color however, *is* applied.
| * grid: refactor: first step towards a more generic range handlingDaniel Eklöf2024-06-26-81/+135
|/
* Merge branch 'vs15-16'Daniel Eklöf2024-06-26-8/+930
|\ | | | | | | Closes #1742
| * scripts: generate-emoji-variation-sequences: don't assume single codepoint sequencesDaniel Eklöf2024-06-26-4/+11
| | | | | | | | | | | | | | | | | | | | Right now (Unicode 15.1), all valid variation sequences consist of a single Unicode codepoint (followed by either VS-15 or VS-16). Don't assume this is the case. We don't actually handle longer sequences. But now we at least catch such escapes, and error out.
| * scripts: generate-emoji-variation-sequences: compact the C structDaniel Eklöf2024-06-26-3/+3
| | | | | | | | | | | | | | | | | | | | Lookups in this table is not performance critical at all. Thus, let's compact it to bring down the binary size of foot. This brings the size of each entry down from 9 bytes to 6, bringing the size of the whole thing down from 1647 bytes to 1098 bytes, saving us 549 bytes.
| * vt: unittest: verify emoji_vs list is sortedDaniel Eklöf2024-06-25-0/+14
| |
| * scripts: generate-emoji-variation-sequences: don't assume input is sortedDaniel Eklöf2024-06-25-15/+16
| |
| * vt: only apply VS-15/16 to valid sequencesDaniel Eklöf2024-06-25-6/+903
| | | | | | | | | | | | | | | | | | | | At compile time, build a lookup table from the Unicode data file 'emoji-variation-sequences.txt'. At run-time, when we detect a VS-15/16 sequence, do a lookup in this table, and enforce the variation selector iff the sequence is valid. Closes #1742
| * vt: don't ignore VS-15 (text presentation)Daniel Eklöf2024-06-25-3/+6
|/ | | | | When we encounter either VS-15 or VS-16, set the grapheme width to 1 or 2 explicitly.
* doc: foot.ini: fix typosDaniel Eklöf2024-06-25-3/+3
|
* doc: foot.ini: document issues with fractional scaling and initial-window-size-*Daniel Eklöf2024-06-25-1/+12
| | | | | | Since most compositors don't report the correct scaling factor until *after* the window has been mapped, these options often do not work.
* shm: discard shm buffers with mis-matching alpha-settingDaniel Eklöf2024-06-24-1/+5
|
* input: don't reset the XKB compose state in keymap()Daniel Eklöf2024-06-22-27/+22
| | | | | | | | | | | | | When the compositor sends a new keymap, don't reset the XKB compose state. This is done by initializing the XKB context, along with the compose state, when binding the seat, instead of in keymap(). Then, in keymap(), simply stop destroying the old xkb state. Only destroy, and re-create the keymap state. Closes #1744
* input: implement wl_pointer::axis_value120()Daniel Eklöf2024-06-18-13/+69
| | | | | | | | | | | | | | | | | | | This implements high resolution mouse wheel scroll events. A "normal" scroll step corresponds to the value 120. Anything less than that is a partial scroll step. This event replaces axis_discrete(), when we bind wl_seat v8 (which we now do, when available). We calculate the number of degrees that is required to scroll a single line, based off of the scrollback.multiplier value. Each high-res event accumulates, until we have at least the number of degress required to scroll one, or more lines. The remaining degrees are kept, and added to in the next scroll event. Closes #1738
* osc: 52: treat OSC-52 replies as paste data (after all, they are)Daniel Eklöf2024-06-09-8/+34
| | | | | | | | | | | | | | | | | This fixes an issue where other data (such as replies to other requests) being interleaved with the OSC-52 reply. The patch piggy backs on the already existing mechanism for handling regular pastes, where other data is queued up until the paste is done. There's one corner case that won't work; if the user *just* did a normal paste (i.e. at virtually the same time the application requested OSC-52 data), the OSC-52 request will return an empty reply. Likewise, if there are multiple OSC-52 requests at the same time, only the first will return data. Closes #1734
* foot.ini: add missing option resize-by-cellsDaniel Eklöf2024-06-08-0/+1
| | | | Closes #1731
* config: codespell: varios -> variousDaniel Eklöf2024-06-08-1/+1
|
* ime: codespell: surroundin -> surroundingDaniel Eklöf2024-06-08-1/+1
|
* issue-template: let's see if we can disable the default templateDaniel Eklöf2024-06-08-1/+1
|
* meson: auto-detect execvpe on FreeBSDJan Beich2024-06-07-3/+8
| | | | https://github.com/freebsd/freebsd-src/commit/0667d0e0e365
* doc: foot.ini: document pixelsizeDaniel Eklöf2024-06-07-3/+9
| | | | | People are apparently too lazy to read fontconfig's documentation, and don't understand how to configure font sizes in foot.
* sixel: comment: document the P1 parameterDaniel Eklöf2024-05-22-1/+7
| | | | (and no, it's no longer unimplemented)
* issue-template: link "debug build", not just "build"Daniel Eklöf2024-05-22-2/+2
|
* issue-template: formatting; hopefully makes it easier to readDaniel Eklöf2024-05-22-5/+13
|
* issue-template: ask user to provide info on tmux, zellij, IMEs etcDaniel Eklöf2024-05-22-0/+5
|
* issue-template: add input-field for TERMDaniel Eklöf2024-05-22-0/+8
|
* shm: minor optimizationDaniel Eklöf2024-05-22-1/+1
| | | | | | | | | | | | | | | Don't retry memfd_create() without MFD_NOEXEC_SEAL is 0. The overall logic is this: * Try memfd_create() with MFD_NOEXEC_SEAL * If that fails (which it does, on older kernels), try without the flag If compiling against an older kernel, or on a system that doesn't support the noexec seal, MFD_NOEXEC_SEAL is 0. In this case, there's little point in retrying memfd_create a second time, with the exact same set of flags.
* changelog: wp-single-pixel-buffer-v1Daniel Eklöf2024-05-22-0/+3
|
* render: single-pixel: minor optimizationDaniel Eklöf2024-05-22-15/+32
| | | | | | | | | | | | | | Don't re-create the single-pixel buffer, unless necessary. The buffer itself doesn't have a size. That means we can re-use the buffer if the last frame's overlay style matches the current frame's style. What we *do not* know is whether the current frame's size is the same as the last frame's. This means we still have to set the viewport destination, and commit the surface.
* render: use single-pixel buffers for overlays, when possibleDaniel Eklöf2024-05-22-11/+92
| | | | | | | | | | | | | | | | | | | The unicode-mode, and flash overlays are single color buffers. This means we can use the single-pixel buffer protocol. It's undefined whether the compositor will release the buffer or not; to make things easier, simply destroy the buffer as soon as we've committed it. Note that since compositors don't necessarily release single-pixel buffers, we can't plug them into our own buffer interface. This means we can't use buffer pointers to check if we can re-use the previous buffer (i.e. we can skip comitting a new buffer), or if we have to create a new one. It's _almost_ enough to just check if the last overlay style is the same as the current one. Except that that doesn't take window resizes into account...
* issue-template: fix typoCraig Barnes2024-05-21-1/+1
|
* url-mode: disable IME mode while URL-mode is activeDaniel Eklöf2024-05-21-1/+18
| | | | | | | This prevents the IME from stealing "our" key-presses, and thus preventing the user from opening URLs. Closes #1718, hopefully.
* unicode-mode: move state from seat to termDaniel Eklöf2024-05-21-49/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes an issue where entering unicode-mode in one foot client, also enabled unicode-mode on other foot clients. Both visually (although glitchy), and in effect. The reason the state was originally in the seat objects, was to fully support multi-seat. That is, one seat/keyboard entering unicode-mode should not affect other seats/keyboards. The issue with this is that seat objects are Wayland global. Thus, in server mode, all seat objects are shared between the foot clients. There is a similarity with IME, which also keeps state in the seat. There's one big difference, however, and that is IME has Wayland native enter/leave events, that the compositor emits when windows are focused/unfocused. These events allow us to reset IME state. For our own Unicode mode, there is nothing similar. This patch moves the Unicode state from seats, to the terminal struct. This does mean that if one seat/keyboard enters Unicode mode, then *all* seats/keyboards will affect the unicode state. This potential downside is outweighed by the fact that different foot clients no longer affect each other. Closes #1717
* issue-template: feature: use yaml insteadDaniel Eklöf2024-05-21-19/+26
|
* issue-template: try to add another template, for feature requests.Daniel Eklöf2024-05-21-0/+19
|
* issue-template: it's validation*s*Daniel Eklöf2024-05-21-1/+1
|
* issue-template: try to fix link to INSTALL.md, attempt 3Daniel Eklöf2024-05-21-3/+4
|
* issue-template: try to fix link to INSTALL.md, attempt 2Daniel Eklöf2024-05-21-1/+1
|
* issue-template: try to fix link to INSTALL.mdDaniel Eklöf2024-05-21-1/+1
|
* forgejo: issue report templatesDaniel Eklöf2024-05-21-0/+74
|
* foot.ini: add commented out 'blink-rate'Daniel Eklöf2024-05-20-0/+1
|
* config: add cursor.blink-rate optionDaniel Eklöf2024-05-20-11/+37
| | | | | | The default is 500ms, which corresponds to the old, hardcoded default. Closes #1707
* themes: add onehalf-darkMariusz Bialonczyk2024-05-17-0/+39
|
* scripts: generate-builtin-terminfo: fix syntax errorArtturin2024-05-01-1/+1
|
* scripts: generate-builtin-terminfo: use \xNN for control charactersDaniel Eklöf2024-04-30-3/+3
| | | | | Instead of emitting raw control characters (for e.g. bel, cub1 and kbs), use \xNN C string escapes.
* dcs: xtgettcap: always reply with tigetstr(3) formatted "strings"Daniel Eklöf2024-04-27-21/+60
| | | | | | | | | | | That is, instead of sometimes replying with a "source" encoded string (where e.g. '\E' are returned just like that, and not as an actual ESC), always unescape all string values. This also includes \n \r \t \b \f \s, \^ \\ \ \:, as well as ^x-styled escapes. Closes #1701
* dcs: XTGETTCAP: handle empty requestDaniel Eklöf2024-04-20-0/+9
| | | | | | | If the XTGETTCAP request is empty (no capabilities in it), reply with an empty error reply. Closes #1694
* term: default to DPI 96, if the monitor's DPI is 0Daniel Eklöf2024-04-20-4/+13
| | | | | This can happen in virtualized environments, or when running a nested Wayland session.