aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
* meson-pgo: realpath() on build dir tooDaniel Eklöf2021-09-12-1/+1
|
* meson-pgo: initial version of a meson wrapper script for PGO buildsDaniel Eklöf2021-09-12-0/+109
| | | | | | | | | | | | | | Usage: meson-pgo.sh auto|partial|full <source-dir> <build-dir> <meson-options> Note: build-dir must *not* exist before the script is run (but if it does, the script will tell you so, and exit). Supported compilers: gcc and clang The script does *not* add _any_ custom meson options, except configure -Db_pgo. Thus, you probably want to call it like this: meson-pgo.sh auto . /tmp/foot-pgo-build --buildtype=release -Db_lto=true
* Merge branch 'gnome-pointer-button-workaround'Daniel Eklöf2021-09-12-45/+63
|\ | | | | | | Closes #709
| * input: workaround GNOME issue with pointer button eventsDaniel Eklöf2021-09-12-45/+63
|/ | | | | | | | | | | | | | | | | Under certain circumstances, GNOME will send multiple pointer button press events, without any release or leave events in between. This trips up our button tracking. Workaround, by replacing the existing state for the pressed button with the new state. Previously, debug builds would assert (and thus crash), while release builds would have multiple states for the same button, causing (probably) issues like the title bar not being usable (as in, cannot be dragged, buttons not working etc). Hopefully closes #709
* Merge branch 'default-section-is-main'Daniel Eklöf2021-09-09-3/+4
|\
| * doc: Document that the default section can be reopened as [main]Arnavion2021-09-09-3/+4
|/
* term: reduce scope of variableDaniel Eklöf2021-09-05-3/+1
|
* sixel: call decsixel() directly, instead of going through sixel_put()Daniel Eklöf2021-09-05-2/+2
|
* sixel: avoid looking up color from palette for each sixelDaniel Eklöf2021-09-05-3/+4
| | | | | | Instead, do the palette lookup when we receive the DECGCI (i.e. when the palette entry is selected), and store the actual color value in our sixel struct.
* sixel: calculate default bg once, in initDaniel Eklöf2021-09-05-15/+11
| | | | | | | | We have all information we need to calculate the default background color in sixel_init(): * Whether the image have transparency or not * The current ANSI background color
* server: no need to clone the config to handle -N,--no-waitDaniel Eklöf2021-09-05-7/+2
|
* render: unref clip regionDaniel Eklöf2021-09-04-0/+1
|
* Merge branch 'check-font-is-monospace'Daniel Eklöf2021-09-03-0/+84
|\ | | | | | | Closes #704
| * config: codespell: setting has only two ‘t’Daniel Eklöf2021-08-31-1/+1
| |
| * changelog: check if primary font is monospacedDaniel Eklöf2021-08-31-0/+6
| |
| * server: verify primary font is monospacedDaniel Eklöf2021-08-31-0/+6
| | | | | | | | | | | | ... unless we’re re-using the main conf as-is, in which case we will already have done this (and the conf’s user-notification list will already contain a warning).
| * main: verify primary font is monospaced at startupDaniel Eklöf2021-08-31-0/+72
|/ | | | | | | | | | Load a couple of ASCII glyphs and check if their advance widths matches. If not, warn the user that the font is probably not monospaced. This can be disabled by setting tweak.font-monospace-warn=no. Closes #704.
* terminal: prefer the advance width of ‘M’ over that of a spaceDaniel Eklöf2021-08-31-3/+8
| | | | | | | | This makes some non-monospaced fonts more readable, allowing users to read errors and warnings printed in the window. Furthermore, fcft-3.0 will remove the space_advance member, so once we upgrade, we’ll have to rasterize a glyph ourselves anyway.
* Merge branch 'csi-cleanup'Craig Barnes2021-08-30-32/+13
|\
| * csi: various, minor code/formatting improvementsCraig Barnes2021-08-30-32/+13
| |
* | changelog: terminfo changesDaniel Eklöf2021-08-30-0/+11
| |
* | pkgbuild: fix terminfo package install locationDaniel Eklöf2021-08-30-2/+2
| |
* | pkgbuild: line-wrap meson configure command lineDaniel Eklöf2021-08-30-1/+5
| |
* | install: terminfo: pipe sed output to ticDaniel Eklöf2021-08-30-2/+2
| | | | | | | | Related to #700
* | install: document how to manually pre-process the terminfo source fileDaniel Eklöf2021-08-30-6/+3
| | | | | | | | Related to #700
* | pkgbuild: fix terminfo removalDaniel Eklöf2021-08-30-1/+1
| |
* | Merge branch 'terminfo-no-custom-install-location'Daniel Eklöf2021-08-30-118/+77
|\ \ | | | | | | | | | Closes #695
| * | meson: terminfo install location now defaults to $datadir/terminfoDaniel Eklöf2021-08-30-118/+77
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The meson command line option -Dcustom-terminfo-install-location has been changed in the following ways: * If unset, $datadir/terminfo is used, and TERMINFO is *not* exported * If set, that value (relative to $prefix) is used, and TERMINFO *is* exported. * The special value ‘no’ is removed. -Ddefault-terminfo now also changes the terminfo names generated when -Dterminfo=enabled. Furthermore, the documentation for the TERMINFO environment variable has been removed from the foot.1 and footclient.1 man pages (but as mentioned above, foot *will* still set it if -Dcustom-terminfo-install-location has been used). INSTALL.md has been updated to now recommend using ncurses’ terminfo definitions, if available. But also to document the other alternatives; installing the terminfo definitions in a custom location, or installing them with a diferent name. It also describes the general problem, and the disadvantages of each alternative (but without going into too much depth).
* | spawn: don’t error out if we fail to chdir()Daniel Eklöf2021-08-30-1/+7
| |
* | slave: log _which_ CWD we failed to change toDaniel Eklöf2021-08-30-1/+1
|/
* ci: codespell: ignore ‘doas’Daniel Eklöf2021-08-27-2/+2
|
* doc: how to pass TERMINFO through ‘doas’Daniel Eklöf2021-08-27-10/+24
| | | | See #692
* changelog: add new ‘unreleased’ sectionDaniel Eklöf2021-08-27-0/+11
|
* Merge branch 'releases/1.9'Daniel Eklöf2021-08-27-7/+6
|\
| * meson/pkgbuild: bump version to 1.9.01.9.0Daniel Eklöf2021-08-27-2/+2
| |
| * changelog: prepare for 1.9.0Daniel Eklöf2021-08-27-5/+4
|/
* doc: foot{,,client}: document TERMINFODaniel Eklöf2021-08-27-0/+46
| | | | Closes #691
* meson: run generate_version.sh in a C localeDaniel Eklöf2021-08-25-2/+3
| | | | | | | | Previously, only the date command inside the script was run with LC_TIME=C. But there’s no reason to be that conservative; we absolutely do not want _anything_ in that script to generate locale dependent output.
* Merge branch 'terminfo'Daniel Eklöf2021-08-19-28/+20
|\ | | | | | | Closes #687
| * slave: set TERMINFO instead of TERMINFO_DIRSDaniel Eklöf2021-08-18-28/+20
|/ | | | | | | | | This seems to be slightly better supported than TERMINFO_DIRS. It also simplifies our code, since it’s no longer an issue of whether to append or not - we just set TERMINFO, and ignore whatever it was set to before. Also closes #687
* changelog: cursor.blink now works in GNOMEDaniel Eklöf2021-08-18-0/+2
|
* Merge branch 'terminfo-dirs'Daniel Eklöf2021-08-17-81/+191
|\ | | | | | | Closes #671
| * terminfo: install to $datadir/foot/terminfo by default, append to TERMINFO_DIRSDaniel Eklöf2021-08-17-81/+191
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As of 2021-07-31, ncurses ships its own version of foot’s terminfo. Since: * It doesn’t have the non-standard Sync,Tc,setrgbf,setrgbb capabilities. * It doesn’t set hs,fsl,dsl (statusbar). * We want to be able to update our termminfo without waiting for an ncurses release. * Foot should be installable and usable on Linux systems that doesn’t have the latest ncurses. we still want to ship our own version. We can however not install it to the default terminfo location (e.g. /usr/share/terminfo), since it will collide with the ncurses provided files. Our options are to either rename our terminfo to something else, or to keep the name, but install our terminfo files somewhere else. The first option would be the easy one. However, I think it makes sense to use the same name. For example, a user that SSH’s into a remote system that does *not* have our own version installed, but *does* have the ncurses one, will gracefully fall back to that one, which is better than manually having to set e.g. TERM=xterm-256color. Now, if we want to use the same name, we need to install it somewhere else. But where? And how do we ensure our version is preferred over the ncurses one? I opted to $datadir/foot/terminfo (e.g. /usr/share/foot/terminfo) by default. It makes it namespaced to foot (i.e. we’re not introducing a new “standard” terminfo location), thus guaranteeing it wont collide with ncurses. To enable applications to find it, we export TERMINFO_DIRS. This is a list of *additional* directories to search for terminfo files. If it’s already defined, we *append* to it. The nice thing with this is, if there’s no terminfo in that location (e.g. when you SSH into a remote), the default terminfo location is *also* searched. But only *after* having searched through TERMINFO_DIRS. In short: our version is preferred, but the ncurses one (or an older version of our terminfo package!) will be used if ours cannot be found. To enable packagers full control over the new behavior, the existing meson command line options have been modified, and a new option added: -Dterminfo=disabled|enabled|auto: *build* and *install* the terminfo files. -Dcustom-terminfo-install-location=<path>: *where* the terminfo files are expected to be found. This *needs* to be set *even* if -Dterminfo=disabled. For example, if the packaging script builds and packages the terminfo files separate from the regular foot build. The path is *relative to $prefix*, and defaults to $datadir/foot/terminfo. This is the value that will be appended to TERMINFO_DIRS. Note that you can set it to ‘no’, in which case foot will *not* set/modify TERMINFO_DIRS. Only do this if you don’t intend to package foot’s terminfo files at all (i.e. you plan on using the ncurses ones only). -Ddefault-terminfo=foot. Allows overriding the default TERM value. This should only be changed if the target platform doesn’t support terminfo files. Closes #671
* term: check visual-focus, not kbd-focus when enabling/disabling cursor blinkDaniel Eklöf2021-08-17-2/+5
| | | | | | | | | | | | term_cursor_blink_update() is called when the visual focus changes state (i.e. when our top-level surface is activated de-activated). Checking keyboard focus worked on Sway, but on e.g. GNOME, the order in which keyboard focus and visual focus are updated is different, and we ended up either making the cursor invisible, or visible, but not blinking, when changing focus back to the window. Closes #686
* Merge branch 'selection-modify-only-use-one-cell-bit'Daniel Eklöf2021-08-16-27/+60
|\
| * selection: modify: no need to check for NULL before calling free()Daniel Eklöf2021-08-16-4/+1
| |
| * selection: modify: convert ‘keep_selection’ bitmask from uint64_t to uint8_tDaniel Eklöf2021-08-16-11/+11
| |
| * selection: modify: replace reset_context() macro with a functionDaniel Eklöf2021-08-16-9/+9
| |
| * selection: don’t require two cell attr bits for selection updatingDaniel Eklöf2021-08-16-27/+63
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When updating the selection (i.e when changing it - adding or removing cells to the selection), we need to do two things: * Unset the ‘selected’ bit on all cells that are no longer selected. * Set the ‘selected’ bit on all cells that *are* selected. Since it’s quite tricky to calculate the difference between the “old” and “new” selection, this is done by first un-selecting the old selection, and then selecting the new, updated selection. I.e. first we clear the ‘selected’ bit from *all* cells, and then we re-set it on those cells that are still selected. This process also dirties the cells, to make sure they are re-rendered (needed to reflect their new selected/un-selected status). To avoid dirtying *all* previously selected, and newly selected cells, we have used an algorithm that first runs a “pre-pass”, marking all cells that *will* be selected as such. The un-select pass would then skip (no dirty) cells that have been marked by the pre-pass. Finally, the select pass would only dirty cells that have *not* been marked by the pre-pass. In short, we only dirty cells whose selection state have *changed*. To do this, we used a second ‘selected’ bit in the cell attribute struct. Those bits are *scarce*. This patch implements an alternative algorithm, that frees up one of the two ‘selected’ bits. This is done by lazy allocating a bitmask for the entire grid. The pre-pass sets bits in the bitmask. Thus, after the pre-pass, the bitmask has set bits for all cells that *will* be selected. The un-select pass simply skips cells with a one-bit in the bitmask. Cells without a one-bit in the bitmask are dirtied, and their ‘selected’ bit is cleared. The select-pass doesn’t even have to look at the bitmask - if the cell already has its ‘selected’ bit set, it does nothing. Otherwise it sets it and dirties the cell. The bitmask is implemented as an array of arrays of 64-bit integers. Each outer element represents one row. These pointers are calloc():ed before starting the pre-pass. The pre-pass allocates the inner arrays on demand. The unselect pass is designed to handle both the complete absence of a bitmask, as well as row entries being NULL (both means the cell is *not* pre-marked, and will thus be dirtied).
* Merge branch 'tempus-themes'Daniel Eklöf2021-08-15-0/+448
|\
| * add tempus themesGadzhi Kharkharov2021-08-14-0/+448
| | | | | | | | | | | | | | | | rebuild with cursor colors rebuilt with commented selection colors rebuild with commented cursor colors
* | Merge branch 'terminfo-remove-keypad'Daniel Eklöf2021-08-14-21/+12
|\ \ | | | | | | | | | Closes #670
| * | changelog: mention keypad application mode keys being removedDaniel Eklöf2021-08-14-0/+4
| | |
| * | changelog: mention km/smm/rmm being removedDaniel Eklöf2021-08-14-0/+8
| | |
| * | terminfo: remove keypad key caps (for keypad application mode)Daniel Eklöf2021-08-14-18/+0
| | | | | | | | | | | | | | | The keypad application mode gated by private mode 1035. I.e. by default, there _is_ no keypad application mode in foot.
| * | terminfo: remove km/smm/rmmDaniel Eklöf2021-08-14-3/+0
|/ / | | | | | | | | | | | | | | By default, foot prefixes Alt-<key> combos with ESC, instead of setting the 8:th “meta” bit. In this mode, smm/rmm has no effect. This mode _can_ be disabled, by resetting private mode 1036. However, the terminfo should reflect the terminal’s *default* behavior.
* | Merge branch 'pt-or-px-scaling'Daniel Eklöf2021-08-14-46/+62
|\ \ | |/ |/| | | Closes #680
| * pt-or-px: heed the dpi-aware settingDaniel Eklöf2021-08-13-46/+62
|/ | | | | | | | | | | | | | | | | | | | | | | | Before this patch, pt-or-px values, like letter-spacing, were *always* scaled using the current DPI value. This is wrong; if the fonts are scaled using the output’s scaling factor, then so should all other point values. This also fixes an issue where e.g. letter-spacing would use one DPI value at startup, but then when increasing/decreasing or resetting the font size, would be re-calculated using a different DPI value, leading to completely different spacing. This happened when there were multiple monitors, with different DPI values, and foot guessed the initial DPI value wrong. Normally, foot would correct itself as soon as the window was mapped, and the “correct” DPI value known. But if the fonts were scaled using the scaling factor, it was possible that the font reload never happened. This patch also updates the thickness calculation (for LIGHT and HEAVY box drawing characters) to use the scaling factor when appropriate. Closes #680
* readme: change "32bpp" to "24bpp" in features listCraig Barnes2021-08-12-1/+1
| | | | | This is somewhat ambiguous, but in a terminal context "True Color" is usually synonymous with 24-bit RGB (as opposed to 32-bit RGBA).
* Merge branch 'sixel-left-most-column-overwritten'Daniel Eklöf2021-08-11-18/+70
|\
| * render: run the “overflowing glyphs” prepass *before* rendering sixelsDaniel Eklöf2021-08-11-18/+70
|/ | | | | | | | | | | | | | | | | | | | | | | This fixes an issue where the left-most column of a sixel was “overwritten” by the cell content. This patch also rewrites the prepass logic, to try to reduce the number of loads performed. The new logic loops each row from left to right, looking for dirty cells. When a dirty cell is found, we first scan backwards, until we find a non-overflowing cell. That cell is unaffected by the overflowing cell we’re currently dealing with. We can also stop as soon as we see a dirty cell, since that cell will already have been dealt with. Then, we scan forward, dirtying cells until we see a non-overflowing cell. That first non-overflowing cell is also dirtied, but after that we break. The last loop, that scans forward, advances the same cell pointer used in the outer loop.
* Merge branch 'uri-characters'Daniel Eklöf2021-08-11-41/+116
|\ | | | | | | Closes #654
| * changelog: url.uri-charactersDaniel Eklöf2021-08-09-0/+2
| |
| * config: add url.uri-charactersDaniel Eklöf2021-08-09-41/+114
|/ | | | | | | | | | | | This option specifies the characters allowed in the auto-detected URLs. Any character not in this set constitutes an URL delimiter, and will never be included in auto-detected URLs. This option does not affect OSC-8 URLs. Closes #654
* meson: require meson >= 0.54Daniel Eklöf2021-08-08-1/+1
| | | | We use meson.override_dependency, which was added in 0.54
* editorconfig: adjust max-line-length, down from 80 to 70Daniel Eklöf2021-08-07-1/+1
|
* Merge branch 'mouse-wheel-tilt'Daniel Eklöf2021-08-07-29/+55
|\
| * input: implement support for mouse wheel left/rightDaniel Eklöf2021-08-07-29/+55
|/ | | | | | | | | | | | | We now emit button 6/7 events (when the client application grabs the mouse). This buttons map to mouse wheel horizontal scroll events. Or, left/right tilting, if you like. Wayland report these as ‘axis’ events (just like regular scroll wheel events), and thus we need to translate those scroll events to button events. libinput does not define any mouse buttons for wheel tilts, so we add our own defitions. These are added last in the BTN_* range, just before the BTN_JOYSTICK events.
* Revert "terminfo: add ich1=\E[@"Daniel Eklöf2021-08-07-2/+0
| | | | | | This reverts commit 76fab8cf695b8e18e9f07d383189a34ca129e3ac. See https://codeberg.org/dnkl/foot/issues/668#issuecomment-246149
* input: codespell: follwing -> followingDaniel Eklöf2021-08-06-1/+1
|
* Merge branch 'gnome-drag-workaround'Daniel Eklöf2021-08-06-1/+47
|\
| * input: workaround GNOME messing up pointer leave/enter after moving windowDaniel Eklöf2021-08-06-1/+47
|/ | | | | | | | | | GNOME doesn’t send pointer enter after finishing a window move. In subsequent move operations, it is also possible to make it skip sending pointer leave when starting the move operations. This caused foot to assert in debug builds, and add the same button multiple times to the list of buttons currently being pressed.
* Merge branch 'terminfo-kmous-xm'Daniel Eklöf2021-08-06-7/+5
|\
| * terminfo: change kmous to \E[<, add XM+xm capabilitiesDaniel Eklöf2021-08-06-7/+5
|/ | | | | | | | | | | ncurses has had a bug where mouse support is completely disabled if the terminfo didn’t have kmous=\E[M, *or*, the terminfo *name* contained ‘xterm’. This appears to have been fixed. Thus, change kmous to \E[<, and set xm/XM accordingly. With this, ncurses application will use the SGR mouse reporting mode, instead of the legacy reporting mode.
* Merge branch 'terminfo-ich1'Daniel Eklöf2021-08-06-0/+2
|\
| * terminfo: add ich1=\E[@Daniel Eklöf2021-08-06-0/+2
|/
* Merge branch 'box-drawing-realign-sextants-and-wedges'Daniel Eklöf2021-08-06-47/+62
|\
| * box-drawing: fix compiler warningDaniel Eklöf2021-08-06-1/+1
| | | | | | | | | | | | | | | | | | | | ../../box-drawing.c: In function 'box_drawing': ../../box-drawing.c:2774:13: error: 'y1' may be used uninitialized in this function [-Werror=maybe-uninitialized] 2774 | int y0, y1; | ^~ ../../box-drawing.c:2774:9: error: 'y0' may be used uninitialized in this function [-Werror=maybe-uninitialized] 2774 | int y0, y1; | ^~
| * box-drawing: re-align sextants and wedgesDaniel Eklöf2021-08-06-47/+62
|/ | | | | Improve the visual quality of sextants (and wedges) when the cell height isn’t a multiple of three.
* Merge branch 'box-drawing-size-optimize'Daniel Eklöf2021-08-06-159/+140
|\
| * box-drawing: don’t inline functions called for multiple codepointsDaniel Eklöf2021-08-05-5/+5
| | | | | | | | | | In several cases, this expanded to multiple calls, and when inlined, resulted in much larger code size.
| * box-drawing: wedges: pre-load x_halfs[] and y_thirds[]Daniel Eklöf2021-08-05-64/+71
| | | | | | | | This reduces the number of loads in the rest of the function.
| * box-drawing: wedges: avoid floating point mathDaniel Eklöf2021-08-05-68/+66
| | | | | | | | | | Re-use the pre-calculated offsets used by the sextants. This is the correct thing to do since wedges *should* align with sextants.
| * box-drawing: pre-calculate sextant x,y offsetsDaniel Eklöf2021-08-05-6/+19
| | | | | | | | | | | | | | | | We’re using floating point math, as a way to ensure that sextant primitives overlap, rather than leaving empty spaces, or being uneven, when the cell width/height isn’t divisible with 2 (width) or 3 (height). This gets rid of all floating point math from the sextant drawing functions.
| * box-drawing: deal with quads in the same as sextantsDaniel Eklöf2021-08-05-79/+42
| | | | | | | | | | | | That is, encode which “pieces” make up each quad in a static array, and use a single function to draw all quads using the four primitives “upper left/right, lower left/right”.
| * box-drawing: don’t inline horizontal-one-eighth-block-NDaniel Eklöf2021-08-05-1/+1
| |
| * box-drawing: don’t inline light diagionalDaniel Eklöf2021-08-05-2/+2
|/
* Merge branch 'box-drawing-wedges'Daniel Eklöf2021-08-05-15/+356
|\ | | | | | | Closes #474
| * box-drawing: wedges: fix alignment of inverted wedgesDaniel Eklöf2021-08-05-33/+109
| | | | | | | | | | | | | | | | | | | | | | | | | | We render the inverted wedges by first rendering a non-inverted triangle, and then inverting it with PIXMAN_OP_OUT. In cases where truncating and round():ing the triangle points have different results, the final, inverted wedge ends up being unaligned with the corresponding sixel(s). This patch fixes that by handling the pre-inverted triangles specifically. I.e. we don’t re-use the same triangle coordinates as the corresponding non-inverted triangle.
| * box-drawing: wedges: don’t group similar cases togetherDaniel Eklöf2021-08-05-48/+100
| | | | | | | | | | Since they’re not exactly alike, we still need branches within each case. Better to split them up - one case per codepoint.
| * box-drawing: add U+1FB3C-U+1FB6F, U+1FB9A and U+1FB9BDaniel Eklöf2021-08-05-15/+228
|/ | | | | | These are the “wedges” from the Unicode 13 “Legacy Computing” symbols. Closes #474
* term: disable debug loggingDaniel Eklöf2021-08-05-1/+1
|
* Merge branch 'async-client-termination'Daniel Eklöf2021-08-03-66/+212
|\
| * term: send SIGTERM/SIGKILL to the entire process groupDaniel Eklöf2021-07-31-8/+10
| |
| * changelog: asynchronous client application terminationDaniel Eklöf2021-07-31-0/+6
| |
| * term: fix release builds when LOG_ENABLE_DBG=0Daniel Eklöf2021-07-31-1/+2
| |
| * term: consolidate shutdown related state into an anonymous structDaniel Eklöf2021-07-31-39/+48
| |
| * term: rename: slave_died() -> fdm_client_terminated()Daniel Eklöf2021-07-31-5/+6
| |
| * term: asynchronous client application terminationDaniel Eklöf2021-07-31-43/+170
|/ | | | | | | | | | | | | | | | | | When the foot window is closed, and we need to terminate the client application, do this in an asynchronous fashion: * Don’t do a blocking call to waitpid(), instead, rely on the reaper callback * Use a timer FD to implement the timeout before sending SIGKILL (instead of using SIGALRM). * Send SIGTERM immediately (we used to *just* close the PTY, and then wait 2 seconds before sending SIGTERM). * Raise the timeout from 2 seconds to 60 Full shutdown now depends on *two* asynchronous tasks - unmapping the window, and waiting for the client application to terminate. Only when *both* of these have completed do we proceed and call term_destroy(), and the user provided shutdown callback.
* Merge branch 'tilde-expansion-in-include'Daniel Eklöf2021-07-31-9/+28
|\ | | | | | | Closes #659