aboutsummaryrefslogtreecommitdiff
path: root/grid.h (follow)
Commit message (Collapse)AuthorAgeLines
* grid: reflow: calculate width of composed characters correctlyDaniel Eklöf2020-09-06-1/+3
| | | | | Before this patch, reflow called `wcwidth()` on our magic values for composed characters.
* grid: swap_row: remove unused parameter 'initialize'Daniel Eklöf2020-05-16-1/+1
|
* grid: reflow: make tracking_points array 'const'Daniel Eklöf2020-04-17-1/+1
| | | | | The elements aren't, and cannot be, const. But the array itself can, and should be.
* grid: reflow: caller may now pass a list of coordinates that should be translatedDaniel Eklöf2020-04-17-1/+3
|
* grid: grid_reflow() now translates cursor coordinatesDaniel Eklöf2020-04-16-1/+1
|
* render/grid: move grid reflow code to grid.cDaniel Eklöf2020-02-15-0/+3
|
* search: wip: initial search matchingDaniel Eklöf2019-08-27-2/+14
| | | | | | | | * match search buffer against scrollback content * adjust view to ensure matched content is visible * create selection on a successful match * finalize selection when user presses enter (to "commit" the search) * ctrl+r searches for the next match. Needs more work though.
* scrolling: optimize row access by assuming number of rows is a power of 2Daniel Eklöf2019-08-22-8/+20
| | | | | | | | | | | | | | | | | | | With this assumption, we can replace 'a % b' with 'a & (b - 1)'. In terms of instructions, this means a fast 'and' instead of a slow 'div'. Further optimize scrolling by: * not double-initializing empty rows. Previously, grid_row_alloc() called calloc(), which was then followed by a memset() when scrolling. This is of course unnecessary. * Don't loop the entire set of visible rows (this was done to ensure all visible rows had been allocated, and to prefetch the cell contents). This isn't necessary; only newly pulled in rows can be NULL. For now, don't prefetch at all.
* grid: prefetch cells in grid_row()Daniel Eklöf2019-07-10-0/+1
|
* grid: repair grid_row_in_view(): use 'view', not 'offset'Daniel Eklöf2019-07-10-1/+1
|
* grid: don't pre-allocate the entire grid (with all scrollback lines)Daniel Eklöf2019-07-10-6/+22
| | | | | | | | | | The row array may now contain NULL pointers. This means the corresponding row hasn't yet been allocated and initialized. On a resize, we explicitly allocate the visible rows. Uninitialized rows are then allocated the first time they are referenced.
* grid: don't implement grid_swap_row() in the header fileDaniel Eklöf2019-07-10-24/+1
|
* wip: initial scroll back supportDaniel Eklöf2019-07-09-0/+7
| | | | | | | | | | | | | | | | | | | | | | | Can scroll up and down, and stops when the beginning/end of history is reached. However, it probably breaks when the entire scrollback buffer has been filled - we need to detect when the view has wrapped around to the current terminal offset. The detection of when we've reached the bottom of the history is also flawed, and only works when we overshoot the bottom with at least a page. Resizing the windows while in a view most likely doesn't work. The view will not detect a wrapped around scrollback buffer. I.e. if the user has scrolled back, and is stationary at a view, but there is still output being produced. Then eventually the scrollback buffer will wrap around. In this case, the correct thing to do is make the view start following the beginning of the history. Right now it doesn't, meaning once the scrollback buffer wraps around, you'll start seeing command output...
* wip: grid is now represented as a grid, not a linear arrayDaniel Eklöf2019-07-08-0/+28
| | | | | | | | | | | | The grid is now represented with an array of row *pointers*. Each row contains an array of cells (the row's columns). The main point of having row pointers is we can now move rows around almost for free. This is useful when scrolling with scroll margins for example, where we previously had to copy the lines in the margins. Now it's just a matter of swapping two pointers.
* grid: grid_memset() -> grid_memclear()Daniel Eklöf2019-07-07-1/+1
|
* scrolling: initial reverse scrolling support - no scroll regionsDaniel Eklöf2019-07-03-3/+3
|
* grid: implement a memmove-sort-of functionDaniel Eklöf2019-07-01-0/+1
| | | | | grid_memmove() moves cell data from one index to another, taking the grid offset into account.
* wip: use a sliding window instead of memmove() to scrollDaniel Eklöf2019-07-01-0/+4
| | | | | Instead of memmoving a large amount of data on every scroll, use a sliding window. That is, each time we scroll, we offset origin.
* Rename grid_* functions to term_*Daniel Eklöf2019-06-29-29/+0
|
* scroll-region: don't clear damage queue when changing scroll regionDaniel Eklöf2019-06-25-3/+7
| | | | | | | | | | | | | | | | | | | | | | Vim, for example, changes the scroll region every time you scroll a single line. Thus, resetting the damage queue is slow. This reworks the damage handling of scroll updates: * Split damage queue into two: one for scroll operations and one for update/erase operations. * Don't separate update/erase operations inside/outside the scroll region * Store the current scroll region in the scroll damage operation. This allows us to stack multiple scroll operations with different scroll regions. * When updating update/erase operations after a scroll operation, split the update/erase operations if necessary (the current scroll operation may have a scroll region different from before, thus forcing us to split existing update/erase operations. * The renderer no longer erases after a scroll. The scroll operation also adds an erase operation. This also means that erase operation are subject to adjustments by later scroll operations.
* scrolling region: wipDaniel Eklöf2019-06-23-1/+4
|
* vt: wip: implement scrolling regionDaniel Eklöf2019-06-23-2/+1
| | | | | | | | | | This is largely untested, but existing scrolling code has been converted to using a terminal-global scrolling region that is defined as start-end of the scrollable region. This is compared to the old code where the scrolling region where defined in terms of marginals, counted in lines from top and from bottom.
* vt: implement reverse scrolling (terminfo 'ri')Daniel Eklöf2019-06-23-1/+3
| | | | | This currently duplicates the code paths for DAMAGE_SCROLL; there are many similarities between the two, but also major differences...
* grid: implement DAMAGE_SCROLLDaniel Eklöf2019-06-21-0/+2
|
* Use a 'damage' list to communicate what needs to be updatedDaniel Eklöf2019-06-19-0/+3
| | | | | | | | | | Instead of having each cell in the grid track it's own dirtiness, grid operations now append "damage" to a list. This list is consumed every time we render the grid. This allows us to special case some operations, like erase (and in the future, scroll).
* wip: initial scrolling support (no scrollback though)Daniel Eklöf2019-06-19-0/+3
|
* wip: initial input handlingDaniel Eklöf2019-06-19-0/+2
|
* grid: track both linear and row,col cursorDaniel Eklöf2019-06-17-2/+8
|
* wip: vt parsing: break out grid operating functionsDaniel Eklöf2019-06-17-0/+8