aboutsummaryrefslogtreecommitdiff
path: root/CHANGELOG.md (follow)
Commit message (Collapse)AuthorAgeLines
...
* | changelog: 'CSI 21 t' and 'OSC 176 ?' disabledDaniel Eklöf2025-01-07-0/+7
| |
* | changelog: utf8proc.h not foundDaniel Eklöf2025-01-04-0/+3
| |
* | changelog: add missing issue refDaniel Eklöf2025-01-03-1/+1
| |
* | changelog: add new 'unreleased' sectionDaniel Eklöf2025-01-03-0/+11
|/
* changelog: prepare for 1.20.1Daniel Eklöf2025-01-03-9/+3
|
* render: fix order we're checking custom codepointsDaniel Eklöf2025-01-03-0/+7
| | | | | | | Fixes a crash when trying to print a "Legacy Computing" symbol (U+1FB00-U+1FB9B). Closes #1901
* config: don't allow colors.flash-alpha to be 1.0Daniel Eklöf2025-01-02-0/+3
| | | | | | | | | | | | | | | | | | A compositor will not send a frame callback for our main window if it is fully occluded (for example, by a fully opaque overlay...). This causes the overlay to stuck. For regular buffers, it _should_ be enough to *not* hint the compositor it's opaque. But at least some compositor special cases single-pixel buffers, and actually look at their pixel value. Thus, we have two options: implement frame callback handling for the overlay sub-surface, or ensure we don't use a fully opaque surface. Since no overlays are fully opaque by default, and the flash surface is the only one that can be configured to be opaque (colors.flash-alpha), and since adding frame callback handling adds a lot of boilerplate code... let's go with the simpler solution of
* term: limit app-id to 2048 charactersDaniel Eklöf2025-01-02-0/+7
| | | | | | | | | | | | Unsure if the protocol imposes a limit (haven't found any documentation), or if the issue is in the libwayland implementation, or wlroots (triggers in at least sway+river). The issue is that setting a too long app-id causes the compositor (river at least) to peg the CPU at 100%, and stop sending e.g. frame callbacks to foot. Closes #1897
* changelog: add missing issue refDaniel Eklöf2025-01-01-0/+2
|
* changelog: add new 'unreleased' sectionDaniel Eklöf2025-01-01-0/+11
|
* changelog: prepare for 1.20.0Daniel Eklöf2025-01-01-5/+9
|
* kitty kbd: don't generate release events for plain Enter+Tab+BackspaceDaniel Eklöf2025-01-01-0/+4
| | | | | | | | | | | From the specification: The Enter, Tab and Backspace keys will not have release events unless Report all keys as escape codes is also set, so that the user can still type reset at a shell prompt when a program that sets this mode ends without resetting it. Closes #1892
* osc: add option to disable OSC-52, partially or fullyDaniel Eklöf2024-12-22-0/+3
| | | | Closes #1867
* selection: fix crash when tripple clicking in a region containing NUL charactersDaniel Eklöf2024-12-22-0/+1
| | | | | | | If a cell contains a NUL character, it was incorrectly treated as a quote, later triggering an assertion. Patch by Johannes Altmanninger
* term: set_app_id() + set_window_title(): only allow printable charactersDaniel Eklöf2024-12-17-0/+2
|
* box-drawings: implement octantsDaniel Eklöf2024-12-08-0/+3
|
* char32: use utf8proc_charwidth() instead of wcwidth(), when availableDaniel Eklöf2024-11-02-0/+5
| | | | | | | | | | It appears to be slightly more up-to-date with recent Unicode versions. In particular, it handles the new "Symbols for Legacy Computing Supplement" block, introduced in Unicode 16. Closes #1865
* osc: 9: ignore ConEmu/Windows Terminal sequencesDaniel Eklöf2024-11-02-0/+6
| | | | | OSC-9 sequences starting with "<number>;" are now ignored, as they are ConEmu sequences, and not iTerm notifications.
* unicode: update data files to 16.0Daniel Eklöf2024-10-31-0/+6
| | | | Yup, there's no _actual_ changes 🤷
* changelog: osc-9/777 crash when body is emptyDaniel Eklöf2024-10-31-0/+7
|
* changelog: add new 'unreleased' sectionDaniel Eklöf2024-10-23-0/+11
|
* changelog: prepare for 1.19.0Daniel Eklöf2024-10-23-5/+8
|
* uri: skip query/fragment parsing when dealing with file:// URIsDaniel Eklöf2024-10-23-0/+4
| | | | | | | Also, ignore invalid query/fragments (i.e. if the fragment comes before the query). Closes #1840
* config: add color.sixelN optionsDaniel Eklöf2024-10-23-0/+2
| | | | These options allows you to configure the default sixel color palette.
* render: sixels: update damage region when rendering sixelsDaniel Eklöf2024-10-05-0/+4
| | | | | | | | | | | | | | This fixes flickering when foot is forced to double-buffer (e.g when running under KDE, or smithay based compositors). Since the damage region isn't updated, the sixel images aren't included in the memcpy that is done to transfer the last frame's updated regions to the next frame. As a result, every other frame will have the sixels, while the others don't. Closes #1851
* changelog: #1715: "ghost" lines when selecting textDaniel Eklöf2024-09-21-0/+4
|
* render: xcursor_is_valid(): don't crash when there's no theme loadedDaniel Eklöf2024-09-21-0/+2
| | | | | | | | | | | | When trying to set a custom cursor shape, we first validate it. This is done by checking against known server-side names, and then trying to load the cursor from the client side cursor theme. But, if we're using server side names, there is no theme loaded, and foot crashed. Fix by checking if we have a theme loaded, and if not, fail the cursor shape name validation.
* changelog: remove escape sequences we've revertedDaniel Eklöf2024-09-13-4/+0
|
* toplevel-icon: implement OSC-1, CSI 20/21/22/23 tDaniel Eklöf2024-09-13-0/+5
| | | | | | | | | | | | | | * The toplevel icon is now set to the app-id, unless "overridden" by OSC-1 or OSC-0. * Implemented OSC-1 * OSC-0 extended to also set the icon * Implemented CSI 20 t - report window icon * Implemented CSI 21 t - report window title * Implemented CSI 22 ; 1 t - push window icon * Implemented CS 23 ; 1 t - pop window icon * Extended CSI 22/23 ; 0 t to also push/pop the icon * Verify app-id set by OSC-176 is valid UTF-8 * Verify icon set by OSC-0/1 is valid UTF-8
* changelog: xdg-toplevel-icon-v1Daniel Eklöf2024-09-13-0/+1
|
* render: resize(): don't overflow the number of scrollback linesDaniel Eklöf2024-09-09-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The config system allows setting the scrollback lines to 2**32-1. However, the total number of grid lines is the scrollback lines plus the window size, and then rounded *up* to the nearest power of two. Furthermore, the number of rows is represented with a plain 'int' throughout the code base. The largest positive integer that fits in an int is 2**31-1. That however, is not a power of two. The largest positive integer, that also is a power of two, that fits in an int is 2**30, or 1073741824. Ideally, we'd just cast the line count to a 64-bit integer, and call __builtin_clzl{,l}() on it, and then take the smallest value of that, or 2**30. But, for some reason, __builtin_clzl(), and __builtin_clzll() appears to ignore bits above 32, despite they being typed to long and long long. Bug? Instead, ensure we never call __builtin_clz() on anything larger than 2**30. Closes #1828
* desktop: rename to foot{,client,-server}.desktopDaniel Eklöf2024-09-08-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | That is, skip the reverse DNS naming scheme suggested by the .desktop specification, and directly match our app-ids ("foot", and "footclient"). This simplifies .desktop -> window instance mapping, allowing DEs to match the filenames directly, without having to look at the StartupWMClass key in the .desktop files. These are the original names of the .desktop files. There were renamed (to use the reverse DNS syntax) to please the flathub people, who *required* this scheme to accept the foot package. But, since: * We don't package foot ourselves * We don't go out of our way to support non-distro packaging schemes * Flathub still hasn't merged the foot PR (it's now 2 years old) * There are no know issues in any known DE that prevents a non-reverse DNS .desktop filename from working * There are plenty of other applications that doesn't use reverse DNS names (a very clear majority, in my case) Let's just revert back to the simpler naming scheme. Closes #1607
* sixel: default bg color is now taken from the sixel palette, not the ANSI bg colorDaniel Eklöf2024-09-05-0/+3
| | | | | | | | | | | | | | | | The wording in the original VT340 documentation is vague: Pixel positions specified as 0 are set to the current background color. What does that mean? We _thought_ it meant the current ANSI background color, as set with e.g. CSI 4x m. It's still all a bit vague, but seeing that we have separate palettes for text and graphic (should we?), it doesn't make sense to use the ANSI background color as the default sixel background color. So, use entry 0 from the sixel palette instead.
* notifications: BEL and OSC-777 now focuses the window on notification activationDaniel Eklöf2024-09-05-0/+8
| | | | | | | | | | | Or put more propertly; if the notification daemon, and the notification helper used by foot has been configured properly (i.e. they both support XDG activation tokens), notifications generated by BEL and OSC-777 will now raise/focus the window when the default action of the notification is activated - typically by clicking the notification. Closes #1822
* changelog: strikeout-thicknessDaniel Eklöf2024-08-26-0/+1
|
* changelog: mbsntoc32() failure checksDaniel Eklöf2024-08-20-0/+6
|
* changelog: resize-keep-gridDaniel Eklöf2024-08-20-0/+8
|
* changelog: add missing reference to #1787Daniel Eklöf2024-08-20-0/+2
|
* render: follow cursor.unfocused-style regardless of cursor.styletokyo4j2024-08-20-0/+5
| | | | | Before this commit, cursor.unfocused-style was effective only with cursor.style=block
* changelog: add new 'unreleased' sectionDaniel Eklöf2024-08-14-0/+11
|
* changelog: prepare for 1.18.1Daniel Eklöf2024-08-14-5/+6
|
* osc: regression: fix OSC-111 handling of alpha changesDaniel Eklöf2024-08-14-0/+7
| | | | | | | | | | | | | | When the background alpha changes from fully opaque, to transparent, or vice versa, we need to do more than just repaint the affected cells. For example, we need to create new surfaces with the correct pixel format. OSC-11 (set background color) already does this, but the same alpha checking logic was missing in OSC-111 (reset background color). Fixes #1801
* input: CSD buttons are now triggered when releasing the mouse buttonDaniel Eklöf2024-08-09-0/+5
| | | | | | | | | | | | This is how most UIs work. Note that we (at least on River) don't get any surface enter/leave events while a button is held. This means we can't detect if the user pressed the mouse button while on a CSD button, but then moves the mouse outside. Releasing the mouse button will still activate the CSD button. Closes #1787
* changelog: osc-99: sound supportDaniel Eklöf2024-08-04-0/+8
|
* changelog: add new 'unreleased' sectionDaniel Eklöf2024-08-02-0/+11
|
* changelog: prepare for 1.18.0Daniel Eklöf2024-08-02-4/+10
|
* changelog: more template parameters we've added to desktop-notificationsDaniel Eklöf2024-08-02-2/+3
|
* osc: kitty notifications: cleanup and update to latest version of specDaniel Eklöf2024-08-02-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Don't store a list of unfinished notifications. Use a single one. If the notification ID of the 'current' notification doesn't match the previous, unfinished one, the 'current' notification replaces the previous one, instead of updating it. * Update xstrjoin() to take an optional delimiter (for example ','), and use that when joining categories and 'alive IDs'. * Rename ${action-arg} to ${action-argument} * Update handling of the 'n' parameter (symbolic icon name); the spec allows it to be used multiple times, and the terminal is supposed to pick the first one it can resolve. Foot can't resolve icons at all, neither can 'notify-send' or 'fyi' (which is what foot typically executes to display a notification); it's the notification daemon that resolves icons. The spec _could_ be interpreted to mean the terminal should lookup .desktop files, and use the value of the 'Icon' key from the first matching .desktop files. But foot doesn't read .desktop files, and I don't intend to implement XDG directory scanning and parsing of .desktop files just to figure out which icon to use. Instead, use a simple heuristics; use the *shortest* symbolic names. The idea is pretty simple: plain icon names are typically shorter than .desktop file IDs.
* osc: kitty notifications: implement the 'close' requestDaniel Eklöf2024-07-25-0/+3
| | | | | | | | | | | | | | | | Add a new config option, desktop-notifications.close, defining what to execute to close a notification. It has a single template parameter, ${id}, that is expanded to the external notification ID foot may have picked up from the notification helper. notify-send does not support closing notifications, and it appears impossible to pass an *unsigned* integer as argument to gdbus. Hence no default value for the new 'close' option. Example: printf '\e]99;i=123;this is a notification\e\\' printf '\e]99;i=123:p=close;\e\\'
* notify: split up the ${action} template parameterDaniel Eklöf2024-07-23-2/+2
| | | | | | | | | Split it up into two, ${action-name} and ${action-label}. Dunstify, for example, has a different syntax compared to notify-send: notify-send: default=foobar dunstify: default,foobar
* notify: don't focus/report on notification dismissalDaniel Eklöf2024-07-23-1/+1
| | | | | | | | | | | | | | | | Only do it when the notification was activated. Here, activated means the 'click to activate' notification action was triggered. How do we tie everything together? First, we add a new template parameter, ${action}. It's intended to be used with e.g. notify-send's --action option. When the action is triggered, notify-send prints its name on stdout, on a separate line. Look for this in stdout. Only if we've seen it do we focus/report the notification.
* changelog: new desktop-notifications config sectionDaniel Eklöf2024-07-23-0/+11
|
* osc/notify: add support for OSC-99, kitty desktop notificationsDaniel Eklöf2024-07-23-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | 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-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/+3
| | | | | | | | | | | | | 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.
* log: respect the NO_COLOR environment variableDaniel Eklöf2024-07-18-0/+3
| | | | | | http://no-color.org/ Closes #1771
* themes: catppuccin: replace with updated flavorsabs3nt2024-07-18-1/+3
| | | | Pulled from https://github.com/catppuccin/foot
* input: don't map wheel events to BTN_{BACK,FORWARD}Daniel Eklöf2024-07-13-0/+12
| | | | | | | | | | | | | | | | | | | | 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-0/+3
|
* render: cursor: use default fg/bg if cell fg/bg are the sameDaniel Eklöf2024-07-13-0/+6
| | | | | | | 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
* changelog: XTPUSHCOLORS, XTPOPCOLORS and XTREPORTCOLORSDaniel Eklöf2024-07-03-0/+4
|
* csi: implement SGR 21, double underlinesDaniel Eklöf2024-07-03-0/+1
|
* render: cursor color: remove assertion that both cursor fg/bg be setDaniel Eklöf2024-07-01-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* changelog: styled + colored underlinesDaniel Eklöf2024-06-26-1/+2
|
* vt: only apply VS-15/16 to valid sequencesDaniel Eklöf2024-06-25-0/+2
| | | | | | | | | | 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-0/+2
| | | | | When we encounter either VS-15 or VS-16, set the grapheme width to 1 or 2 explicitly.
* shm: discard shm buffers with mis-matching alpha-settingDaniel Eklöf2024-06-24-0/+2
|
* input: don't reset the XKB compose state in keymap()Daniel Eklöf2024-06-22-0/+3
| | | | | | | | | | | | | 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-0/+2
| | | | | | | | | | | | | | | | | | | 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-0/+3
| | | | | | | | | | | | | | | | | 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
* changelog: wp-single-pixel-buffer-v1Daniel Eklöf2024-05-22-0/+3
|
* url-mode: disable IME mode while URL-mode is activeDaniel Eklöf2024-05-21-0/+2
| | | | | | | 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-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* config: add cursor.blink-rate optionDaniel Eklöf2024-05-20-0/+7
| | | | | | The default is 500ms, which corresponds to the old, hardcoded default. Closes #1707
* dcs: xtgettcap: always reply with tigetstr(3) formatted "strings"Daniel Eklöf2024-04-27-0/+15
| | | | | | | | | | | 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/+3
| | | | | | | 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-0/+6
| | | | | This can happen in virtualized environments, or when running a nested Wayland session.
* changelog: add new 'unreleased' sectionDaniel Eklöf2024-04-17-0/+11
|
* changelog: prepare for 1.17.2Daniel Eklöf2024-04-17-9/+3
|
* term: stash last known DPI, and use after a unmapped/mapped sequenceDaniel Eklöf2024-04-17-0/+3
| | | | | | | | | | | | | | | | | | A compositor may unmap, and then remap the window, for example when the window is minimized, or if the user switches workspace. With DPI aware rendering, we *need* to know on which output we're mapped, in order to use the correct DPI. This means the first frame we render, before being mapped, always guesses the DPI. In an unmap/map sequence, guessing the wrong DPI means the window will flicker. Fix by stashing the last used DPI value, and use that instead of guessing. This means the *only* time we _actually_ guess the DPI, is the very first frame, when starting up foot.
* sixel: don't allow pan/pad changes after sixel data has been emittedDaniel Eklöf2024-04-15-0/+3
| | | | | | | | | | | | | | | | | Changing pan/pad changes the sixel's aspect ratio. While I don't know for certain what a real VT340 would do, I suspect it would change the aspect ratio of all subsequent sixels, but not those already emitted. The way we implement sixels in foot, makes this behavior hard to implement. We currently don't resize the image properly if the aspect ratio is changed, but not the RA area. We have code that assumes all sixel lines have the same aspect ratio, etc. Since no "normal" applications change the aspect ratio in the middle of a sixel, simply disallow it, and print a warning. This also fixes a crash, when writing sixels after having modified the aspect ratio.
* sixel: also set 'alloc_height', when short-cutting a resize operationDaniel Eklöf2024-04-15-0/+3
| | | | | | | | | | In some cases, a sixel may be resized vertically, while still having a zero-width. In this case, the resize operations are short-cutted, and no actual allocations are done. However, we forgot to set 'alloc_height' when doing so. As a result, the trimming code (when the sixel is "done"), trimmed away the entire sixel.
* term: don't print outside grid when printing multi-column charactersDaniel Eklöf2024-04-15-0/+3
| | | | | | | | | | When auto-wrap is disabled, a multi-column character may be printed on a line that doesn't fit the entire character. That is, the "spacers" we print, as place holders in the columns after the first one, may reach outside the grid. We did (try to) check for this, but the check was off by one. Meaning, we could, in some cases, print outside the grid.
* osc: reject notifications with invalid UTF-8 stringsDaniel Eklöf2024-04-15-0/+4
|
* changelog: add a new 'unreleased' sectionDaniel Eklöf2024-04-11-0/+11
|
* changelog: prepare for 1.17.1Daniel Eklöf2024-04-11-6/+8
|
* config: add new key-binding 'quit', unbound by defaultDaniel Eklöf2024-04-11-0/+2
| | | | Closes #1475
* config: add cursor.unfocused-styleDaniel Eklöf2024-04-10-0/+7
| | | | | | | | | | | | | | | This option controls how we render the cursor when the terminal window is unfocused. Possible values are: * hollow: the default, and how we rendered the cursor before this patch. * unchanged: render the cursor exactly the same way as when the window is focused. * none: do not render any cursor at all Closes #1582
* dcs: DECRQSS: fix off-by-one when checking for space in the DCS bufferDaniel Eklöf2024-04-10-0/+2
|
* term: send SIGHUP before SIGTERM when shutting downDaniel Eklöf2024-04-05-0/+3
| | | | | | | | If we're the ones initiating shutdown, start by sending SIGHUP. Only if the client application does not terminate, send SIGTERM (and if it still refuses to terminate, send SIGKILL). Also reduce the timeout between the signals from 60s to 30s.
* term: don't shutdown terminal when PTY is closed, unless --pty was usedDaniel Eklöf2024-04-05-0/+5
| | | | | | | | | | | | | | | | | Unless --pty has been used, we do *not* want to shutdown the terminal when the PTY is closed by the client application; we want to wait for the client application to actually terminate. This was the behavior before the --pty patch. This was changed in the --pty patch, since then, we don't *have* a client application. That is, foot has not forked+exec:ed anything. The only way to trigger a shutdown (from the client side) is to close the PTY. This patch restores the old behavior, when --pty is *not* used. Closes #1666
* log: fix syslog not respecting the configured log levelDaniel Eklöf2024-04-05-0/+4
|
* changelog: add new 'unreleased' sectionDaniel Eklöf2024-04-02-0/+11
|
* changelog: prepare for 1.17.0Daniel Eklöf2024-04-02-5/+20
|
* changelog: move DECRQM for private mode 67 from "added" to "changed"Daniel Eklöf2024-04-01-2/+2
|
* terminfo: tighten up the rv/xr regular expressionsDaniel Eklöf2024-03-29-0/+2
|
* terminfo: add 'nel' capabilityDaniel Eklöf2024-03-29-0/+1
|
* terminfo: add fe/fd (focus enable/disable)Daniel Eklöf2024-03-29-0/+5
| | | | | | These are new capabilities, recently added to ncurses. Applications are supposed to use these, instead of XM (to enable focus events). So, remove "CSI ? 1004h" from XM.
* sixel: trim trailing, fully transparent sixel rowsDaniel Eklöf2024-03-18-0/+2
| | | | See https://github.com/hpjansson/chafa/issues/192