aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
| * render: must now set alpha in bg color when calling render_osd()Daniel Eklöf2021-07-24-4/+4
| |
| * render: render_osd(): set clip region, use background alphaDaniel Eklöf2021-07-24-53/+61
| | | | | | | | | | | | | | | | | | Set clip region in render_osd(). This ensures we don’t step outside the pixman buffer when rendering the glyphs. Furthermore, don’t ignore the alpha channel in the background color. Move render_osd() to make it visible to the render_csd_*() functions.
| * render: color_dim(): retain alpha channelDaniel Eklöf2021-07-24-1/+2
|/
* readme: add OSC-9 to list of supported OSC sequencesDaniel Eklöf2021-07-24-0/+1
|
* osc: fix typo in LOG_DBG() messageCraig Barnes2021-07-24-1/+1
|
* readme: fix a typoKnut Anders Hatlen2021-07-23-1/+1
|
* pgo: add stub for search_selection_cancelled()Daniel Eklöf2021-07-23-0/+2
| | | | | | | Fixes PGO build failures caused by 251545203baa65364e491ddbe71ab3f8080bfe25 Closes #648
* Merge branch 'search-crash-when-selection-is-cancelled'Daniel Eklöf2021-07-22-0/+16
|\ | | | | | | Closes #644
| * search: redraw search box after selection has been cancelledDaniel Eklöf2021-07-22-0/+1
| |
| * search: reset match state when selection is cancelledDaniel Eklöf2021-07-22-0/+15
|/ | | | | | | | | | | | While we’re in scrollback search mode, the selection may be cancelled (for example, if the application is scrolling out the selected text). Trying to e.g. extend the search selection after this has happened triggered a crash. This fixes it by simply resetting the search match state when the selection is cancelled. Closes #644
* doc: ctlseq: improve description of OSC 52 responseDaniel Eklöf2021-07-22-2/+2
|
* Merge branch 'pgo-shm-fixes'Daniel Eklöf2021-07-22-0/+11
|\ | | | | | | Closes #642
| * pgo: fix PGO builds with clangDaniel Eklöf2021-07-22-0/+11
|/ | | | | | | | Add stubs for shm_chain_new(), shm_chain_free() and shm_unref(). This fixes ‘pgo’ linking failures in the ‘generate’ phase when doing a PGO build with clang. Closes #642
* Merge branch 'prevent-overflow-into-margin'Daniel Eklöf2021-07-20-1/+7
|\
| * render: prevent cells from overflowing into marginTimur Celik2021-07-20-1/+7
|/
* changelog: add new ‘unreleased’ sectionDaniel Eklöf2021-07-18-0/+11
|
* Merge branch 'releases/1.8'Daniel Eklöf2021-07-18-6/+5
|\
| * meson/pkgbuild: bump version to 1.8.21.8.2releases/1.8Daniel Eklöf2021-07-18-2/+2
| |
| * changelog: prepare for 1.8.2Daniel Eklöf2021-07-18-4/+3
| |
| * Merge branch 'master' into releases/1.8Daniel Eklöf2021-07-18-451/+1082
| |\ | |/ |/|
* | changelog: remove entries that are no longer relevantDaniel Eklöf2021-07-18-4/+0
| | | | | | | | | | The tweak.allow-overflowing-double-width-glyphs option have been superseded by tweak.overflowing-glyphs.
* | Merge branch 'csd-shared-shm-pool'Daniel Eklöf2021-07-18-56/+48
|\ \
| * | render: use a single backing SHM pool for CSD surface buffersDaniel Eklöf2021-07-18-56/+44
| | |
| * | shm: get_many(): allow “NULL” buffers - buffers where width or height is 0Daniel Eklöf2021-07-18-0/+4
|/ / | | | | | | | | | | | | | | When a zero-sized buffer is requested, simply return a NULL buffer, instead of crashing with a Wayland protocol error. This makes it easier to request many buffers, where some may be zero-sized, without having to pack the width/height and bufs arrays.
* | term: erase_scrollback(): destroy sixels that touch the scrollbackDaniel Eklöf2021-07-18-13/+55
| |
* | sixel: destroy(): don’t unref a NULL pixman imageDaniel Eklöf2021-07-18-2/+3
| |
* | Merge branch 'crash-when-selection-is-in-scrollback-and-scrollback-is-erased'Daniel Eklöf2021-07-18-23/+166
|\ \ | | | | | | | | | Closes #633
| * | changelog: crash when \E[3J was executed with a selection in the scrollbackDaniel Eklöf2021-07-18-0/+3
| | |
| * | term: add unit test for term_erase_scrollback()Daniel Eklöf2021-07-18-0/+97
| | |
| * | csi: erase scrollback: cancel selection if it touches the scrollbackDaniel Eklöf2021-07-18-23/+66
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This breaks out the scrollback erasing logic for \E[3J from csi.c, and moves it to the new function term_erase_scrollback(), and changes the logic to calculate the start and end row (absolute) numbers of the scrollback, and only iterate those, instead of iterating *all* rows, filtering out those that are on-screen. It also adds an intersection range check of the selection range, and cancels the selection if it touches any of the deleted scrollback rows. This fixes a crash when trying to render the next frame, since the selection now references rows that have been freed. Closes #633
* | Merge branch 'refactor-shm-buffer-management'Daniel Eklöf2021-07-18-277/+382
|\ \
| * | shm: chain_free: BUG() if there are buffers remaining after purgeDaniel Eklöf2021-07-17-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | There may be buffers left, if their destruction has been deferred. However, they should be on the 'deferred' list, not the chain's buffer list. If there are buffers left on the chain's list, that means someone forgot to call shm_unref().
| * | shm: get_buffer: purge mismatching buffers in first buffer iterationDaniel Eklöf2021-07-17-26/+6
| | | | | | | | | | | | | | | | | | There's no longer any need to defer purging of mismatching buffer (i.e. buffers whose width/height doesn't match the requested ones) to after the cache lookup loop.
| * | shm: refactor: move away from a single, global, buffer listDaniel Eklöf2021-07-17-164/+190
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Up until now, *all* buffers have been tracked in a single, global buffer list. We've used 'cookies' to separate buffers from different contexts (so that shm_get_buffer() doesn't try to re-use e.g. a search-box buffer for the main grid). This patch refactors this, and completely removes the global list. Instead of cookies, we now use 'chains'. A chain tracks both the properties to apply to newly created buffers (scrollable, number of pixman instances to instantiate etc), as well as the instantiated buffers themselves. This means there's strictly speaking not much use for shm_fini() anymore, since its up to the chain owner to call shm_chain_free(), which will also purge all buffers. However, since purging a buffer may be deferred, if the buffer is owned by the compositor at the time of the call to shm_purge() or shm_chain_free(), we still keep a global 'deferred' list, on to which deferred buffers are pushed. shm_fini() iterates this list and destroys the buffers _even_ if they are still owned by the compositor. This only happens at program termination, and not when destroying a terminal instance. I.e. closing a window in a “foot --server” does *not* trigger this. Each terminal instatiates a number of chains, and these chains are destroyed when the terminal instance is destroyed. Note that some buffers may be put on the deferred list, as mentioned above.
| * | shm: remove deferred buffers from main list immediatelyDaniel Eklöf2021-07-17-53/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When unref:ing a "busy" buffer, destruction is (still) deferred to the buffer release event. However, we now move the buffer off the buffer list immediately, and instead push it to a 'deferred' list. This prevents buffer re-use of buffers scheduled for destruction. It also means less buffers to iterate through when trying to find a re-usable buffer in shm_get_buffer(), since we no longer have to wade through a potentially long list of to-be-deleted buffers.
| * | shm: replace 'locked' attribute with a ref-counterDaniel Eklöf2021-07-17-53/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The initial ref-count is either 1 or 0, depending on whether the buffer is supposed to be released "immeidately" (meaning, as soon as the compositor releases it). Two new user facing functions have been added: shm_addref() and shm_unref(). Our renderer now uses these two functions instead of manually setting and clearing the 'locked' attribute. shm_unref() will decrement the ref-counter, and destroy the buffer when the counter reaches zero. Except if the buffer is currently "busy" (compositor owned), in which case destruction is deferred to the release event. The buffer is still removed from the list though.
| * | shm: we may exit with busy buffers remaining (seen on KDE)Daniel Eklöf2021-07-17-8/+22
| | |
| * | shm: move ‘size’ to the private buffer structDaniel Eklöf2021-07-17-18/+18
| | |
| * | shm: replace inclusion of terminal.h with a forward declaration of damageDaniel Eklöf2021-07-17-1/+1
| | | | | | | | | | | | It’s the only thing we “need” from terminal.h
| * | shm: rename buffer.mmapped to buffer.dataDaniel Eklöf2021-07-17-12/+14
| | |
| * | shm: split up buffer struct into internal/private and public partsDaniel Eklöf2021-07-17-99/+127
|/ /
* | Merge branch 'allow-bleeding-glyphs'Daniel Eklöf2021-07-17-75/+71
|\ \
| * | render: Allow cells to bleed into their neighborTimur Celik2021-07-17-75/+71
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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*.
* | Merge branch 'decsdm'Daniel Eklöf2021-07-16-5/+7
|\ \ | | | | | | | | | Closes #631
| * | csi: invert the meaning of DECSDMDaniel Eklöf2021-07-14-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There has been some confusion whether enabling DECSDM (private mode 80) enables or disables sixel scrolling. Foot currently enables scrolling when DECSDM is set, and this patch changes this, such that setting DECSDM now *disables* scrolling. The confusion is apparently due to a documentation error in the VT340 manual, as described in https://github.com/dankamongmen/notcurses/issues/1782#issuecomment-863603641. And that makes sense, in a way: the SDM in DECSDM stands for Sixel Display Mode. I.e. it stands to reason that enabling that disables scrolling. Anyway, this lead to https://github.com/hackerb9/lsix/issues/41, where it was eventually proven (by testing on a real VT340), that foot, and a large number of other terminals (including XTerm) has it wrong: https://github.com/hackerb9/lsix/issues/41#issuecomment-873269599.
* | | shm: codespellDaniel Eklöf2021-07-15-1/+1
| | |
* | | shm: auto-purge when we have multiple buffers eligible for re-useDaniel Eklöf2021-07-15-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It may happen that we end up with multiple non-busy, same-sized buffers for the same cookie (context), and thus eligible for re-use. Before this patch, we would keep all those buffers around. This is completely unnecessary. Under normal circumstances, we’ll either be re-using a single buffer, or swap between two. In the second case, the “other” buffer is always busy, and thus not eligible for re-use. So, if we _do_ detect multiple, re-usable buffers, pick the one with the lowest “age” (increasing the chance of applying damage tracking, instead of re-drawing everything), and mark the other one for purging.
* | | wayland: win_destroy: unmap URL labelsDaniel Eklöf2021-07-15-0/+6
| | |
* | | url-mode: use shm_get_many()Daniel Eklöf2021-07-15-17/+79
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If we have lots of URLs, we use up a *lot* of SHM buffers (and thus pools). Each and every one is a single mmap(), of at least 4K. Since all URL labels are created and destroyed at the same time, it makes sense to use a single pool for all buffers. To do this, we must now do two passes; first one to generate the actual string (label content), and to calculate the label sizes. Then we use this information to allocate all SHM buffers at once, from the same pool. Finally, we iterate the URLs again, this time to actually render them.
* | | shm: add shm_get_many() - allows buffers to share a single poolDaniel Eklöf2021-07-15-129/+274
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | shm_get_many() always returns new buffers (i.e. never old, cached ones). The newly allocated buffers are also marked for immediate purging, meaning they’ll be destroyed on the next call to either shm_get_buffer(), or shm_get_many(). Furthermore, we add a new attribute, ‘locked’, to the buffer struct. When auto purging buffers, look at this instead of comparing cookies. Buffer consumers are expected to set ‘locked’ while they hold a reference to it, and don’t want it destroyed behind their back.
* | | render: search: set clip regionDaniel Eklöf2021-07-15-0/+8
| | | | | | | | | | | | | | | Fixes crash when the search box has been reduced in height, due to limited window space.
* | | render: scrollback indicator: improve handling of very small window sizesDaniel Eklöf2021-07-15-10/+19
| | |
* | | render: margins: use correct background colorDaniel Eklöf2021-07-15-6/+3
| | | | | | | | | | | | | | | | | | * Sync actual color used, with how render_cell() selects the background color * Use color_dim_for_search(), not color_dim()
* | | render: track alpha directly, rather whether to use it or notDaniel Eklöf2021-07-15-6/+5
| | |
* | | shm: reset buffer pool FD when we close itDaniel Eklöf2021-07-14-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes an issue where we ended up "double closing" buffer FDs. In many cases (especially on compositors with SSDs) this was pretty rare. And even when it did happen, the FD was normally unused, and thus nothing bad happened. However, by quickly resizing the window while using CSDs, it was fairly easy to trigger this. We sometimes ended up closing the TIOCSWINCH timer FD while thinking it was a buffer FD, but most of the times we just ended up closing _another_ buffer’s pool FD, leading to an immediate disconnect by the compositor.
* | | render: tiocswinsz: don’t remove/close the fd passed as argumentDaniel Eklöf2021-07-14-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | There’s a chance the resize timeout FD was closed, and *reused*, after epoll() told us the FD is readable, but before our callback runs. Thus, closing the FD provided as an argument is dangerous, as it may refer to something completely different.
* | | Revert "render: don’t assume PIXMAN_a8r8g8b8 for color glyphs"Daniel Eklöf2021-07-14-2/+2
| | | | | | | | | | | | | | | | | | | | | This reverts commit 9b4796e996a6b524718591df8d8ea1ebe3b9bbbd. Sub-pixel anti-aliasing also uses 32-bit glyphs (but x8r8g8b8, instead of a8r8g8b8)...
* | | changelog: box-drawing fixes on big-endianDaniel Eklöf2021-07-14-0/+2
| | |
* | | box-drawing: big-endian support when setting bits manuallyDaniel Eklöf2021-07-14-6/+16
| | |
* | | render: don’t assume PIXMAN_a8r8g8b8 for color glyphsDaniel Eklöf2021-07-14-2/+2
|/ / | | | | | | We may want to use PIXMAN_b8g8r8a8 on big-endian in the future.
* | Merge branch 'crash-on-runaway-url'Daniel Eklöf2021-07-11-0/+7
|\ \
| * | url-mode: abort when running into un-allocated scrollback memoryDaniel Eklöf2021-07-11-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When tagging URL cells (in preparation for rendering URL mode), we loop the URL’s entire range, setting the `url` attribute of all cells, and dirtying the rows. It is possible to create URLs that are invalid, and wrap around the scrollback, even though the scrollback hasn’t yet been filled. For example, by starting an OSC-8 URL, moving the cursor, and then closing the OSC-8 URL. These URLs are invalid, but are still rendered just fine. “Fine” being relative - they will typically fill the entire screen. But at least that’s a very clear indication for the user that’s something is wrong. The problem is when we hit un-allocated scrollback rows. We didn’t check for NULL rows, and crashed. This has now been fixed.
* | | server: the terminal now purges SHM pixmaps on its ownDaniel Eklöf2021-07-11-7/+0
|/ /
* | Merge branch 'crash-in-url-mode-remove-duplicates'Daniel Eklöf2021-07-11-7/+14
|\ \ | | | | | | | | | Closes #627
| * | url-mode: fix crash when removing duplicate and/or overlapping URLsDaniel Eklöf2021-07-11-7/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removing overlaping and duplicated URLs is done by running two nested loops, that both iterate the same URL list. When a duplicate is found, one of the URLs is destroyed and removed from the list. Deleting and removing an item *is* safe, but only as long as _no other_ iterator has references to it. In this case, if we remove an item from e.g. the inner iterator, we’ll crash if the outer iterator’s *next* item is the item being removed. Closes #627
* | | shm: close pool FD if buffer doesn’t support SHM scrollingDaniel Eklöf2021-07-11-1/+6
|/ / | | | | | | | | | | | | | | | | The only reason to keep the pool FD open is if we’re going to SHM scroll the buffer; we need the FD for fallocate(FALLOC_FL_PUNCH_HOLE). In all other cases, there’s absolutely no need to keep the FD open. Thus, close it as soon as we’ve instantiated the buffer. This frees up FDs, and help keep foot from FD ulimit.
* | wayland: explicitly purge all SHM pixmaps when destroying windowDaniel Eklöf2021-07-11-0/+8
| | | | | | | | | | | | All SHM pixmap cookies depend on the terminal instance’s memory address. Thus, after a terminal instance has been destroyed, shm pixmaps that belonged to it will never be purged automatically.
* | wayland: purge CSD pixmaps when destroying the CSDsDaniel Eklöf2021-07-11-1/+6
| | | | | | | | | | | | CSDs aren’t typically toggled on and off. Thus, when disabled, immediately purge their corresponding pixmap buffers, to free up some memory, and release file descriptors.
* | url-mode: purge SHM pixmaps when destroying URLsDaniel Eklöf2021-07-11-0/+10
| | | | | | | | | | | | | | | | | | | | Unlike other surface types, the SHM cookie depends on the address of each URL instance. This means if we enable, disable, and then enable URL mode again (thus showing exactly the same URLs as the first time), the URLs will have new addresses, and thus the old SHM pixmaps will not get purged automatically. So, manually purge them when destroying the URLs.
* | Merge branch 'man-page-typo'Daniel Eklöf2021-07-08-1/+1
|\ \
| * | doc: fix typo in foot man pageBen Brown2021-07-08-1/+1
|/ /
* | Merge branch 'locked-title'Daniel Eklöf2021-07-07-0/+22
|\ \
| * | config: add locked-title=no|yesDaniel Eklöf2021-07-04-0/+22
|/ / | | | | | | Closes #386
* | term: rows printed to now defaults to having a hard linebreakDaniel Eklöf2021-07-03-2/+8
| | | | | | | | | | | | | | That is, instead of requiring a ‘\n’ to be printed, non-empty lines are now treated as having a hard linebreak by default. The linebreak is cleared on an explicit wrap.
* | doc: foot.ini.5: typo: relay-size-ms -> resize-delay-msDaniel Eklöf2021-07-02-2/+2
| |
* | render: require glyph count > 0 and cell-cols also for forced double-width PUAsDaniel Eklöf2021-07-02-4/+4
| |
* | allow-overflowing-double-width-glyphs: take glyph offset into accountDaniel Eklöf2021-07-02-3/+10
| | | | | | | | | | | | | | | | A narrow, but offset:ed glyph should still be considered double width. This patch also fixes a crash, when the maybe-double width glyph is in the last column. This is a regression.
* | foot.ini: mention Control+c in default "cancel" key bindingsCraig Barnes2021-07-02-2/+2
| | | | | | | | | | This should have been done as part of commit 6eb6668c3ccb1f8a5921d938bd41722b11c82a7e.
* | vt: add some unit tests for action_collect()Craig Barnes2021-07-02-0/+23
| |
* | changelog: s/from/inDaniel Eklöf2021-07-01-1/+1
| |
* | changelog: add new ‘unreleased’ sectionDaniel Eklöf2021-07-01-0/+11
| |
* | Merge branch 'releases/1.8'Daniel Eklöf2021-07-01-7/+4
|\|
| * meson/pkgbuild: bump version to 1.8.11.8.1Daniel Eklöf2021-07-01-2/+2
| |
| * changelog: prepare for 1.8.1Daniel Eklöf2021-07-01-5/+2
| |
| * Merge branch 'master' into releases/1.8Daniel Eklöf2021-07-01-193/+1509
| |\ | |/ |/|
* | changelog: move grapheme cluster width entry to ‘changed’, and rewrite itDaniel Eklöf2021-07-01-2/+7
| |
* | Merge branch 'max-grapheme-width-is-2'Daniel Eklöf2021-07-01-7/+46
|\ \
| * | config: rename at-most-2 (value for grapheme-width-method) to double-widthDaniel Eklöf2021-07-01-10/+10
| | |
| * | config: add tweak.grapheme-width-method=wcswidth|at-most-2Daniel Eklöf2021-07-01-5/+46
| | |
| * | vt: limit grapheme width to 2 cellsDaniel Eklöf2021-07-01-5/+3
|/ / | | | | | | | | | | | | | | | | | | | | | | All emoji graphemes are double-width. Foot doesn’t support non-latin scripts. Ergo, this should result in the Right Thing, even though we’re not doing it the Right Way. Note that we’re now breaking cursor synchronization with nearly all applications. But the way I see it, the applications need to be updated.
* | config: add unit test for config_clone()Daniel Eklöf2021-06-30-0/+21
| | | | | | | | | | | | | | | | We’re mainly interested in seeing that we don’t leak memory, or double free heap allocated data. Valgrind and/or gcc/clang sanitizers are best at this, hence the very few asserts in the test itself.
* | config: NOINLINE a couple of functions doing tll operationsDaniel Eklöf2021-06-30-4/+4
| |
* | Merge branch 'remove-unused-key-bindings'Daniel Eklöf2021-06-30-32/+134
|\ \ | | | | | | | | | Closes #614
| * | config: remove replaced/removed key bindings, instead of marking as ‘unused’Daniel Eklöf2021-06-30-32/+134
|/ / | | | | | | | | | | | | | | | | | | | | | | Instead of keeping removed/replaced key bindings in the key binding array (marked as ‘unused’), remove them, by compacting the array. The invariant is thus that there should be *no* entries in the key binding list with the `BIND_ACTION_NONE` for action. Add code to debug builds that verifies this, plus a unit test. Closes #614
* | render: don’t look at glyphs[0]->cols when determining if overflow should be allowedDaniel Eklöf2021-06-30-1/+1
| | | | | | | | | | Use ‘cell_cols’ instead, which is the number of cells we’ll actually be using.
* | terminfo: add Tc, setrgbf and setrgbb capabilitiesCraig Barnes2021-06-29-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These extensions are used by tmux and neovim, in order to make use of 24-bit colors without facing the problems that plague the `RGB` capability. This should allow 24-bit colors to work "out of the box" in tmux, without the usual workaround of adding: set-option -ga terminal-overrides ",foot*:Tc" ...to ~/.tmux.conf. See also: * https://github.com/kovidgoyal/kitty/commit/18fe2e8dfa34038aabd5c3a2fdb3624e2b27932a#commitcomment-31373962 * https://github.com/neovim/neovim/blob/f83c25942dd8b94ad5218ce78b9e6fb86d2f0358/runtime/doc/term.txt#L123-L139 * https://github.com/tmux/tmux/blob/b1a8c0fe022e99cffb0fb4f321740464f35bc6b9/CHANGES#L988-L989 Closes #615
* | input: ignore ‘unused’ URL key bindings when mapping bindings to current keymapDaniel Eklöf2021-06-28-2/+0
| | | | | | | | | | This is a temporary fix for #614. Long term fix is to remove the ‘replaced’ bindings from the array at config time.
* | term: destroy: free URLs before free:ing the gridsDaniel Eklöf2021-06-28-3/+5
| | | | | | | | | | Fixes use-after-free when destroying a terminal with “live” URLs (i.e. when URL mode is active).
* | log: add LOG_CLASS_NONE and use as initializer for log_levelCraig Barnes2021-06-26-93/+113
| | | | | | | | | | | | | | | | | | | | | | | | This means that logging will be completely disabled until log_init() has been called, which is useful to prevent log spam when running UNITTEST{} blocks in debug builds. Note that this doesn't change the default log level at runtime, which was already being set to LOG_CLASS_INFO in main.c and client.c. The new log level is also exposed to the command-line interface as `--log-level=none`, which allows disabling logging entirely.
* | vt: don’t reset utf8proc grapheme state when we’re not at a grapheme breakDaniel Eklöf2021-06-25-5/+12
| |