aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
* Merge branch 'no-underlines-below-cell'Daniel Eklöf2021-05-12-2/+10
|\ | | | | | | Closes #503
| * render: force underlines to be visibleDaniel Eklöf2021-05-12-2/+10
|/ | | | | | | | | | | | | | | In some cases, the underline position (typically provided by the font, mind you), end up below the cell, making it visible. Note that below the cell here means below the line. I.e. the font provided underline position is below the font provided line height... Oh well. Doing this in foot rather than fcft, since other applications typically don’t have to clip the rendered text. Closes #503
* Merge branch 'remove-plasma-quirk'Daniel Eklöf2021-05-12-32/+4
|\
| * quirk: remove plasma/kwin quirkDaniel Eklöf2021-05-12-32/+4
|/ | | | | | Older version of Plasma/KWin had an issue where buffer damage recorded before the buffer was attached were ignored. This appears to have been fixed now.
* Merge branch 'double-buffering'Daniel Eklöf2021-05-12-94/+273
|\ | | | | | | Closes #478
| * changelog: improved performance when double bufferingDaniel Eklöf2021-05-12-0/+3
| |
| * render: always do a full repaint if last buffer’s dimension doesn’t matchDaniel Eklöf2021-05-12-8/+9
| |
| * render: add margins to buffer’s dirty region when rendering marginsDaniel Eklöf2021-05-12-0/+12
| |
| * shm: clear buffer’s dirty region before returning a cached bufferDaniel Eklöf2021-05-12-2/+1
| | | | | | | | A non-busy buffer should always have an empty dirty region
| * shm: set ‘age’ in newly allocated buffers to something largeDaniel Eklöf2021-05-12-1/+1
| | | | | | | | This ensures we don’t try to do a partial update of fresh buffer.
| * shm: free scroll damage before returning cached bufferDaniel Eklöf2021-05-12-0/+2
| |
| * render: warn if we’re forced to double buffer at least 5 timesDaniel Eklöf2021-05-12-1/+8
| |
| * render: code cleanup, log double buffering timeDaniel Eklöf2021-05-12-182/+189
| | | | | | | | | | | | | | | | | | | | | | * Break out cursor cell dirtying to separate functions * Break out handling of double buffering * Handle buffers with age > 1 (we’re swapping between more than 2 buffers) * Detect full screen repaints, and skip re-applying old frame’s damage * Use an allocated array insted of a tll list for old frame’s scroll damage * When logging frame rendering time, including the amount used for double buffering.
| * render: subtract current frame’s damage when there’s no scroll damageDaniel Eklöf2021-05-12-10/+6
| | | | | | | | | | | | | | | | | | | | | | When re-applying the previous frame’s damage (due to us being forced to double buffer), subtract the current frame’s damage from the region-to-copy when there’s no scroll damage on the current frame. When the current frame doesn’t have any scroll damage, the current frame’s damage is in the same coordinate system as the previous frame’s damage, and we can safely remove it from the region we copy from.
| * render: wip: re-apply last frame’s damage when forced to double bufferDaniel Eklöf2021-05-12-12/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we are forced to swap between two buffers, re-apply the old frame’s damage to the current buffer, before applying the current frame’s damage. First, while applying this frame’s scroll damage, copy it to the buffer’s scroll damage list (so that we can access it via term->render.last_buf). Also, when iterating and rendering the grid, build a pixman region of the damaged regions. This is currently done on a per-row basis. This is also stored in the buffer. Now, when being forced to double buffer, first iterate the old buffer’s damage, and re-apply it to the current buffer. Then, composite the old buffer on top of the current buffer, using the old frame’s damage region as clip region. This effectively copies everything that was rendered to the last frame. Remember, this is on a per-row basis. Then we go on and render the frame as usual. Note that it would be _really_ nice if we could subtract the current frame’s damage region from the clip region (no point in copying areas we’re going to overwrite anyway). Unfortunately, that’s harder than it looks; the current frame’s damage region is only valid *after* this frame’s scroll damage have been applied, while the last frame’s damage region is only valid *before* it’s been applied. Translating one to the other isn’t easy, since scroll damage isn’t just about counting lines - there may be multiple scroll damage records, each with its own scrolling region. This creates very complex scenarios.
| * shm: add damage tracking to bufferDaniel Eklöf2021-05-12-0/+9
| |
| * shm: track busy buffers’ age, and add compile-time option to force double bufferingDaniel Eklöf2021-05-12-11/+34
|/ | | | | | | | | By default, age all matching buffers that are busy (i.e. in use by the compositor). This allows us to detect whether we can apply the current frame’s damage directly, or if we need to prepare the buffer first (e.g. copy old buffer, or re-apply last frame’s damage etc).
* wayland: codespell: pre-empt -> preemptDaniel Eklöf2021-05-11-1/+1
|
* wayland: add comment describing the configure preempt workaroundDaniel Eklöf2021-05-10-1/+26
|
* Merge branch 'sixel-assertion'Daniel Eklöf2021-05-08-3/+19
|\ | | | | | | Closes #494
| * changelog: sixel assertion hit when a sixel fills the scrollbackDaniel Eklöf2021-05-08-0/+2
| |
| * sixel: don’t emit sixels that will end up covering more than the entire scrollbackDaniel Eklöf2021-05-08-2/+16
| | | | | | | | | | | | | | This limit can be reached by the sixel alone, or the sixel + the final newline. Closes #494
| * sixel: fix assertion: image is allowed to cover the entire scrollbackDaniel Eklöf2021-05-08-1/+1
|/
* Merge branch 'osc8-mem-leak'Daniel Eklöf2021-05-08-5/+10
|\ | | | | | | Closes #495
| * term: reset: combine memset+initializers of vt structDaniel Eklöf2021-05-08-3/+4
| |
| * term: reset: fix reset of the VT structDaniel Eklöf2021-05-08-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | 1. Free buffers and strings 2. memset() the vt struct 3. re-initialize members that must not be zero We _could_ replace the memset() with explicit zeroing of all the members. It’s just that there’s a lot of arrays, so this is much easier. Closes #495
| * term: osc8-open: assert URI in VT struct is NULLDaniel Eklöf2021-05-08-0/+2
|/
* Merge branch 'simplify-parse_section_colors'Craig Barnes2021-05-08-16/+14
|\
| * config: simplify parse_section_colors()Craig Barnes2021-05-08-16/+14
| |
* | config: simplify parsing of "scaling-filter" values slightlyCraig Barnes2021-05-08-12/+9
|/
* Merge branch 'config-code-size'Daniel Eklöf2021-05-08-106/+186
|\
| * config: avoid tll() code expansion when generating default bindingsDaniel Eklöf2021-05-07-29/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | tll_push_back() is a macro that results in quite a lot of instructions. Expanding this macro explicitly in many places thus causes code explosion. This is what happened in when we generate the default key/mouse bindings. Fix by calling tll_push_back() in a no-inline function. Reduces code size with ~4-5K
| * config: don’t inline str_to_*() functionsDaniel Eklöf2021-05-07-8/+8
| |
| * config: implement LOG_AND_NOTIFY_* macros in terms of no-inline functionsDaniel Eklöf2021-05-07-35/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reduces code size by quite a lot: From: section size addr .text 37857 0 ... Total 45169 To: section size addr .text 31681 0 ... Total 38993 LTO release build goes from 500K -> 492K
| * xmalloc: export xvasprintf()Daniel Eklöf2021-05-07-1/+3
| |
| * log: add va_list versions of log_* functionsDaniel Eklöf2021-05-07-33/+73
| |
* | Merge branch 'color-table-config'Daniel Eklöf2021-05-08-4/+28
|\ \ | |/ |/| | | Closes #489
| * configure full color palette in foot.iniRyan Farley2021-05-08-4/+28
|/ | | | | Allow the use of numeric keys in [colors] to configure the full set of 256 colors in the palette. Fixes #489
* Merge branch 'bell-enhancement'Daniel Eklöf2021-05-07-54/+125
|\
| * consistent booleans in config, reset legacy bellRyan Farley2021-05-07-6/+12
| |
| * update changelogRyan Farley2021-05-07-0/+6
| |
| * clearly mark bell as a sectionRyan Farley2021-05-07-1/+1
| |
| * style, consistent bool names, deprecate old configRyan Farley2021-05-07-6/+32
| |
| * enhanced bell configurationRyan Farley2021-05-07-63/+96
| | | | | | | | | | | | | | | | | | | | Add a separate section for bell configuration, with a bell-specific command option and a setting to allow that command to run without regard to keyboard focus (for those of us who enjoy being beeped at at all times, for example). The actions are also no longer mutually exclusive; this is primarily anticipating urgency support which cannot be replicated outside the process (in server mode anyway) and would thus be complementary to any notification or arbitrary command.
* | Merge branch 'bump-fcft-to-2-4-0'Daniel Eklöf2021-05-07-1/+3
|\ \ | |/ |/|
| * meson: require fcft >= 2.4Daniel Eklöf2021-05-07-1/+3
|/
* Merge branch 'fix-color-cube'Daniel Eklöf2021-05-06-3/+10
|\ | | | | | | Closes #479
| * config: fix color cube generationDaniel Eklöf2021-05-06-3/+10
|/ | | | Closes #479
* doc: foot.ini: update max-shm-pool-size-mb sectionDaniel Eklöf2021-05-05-7/+10
| | | | | | | * less highlighting * it’s ‘virtual *address space*’ * mention it’s only supported on Linux * mention it’s only supported on 64-bit archs (but not necessarily x86_64)
* Merge branch 'more-unicode-13-box-drawings'Daniel Eklöf2021-05-04-6/+260
|\ | | | | | | Related to #471
| * box-drawing: add Unicode 13 U+1FB70 - U+1FB8BDaniel Eklöf2021-05-04-6/+260
|/ | | | Part of #471
* Merge branch 'bg-alpha-on-default-bg-only'Daniel Eklöf2021-05-04-4/+8
|\
| * render: only apply alpha when we’re using the default bg for backgroundDaniel Eklöf2021-05-04-4/+8
|/ | | | | | | | In all other cases, alpha is disabled. This includes: * Palette- or RGB-colors matching the default background color * When any kind of reverse video is enabled (e.g. DECSCNM, or ANSI reverse)
* Merge branch 'missing-xkb-build-dependency'Daniel Eklöf2021-05-04-3/+3
|\
| * meson: add ‘xkb’ as a dependency to vtlib, pgolib and pgoDaniel Eklöf2021-05-01-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All of these include wayland.h (either directly, or indirectly), which pulls in xkbcommon.h. Reported by swayyyy on IRC: FAILED: libvtlib.a.p/dcs.c.o In file included from ../../terminal.h:19, from ../../dcs.h:4, from ../../dcs.c:1: ../../wayland.h:9:10: fatal error: xkbcommon/xkbcommon.h: No such file or directory 9 | #include <xkbcommon/xkbcommon.h> | ^
* | Merge branch 'custom-exit-code'Daniel Eklöf2021-05-04-21/+57
|\ \ | | | | | | | | | Closes #466
| * | doc: foot.1 footclient.1: document exit statusDaniel Eklöf2021-05-04-3/+24
| | |
| * | main/client: change exit codeDaniel Eklöf2021-05-04-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | * foot exits with -26/230 * footclient exits with -36/220 This is to give each application a range of exit codes. Currently unused, but we may want to change this in the future.
| * | foot/footclient: use a custom exit code when foot/footclient fail to runDaniel Eklöf2021-05-04-18/+33
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Normally, foot and footclient uses the exit code from the client application (i.e. the shell). However, foot (or footclient) itself may fail to run; if run outside of a Wayland session, or no fonts are installed, or the client application/shell cannot be found (“foot lsdjfldsjf”) etc. Up until now, there has been no way to differentiate these kind of failures from the client application exiting with code 1. This patch changes foot’s failure exit code to -27/229, and footclient’s to -28/228. Note that footclient will exit with foot’s -27/229 if footclient ran successfully, but the foot server failed to instantiate a new window. Closes #466.
* | Merge branch 'beam-thickness'Daniel Eklöf2021-05-04-29/+57
|\ \ | | | | | | | | | Closes #464
| * | config: add ‘beam-thickness’ optionDaniel Eklöf2021-04-30-29/+57
| |/ | | | | | | | | | | | | | | | | | | | | * Rename cursor.style value ‘bar’ to ‘beam’. ‘bar’ remains recognized, but should eventually be deprecated and then removed. * Add ‘cursor.beam-thickness’ option, a pt-or-px value specifying the thickness of the beam cursor. Defaults to 1.5pt. * Rename (and export) pt_or_px_as_pixels() to term_pt_or_px_as_pixels() * Change term_pt_or_px_as_pixels() to round point values instead of truncating them.
* | Merge branch 'add-truecolor-to-feature-list'Daniel Eklöf2021-05-02-0/+1
|\ \ | |/ |/|
| * Add TrueColors support to Readmelord2021-05-02-0/+1
|/
* Merge branch 'bsu-esu-logging'Daniel Eklöf2021-04-26-4/+6
|\
| * dcs: only log debug warnings in bsu() and esu() for unhandled paramsCraig Barnes2021-04-25-4/+6
|/
* Merge branch 'DECSET-2026'Daniel Eklöf2021-04-25-0/+20
|\ | | | | | | Closes #459
| * csi: add support for DECSET 2026, as an alternative to BSU/ESU sequencesCraig Barnes2021-04-25-0/+20
|/ | | | See: https://gitlab.freedesktop.org/terminal-wg/specifications/-/merge_requests/2#note_847720
* Merge branch 'modify-bg-color-when-highlighted-text-has-same-fg-bg'Daniel Eklöf2021-04-24-0/+9
|\ | | | | | | Closes #455
| * render: modify background color for highlighted text when fg == bgDaniel Eklöf2021-04-24-0/+9
|/ | | | | | | | When rendering a selected/highlighted cell where the foreground and background colors are the same, invert the background color to make the selected text legible. Closes #455
* Merge branch 'reveal-concealed-text-when-highlighted'Daniel Eklöf2021-04-24-1/+5
|\
| * render: do render concealed text when it’s highlightedDaniel Eklöf2021-04-23-1/+5
|/
* pkgbuild: run ‘ninja test’ in the PGO generate phaseDaniel Eklöf2021-04-22-0/+5
| | | | | | This is needed when fcft/tllist are built as subprojects, since then we must ensure their unit tests are executed, or we’ll get “profile count data file not found” errors.
* Merge branch 'generate-alt-random-writes-fixes'Daniel Eklöf2021-04-22-13/+48
|\
| * changelog: generate-alt-random-writes.py --sixel fixesDaniel Eklöf2021-04-22-0/+10
| |
| * generate-alt-random: don’t run TIOCGWINSZ ioctl if --cols and --rows were usedDaniel Eklöf2021-04-22-24/+25
| |
| * generate-alt-random: do ioctl(TIOCGWINSZ) on /dev/tty, not stdoutDaniel Eklöf2021-04-22-5/+6
| |
| * generate-alt-random: wait for SIGWINCH if width/height is 0Daniel Eklöf2021-04-22-6/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | If width/height (that is, the *pixel* values) are 0, that means we are early (or that foot is slow) - we’ve managed to reach this point before the foot window has been mapped. Or rather, before foot has loaded the primary fonts and calculated the cell geometry. But that, and the initial mapping of the window is tightly coupled. To handle this case, detect when width or height is 0, an then wait for SIGWINCH before trying again.
| * generate-alt-random: assert that lines/cols/width/height are > 0Daniel Eklöf2021-04-22-0/+5
| |
| * generate-alt-random: use {width,height} + 1 in randrange()Daniel Eklöf2021-04-22-1/+1
| | | | | | | | | | | | | | When randomizing the sixel width and height, use width/height + 1 in the call to randrange(). This ensures the width/height is never 0, and that the maximum width/height is half the window size, not slightly less than that.
* | readme: s/if/isDaniel Eklöf2021-04-22-1/+1
|/
* Merge branch 'releases/1.7'Daniel Eklöf2021-04-18-5/+14
|\
| * meson/pkgbuild: bump version to 1.7.21.7.2releases/1.7Daniel Eklöf2021-04-18-2/+2
| |
| * changelog: prepare for 1.7.2Daniel Eklöf2021-04-18-5/+3
| |
| * changelog: add cglogic to ‘contributors’Daniel Eklöf2021-04-18-0/+2
| |
| * config: bold-text-in-bright: add ‘palette-based’ as a special valueDaniel Eklöf2021-04-18-12/+38
| | | | | | | | | | | | | | | | | | When ‘bold-text-in-bright’ is set ‘to palette-based’, colors matching one of the 8 regular palette colors are brightened by using the corresponding bright palette color. Other colors, or all colors if ‘bold-text-in-bright’ is set to ‘yes|true’, are brightened by increasing the luminance.
| * render: brighten: use corresponding bright palette color for base 8 colorsDaniel Eklöf2021-04-18-2/+14
| | | | | | | | | | | | | | | | When brightening one of the 8 base (“regular”) colors, use the corresponding bright palette color, instead of increasing the luminance. Closes #449
| * Fix commentOleh Hushchenkov2021-04-18-3/+1
| |
| * term: stop reading on eofOleh Hushchenkov2021-04-18-0/+5
| |
| * term: attributes struct: use ‘bool’ instead of ‘uint32_t’ for 1-bit membersDaniel Eklöf2021-04-18-13/+13
| |
| * render: no need to blend fully opaque sixel images - just blit themDaniel Eklöf2021-04-18-1/+1
| |
| * render: don’t let URL jump label sub-surfaces extend outside window geometryDaniel Eklöf2021-04-18-27/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have no guarantee that sub-surfaces extending outside the window geometry are rendered correctly (if at all). For example, both Sway and River will render the window border on top of the sub-surface. Future versions of Sway may clip the sub-surface. Since jump-labels are positioned slightly above, and to the left of the URLs first character, having a label on either the top row, or on the first column, will likely position it outside the window. This is handled by simply setting x/y to 0 (or, to -margin, since the label coordinate is later offsetted with the window margins). Second, if the label is very long, it may extend outside the window. This is very unusual for labels only showing the key, and not the URL itself, but could happen in this case too, if e.g. the user has configured double-width key characters. This is handled by calculating its maximum width, and then truncating the label. Although very unlikely, it is possible for a label to also extend outside the window’s vertical size. This could happen for very small font sizes, where the label’s own margins are large, relative to the font size. This case is currently not handled. Closes #443
| * doc: foot.ini: re-phrase the box-drawings-uses-font-glyphs sectionDaniel Eklöf2021-04-18-2/+3
| |
| * doc: foot.ini: codespell: antaliasing -> antialiasingDaniel Eklöf2021-04-18-1/+1
| |
| * config: add box-drawings-uses-font-glyphs=no|yes optionDaniel Eklöf2021-04-18-1/+30
| | | | | | | | | | | | | | | | | | When disabled, we render box drawing characters ourselves. This is the default. When enabled, we instead use font glyphs. I.e. no special treatment. Closes #430
| * render: draw underline cursor below text underlineDaniel Eklöf2021-04-18-2/+8
| | | | | | | | | | | | | | This ensures the cursor is visible on cells where the text is underlined. Closes #415
| * changelog: rewrite entry for OSC 17/117/19/119Daniel Eklöf2021-04-18-2/+2
| |
| * changelog: auto_left_margin on cub1 onlyDaniel Eklöf2021-04-18-0/+2
| |
| * term/vt: only do reverse-wrapping (‘bw’) on cub1Daniel Eklöf2021-04-18-40/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Foot currently does reverse-wrapping (‘auto_left_margin’, or ’bw’) on everything that calls ‘term_cursor_left()’. This is wrong; it should only be done for cub1. From man terminfo: auto_left_margin | bw | bw | cub1 wraps from column 0 to last column This patch moves the reverse-wrapping logic from term_cursor_left() to the handling of BS (backspace). Closes #441
| * osc: implement OSC 17+19: change selection background/foreground colorsDaniel Eklöf2021-04-18-13/+67
| | | | | | | | | | And of course, we also implement the corresponding reset sequences, OSC 117+119.
| * osc: reset background alpha when resetting the background colorDaniel Eklöf2021-04-18-0/+2
| |