aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
* sixel: do not reset palette after each imageDaniel Eklöf2020-06-10-5/+23
| | | | | | | | A client can re-use the palette between images. Resetting the palette breaks this. Now we initialize the palette on demand, and resets it when the palette size is changed (by the client).
* doc: benchmark: move alacritty-unicode-random text from footnote to separate chapterDaniel Eklöf2020-06-09-13/+20
|
* doc: benchmark: describe _why_ Alacritty is so fast in 'unicode-random'Daniel Eklöf2020-06-09-14/+29
|
* main: log architecture at startupDaniel Eklöf2020-06-09-0/+9
|
* readme: fix mastodon linkDaniel Eklöf2020-06-09-1/+1
|
* readme: add link to my mastodon accountDaniel Eklöf2020-06-09-0/+7
|
* sixel: log message: fix spellingDaniel Eklöf2020-06-09-1/+1
|
* osc: don't assert on \E]4 being followed by a ';'Daniel Eklöf2020-06-09-0/+5
| | | | | This fixes a crash (in debug builds) that could be triggered by e.g. cat:ing /dev/urandom.
* csi: \E[3J: reset render.last_cursor.row if necessaryDaniel Eklöf2020-06-09-0/+5
| | | | | This fixes a crash that occurred when the last rendered cursor cell had scrolled off screen, and \E[3J (clear scrollback) was executed.
* unicode combining: don't log overflow errors unless LOG_ENABLE_DBG == 1Daniel Eklöf2020-06-09-1/+4
|
* Merge branch 'faster-unicode'Daniel Eklöf2020-06-09-49/+147
|\
| * term: print_insert: early returnDaniel Eklöf2020-06-09-11/+12
| |
| * vt: utf8-print: check width == 0 first, when deciding whether to do combiningDaniel Eklöf2020-06-09-1/+1
| |
| * vt: initial version of UTF-8 decoding built-in into the VT parserDaniel Eklöf2020-06-07-37/+134
|/
* render: sixel: use pixman_image_composite32()Daniel Eklöf2020-06-06-1/+1
|
* render: cell: reset clip region also when we're NOT rendering a glyphDaniel Eklöf2020-06-06-1/+1
|
* sixel: don't erase image when printing text *next* to it.Daniel Eklöf2020-06-06-5/+20
|
* sixel: fix asan runtime warning: left shift of 255 by 24 cannot...Daniel Eklöf2020-06-06-4/+4
| | | | be represented in type 'int'
* PKGBUILD: works on aarch64 tooDaniel Eklöf2020-06-05-1/+1
|
* doc: benchmarks: results from my desktopDaniel Eklöf2020-06-05-14/+43
|
* render: regression: don't let cell background overflow into the marginsDaniel Eklöf2020-06-05-6/+8
| | | | | | | | | | | | This used to work before because we had a "global" clip region on the text area, excluding the margins. When we introduced per-cell clipping, this global clip region was removed, and the background drawing code could now overflow into the margins. This fixes it by setting the cell clip region not just when rendering a glyph, but before we render the cell background.
* render: re-write cell clipping to use pixman destination clippingDaniel Eklöf2020-06-04-60/+62
| | | | | | | | | | | | Our home rolled clip-to-cell code was, obviously, not correct. The original problem was that we couldn't use pixman clipping since we have multiple threads writing to the same pixman image, and thus there would be races between the threads setting clipping. The fix is actually simple - just instantiate one pixman image (referencing the same backing image data) for each rendering thread.
* Merge branch 'clip-to-cell'Daniel Eklöf2020-06-03-37/+43
|\
| * changelog: mention fix for glyphs overflowing into surrounding cellsDaniel Eklöf2020-06-03-0/+3
| |
| * render: do not allow glyphs to overflow into surrounding cellsDaniel Eklöf2020-06-03-37/+40
|/ | | | | | | | | | | | | | | This would be done cleaner by using destination clipping in pixman, but since we have multiple threads rendering cells simultaneously, that is not possible. We also cannot use source clipping since we need to offset the destination x,y coordinates with the glyph offsets. So, roll our own clipping by not allowing the x,y offsets to go outside the cell boundaries, and adjusting the glyph offset accordingly. Closes #21
* selection: fix typo when extending selection to cover double-width characterDaniel Eklöf2020-06-03-1/+1
|
* Merge branch 'initial-tiocswinsz'Daniel Eklöf2020-06-03-0/+10
|\
| * term: set an initial TIOCSWINSZ right after opening the ptyDaniel Eklöf2020-06-02-0/+10
|/ | | | | | | | Since foot is pretty aggressive about spawning the client early, it was possible for a fast client to read a 0x0 terminal size. Not all clients coped well. Closes #20.
* meson/PKGBUILD: require fcft 2.1.1Daniel Eklöf2020-06-02-2/+2
| | | | We really want that ÖCD RGB/BGR fix...
* render: draw hollow block cursor on top of the character, not the oppositeDaniel Eklöf2020-06-02-3/+3
|
* selection: don't allow only half of double-width characters to be selectedDaniel Eklöf2020-06-02-1/+30
|
* doc: benchmark: add terminal version numbers as foot notesDaniel Eklöf2020-05-31-7/+13
|
* Merge branch 'benchmark'Daniel Eklöf2020-05-31-1/+99
|\
| * doc: benchmark: right-align columnsDaniel Eklöf2020-05-31-1/+3
| |
| * doc: benchmark: fix typoDaniel Eklöf2020-05-31-1/+1
| |
| * doc: benchmark: newlinesDaniel Eklöf2020-05-31-2/+4
| |
| * doc: benchmark: newlines (?)Daniel Eklöf2020-05-31-2/+2
| |
| * doc: benchmarks: shell highlighting of vtebench commandsDaniel Eklöf2020-05-31-0/+2
| |
| * readme: fix benchmark linkDaniel Eklöf2020-05-31-1/+1
| |
| * benchmarks: initial resultsDaniel Eklöf2020-05-31-1/+42
| |
| * scripts: benchmarking utility scriptDaniel Eklöf2020-05-31-0/+51
|/
* vt: utf8: use mbtowc() instead of mbrtowc()Daniel Eklöf2020-05-31-8/+2
| | | | | | | | | This is slightly faster, since we don't need to initialize an mbstate_t struct (using mbrtowc() with a NULL-pointer for 'ps' also works). Also, avoid a branch by setting wc=0 and then ignoring the result/error code from mbtowc().
* vt: utf8: don't need one entry action for each UTF8 variantDaniel Eklöf2020-05-31-20/+6
|
* readme: cleanupDaniel Eklöf2020-05-30-8/+2
|
* readme: GCC requires -Wno-missing-profile in a PGO buildDaniel Eklöf2020-05-30-3/+6
|
* readme: add link to "running the new build" at the end of the release build sectionDaniel Eklöf2020-05-30-0/+1
|
* readme: describe what should expect to see when running the benchmarkDaniel Eklöf2020-05-30-0/+3
|
* reaadme: add step to remove the temp fileDaniel Eklöf2020-05-30-0/+1
|
* readme: add missing ')'Daniel Eklöf2020-05-30-1/+1
|
* readme: fix URLDaniel Eklöf2020-05-30-1/+1
|
* readme: describe how to do a PGO buildDaniel Eklöf2020-05-30-10/+85
|
* render: resize: don't try to signal TIOCSWINSZ on a closed ptmx FDDaniel Eklöf2020-05-27-1/+1
|
* Merge branch 'hold-option-in-footclient'Daniel Eklöf2020-05-27-0/+22
|\ | | | | | | | | | | | | This adds --hold to footclient. It was an oversight on my part to not add it from the beginning, when it was added to foot. Closes #17
| * changelog: mention addition of '--hold' to footclientDaniel Eklöf2020-05-26-0/+1
| |
| * doc: footclient: add --holdDaniel Eklöf2020-05-26-0/+3
| |
| * completions: zsh: footclient: add --holdDaniel Eklöf2020-05-26-0/+1
| |
| * client/server: implement '--hold' in footclientDaniel Eklöf2020-05-26-0/+17
|/
* slave: set IUTF8Daniel Eklöf2020-05-26-0/+15
|
* readme: mention that -O3 is default in release buildsDaniel Eklöf2020-05-25-1/+3
|
* readme: document work around for GCC 10.1 O2+PGO regressionDaniel Eklöf2020-05-25-2/+5
|
* meson: don't set -Wno-missing-profileDaniel Eklöf2020-05-25-2/+1
| | | | We don't do PGO by default
* PKGBUILD: always set -fno-plt and -Wno-missing-profileDaniel Eklöf2020-05-25-1/+5
|
* PKGBUILD: append -O3 to makepkg provided CFLAGSDaniel Eklöf2020-05-25-0/+1
| | | | This works around a GCC 10.1 O2+PGO regression.
* readme: compared with -> compared toDaniel Eklöf2020-05-25-1/+1
|
* meson: -fprofile-correction is automatically added by mesonDaniel Eklöf2020-05-25-1/+0
|
* readme: spelling: gpo -> pgoDaniel Eklöf2020-05-25-1/+1
|
* terminfo: put 'cvvis' on a separate lineDaniel Eklöf2020-05-25-1/+2
|
* readme: mention GCC 10.1 performance regressionDaniel Eklöf2020-05-25-0/+3
|
* changelog: is -> areDaniel Eklöf2020-05-21-1/+1
|
* reaper: disable debug loggingDaniel Eklöf2020-05-21-1/+1
|
* slave: restore signal maskDaniel Eklöf2020-05-21-1/+5
|
* term: don't double fork new terminal windowsDaniel Eklöf2020-05-21-57/+59
| | | | | Instead, register their PIDs with the new reaper module and let it handle them.
* reaper: new module, uses a signalfd to wait() on child processesDaniel Eklöf2020-05-21-0/+161
| | | | | | | | Use a signalfd to listen for SIGCHLD signals. When we receive a SIGCHLD over the signalfd, reap all dead children by looping over all registered child PIDs and call waitpid(WNOHANG) on them.
* readme: mention that gcc produces a much faster binary than clangDaniel Eklöf2020-05-21-0/+4
|
* meson: add -fprofile-correctionDaniel Eklöf2020-05-21-0/+1
|
* scrolling: fix crash when offset was exactly at the wrap-aroundDaniel Eklöf2020-05-19-2/+5
| | | | | | | When making sure we don't scroll past the scrollback history, and the current offset was exactly at the wrap around, the new view port was set to offset+1, which in this particular case meant outside the valid row numbers.
* selection: performance: check for < 0 or >= 0 instead of == -1Daniel Eklöf2020-05-19-9/+9
|
* selection: handle viewport wrap around correctlyDaniel Eklöf2020-05-19-49/+64
| | | | | When the viewport wraps around, the selection points may be "incorrect".
* term: scrolling: calling function must clamp scroll amountDaniel Eklöf2020-05-19-8/+16
|
* readme: add suggested cflags for a release buildDaniel Eklöf2020-05-18-3/+10
|
* term: erase_cell_range: set row->dirty before calling memset()Daniel Eklöf2020-05-17-2/+2
|
* term: scrolling: mark selection top if-statement as 'unlikely'Daniel Eklöf2020-05-17-4/+4
|
* term: scrolling: hopefully fix all selection/scrolling related crashesDaniel Eklöf2020-05-17-17/+89
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When scrolling, there are a couple of cases where an existing selection must be canceled because we cannot meaningfully represent it after scrolling. These are when the selection is (partly) inside: * The top scrolling region * The bottom scrolling region * The new lines scrolled in. I.e. re-used lines For the scrolling regions, the real problem is when the selection crosses the scrolling region boundary; a selection that is completely inside a scrolling regions _might_ be possible to keep, but we would need to translate the selection coordinates to the new scrolling region lines. For simplicity, we cancel the selection if it touches the scrolling region. Period. The last item, newly scrolled in lines is when the selection covers very old lines and we're now wrapping around the scrollback history. Then there's a fourth problem case: when the user has started a selection, but hasn't yet moved the cursor. In this case, we have no end point. What's more problematic is that when the user (after scrolling) moves the cursor, we try to create a huge selection that covers mostly empty (NULL) rows, causing us to crash. This can happen e.g. when reverse scrolling in such a way that we wrap around the scrollback history. The actual viewport in this case is something like `-n - m`. But the selection we'll end up trying to create will be `m - (rows - n)`. This range may very well contain NULL rows. To deal with this, we simply cancel the selection.
* selection: on_rows_in_view: fix range checkDaniel Eklöf2020-05-17-7/+5
|
* term: scrolling: sixel: simplify now that row count is clampedDaniel Eklöf2020-05-17-2/+2
|
* term: scrolling: in debug builds, verify all rows are allocatedDaniel Eklöf2020-05-16-0/+10
|
* term: scrolling: simplify, now that scroll row count is clampedDaniel Eklöf2020-05-16-11/+5
|
* term: scrolling: clamp number of rows to number of rows in scrolling regionDaniel Eklöf2020-05-16-13/+6
|
* grid: swap_row: remove unused parameter 'initialize'Daniel Eklöf2020-05-16-6/+6
|
* selection: copy: insert line break if either cell is emptyDaniel Eklöf2020-05-16-1/+5
|
* selection/render: sync cells' 'selected' bit before renderingDaniel Eklöf2020-05-16-0/+31
| | | | | | | | | | | | | | | | | | | | | | | For performance reasons, we track whether a cell is selected or not using a bit in a cell's attributes. This makes it easy for the renderer to determine if the cells should be rendered as selected or not - it just have to look at the 'selected' bit instead of doing a complex range check against the current selection. This works nicely in most cases. But, if the cell is updated, the 'selected' bit is cleared. This results in the renderer rendering the cell normally, i.e. _not_ selected. Checking for this, and re-setting the 'selected' bit when the cell is updated (printed to) is way too expensive as it is in the hot path. Instead, sync the 'selected' bits just before rendering. This isn't so bad as it may sound; if there is no selection this is a no-op. Even if there is a selection, only those cells whose 'selected' bit have been cleared are dirtied (and thus re-rendered) - these cells would have been re-rendered anyway.
* term: scrolling: clear selection *before* scrollingDaniel Eklöf2020-05-16-12/+15
| | | | | | | | | | | | We normally don't clear the selection when scrolling. The exception is when the selection covers re-used rows. I.e. rows that we scroll in and clear. In this case we cancel the selection (we _could_ modify it and keep as much as possible and only remove the re-used rows...). We must do this *before* scrolling, since scrolling will swap rows (when there's a scrolling region). When this happens, the selection is "corrupted", and canceling it afterwards will not work.
* selection: update: don't assert on 'start' being setDaniel Eklöf2020-05-16-0/+1
|
* selection: don't automatically no-op operations if selection isn't enabledDaniel Eklöf2020-05-16-29/+25
| | | | | | | | | | | | | | | | | | When the client is capturing the mouse, selection can only be done by holding done shift. This is why a lot of selection functions are no-ops if selection isn't currently enabled. However, there are many cases where we actually need to modify the selection. In particular, selection_cancel(). Thus, only check for enabled selection when we're dealing with user input. Bonus: this also fixes a bug where an ongoing selection were finalized as soon as the user released shift, even if he was still holding down the mouse button.
* selection: on_row_in_view() -> on_rows_in_view(), and now takes a rangeDaniel Eklöf2020-05-16-15/+37
| | | | | This allows us to check the selection once when scrolling, instead of once for each scrolled in line.
* render: only apply transparency to the default background colorDaniel Eklöf2020-05-16-2/+9
|
* readme: add 'synchronized updates' to feature listDaniel Eklöf2020-05-16-0/+1
| | | | The support in foot isn't new, but let's make it more visible.
* terminfo: add tmux extension 'Sync' - indicates 'Synchronized Updates' supportDaniel Eklöf2020-05-16-0/+5
|
* changelog: prepare for the next, unreleased versionDaniel Eklöf2020-05-13-0/+11
|
* Merge branch 'releases/1.3'Daniel Eklöf2020-05-13-8/+5
|\