aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
| * footrc: add pipe-visible and pipe-scrollbackDaniel Eklöf2020-07-15-0/+2
| |
| * doc: foot.5: change pipe-visible example to use bemenu instead of fuzzelDaniel Eklöf2020-07-15-1/+1
| |
| * changelog: minorDaniel Eklöf2020-07-15-1/+1
| |
| * changelog: document pipe-visible and pipe-scrollback bindingsDaniel Eklöf2020-07-15-0/+4
| |
| * doc: foot.5: document pipe-visible and pipe-scrollbackDaniel Eklöf2020-07-15-0/+17
| |
| * config: oopsie, need to use strndup() on the pipe commandDaniel Eklöf2020-07-15-1/+1
| | | | | | | | Since it isn't NULL-terminated.
| * config: change syntax for pipe-command in key bindingDaniel Eklöf2020-07-15-7/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The pipe command can contain almost all printable characters. In particular, we can expect it to contain '='. Having the pipe command as part of the key breaks the key/value splitting. Change it so that it is instead an optional initial part of the value, enclosed in '[]'. I.e. instead of pipe-visible:cmd=binding we now need to write pipe-visible=[cmd] binding
| * input: commentsDaniel Eklöf2020-07-15-1/+3
| |
| * conf: bindings: allow several mappings for the same actionDaniel Eklöf2020-07-15-87/+166
| | | | | | | | | | If the bindings has different pipe command associated with them, treat them as different actions.
| * input: wip: initial support for piping scrollback/view to external toolsDaniel Eklöf2020-07-15-8/+133
| |
| * spawn: add optional stdin/stdout/stderr redirection FDsDaniel Eklöf2020-07-15-5/+11
| | | | | | | | | | If not -1, spawn() will redirect the child's stdin/stdout/stderr to these FDs.
| * config: add support for appending a 'spawn' argument to key bindingsDaniel Eklöf2020-07-15-3/+18
| | | | | | | | | | | | | | | | | | | | | | | | A key binding may now have an optional ':<cmd>' string appended to the key. This is intended to be used like so: pipe-scrollback:sh -c "cat > file"=Print TODO: we still only allow one *action*. Meaning you still cannot specify multiple pipe-scrollback bindings, for example.
| * input: parse_key_binding: free key-codes list if 'bindings' is NULLDaniel Eklöf2020-07-15-1/+3
| |
| * term: break out fork+exec functionality to a separate fileDaniel Eklöf2020-07-15-53/+82
| |
| * term: add term_scrollback_to_text() and term_view_to_text()Daniel Eklöf2020-07-15-2/+62
| | | | | | | | | | These functions extract the current view, or the entire scrollback as an UTF-8 encoded byte buffer.
| * extract: extract_one() sets a fail flag that extract_finish() readsDaniel Eklöf2020-07-15-7/+19
| | | | | | | | | | | | This allows us to safely call extract_finish() when extract_one() failed, and we'll get the expected result; false, indicating extract_finish() failed.
| * selection: provide a const-wrapper for extract_one()Daniel Eklöf2020-07-15-1/+9
| | | | | | | | | | extract_one() takes const pointers, while the callback argument to foreach() expects non-const.
| * extract: extract_one: make arguments constDaniel Eklöf2020-07-15-4/+7
| |
| * selection: refactor: break out text extraction to a separate fileDaniel Eklöf2020-07-15-170/+203
| |
| * conf: add definitions for pipe-{scrollback,view} bindingsDaniel Eklöf2020-07-15-0/+9
|/
* Revert "wiki: testing"Daniel Eklöf2020-07-15-1/+0
| | | | This reverts commit b2dec8db164645cebb82a114564ce231518e6494.
* wiki: testingDaniel Eklöf2020-07-15-0/+1
|
* selection: don't skip SPACER cells in the generic foreach()Daniel Eklöf2020-07-15-4/+3
| | | | | | | | As that breaks e.g. selection marking (SPACER cells didn't get inverted when rendered). Instead, skip them in extract_one() only. I.e. when copying text from the grid.
* selection: row->dirty is a booleanDaniel Eklöf2020-07-15-2/+3
|
* term: don't re-render last cursor cell if cursor was hiddenDaniel Eklöf2020-07-15-1/+3
|
* Merge branch 'multi-column-special-spacer-value'Daniel Eklöf2020-07-15-55/+69
|\
| * term: print: don't pad with spacers if auto-margin is disabledDaniel Eklöf2020-07-15-1/+1
| |
| * grid: reflow: use macro print_spacer() to insert multi-column character spacersDaniel Eklöf2020-07-14-8/+11
| |
| * term: copy current VT attributes to multi-column spacer cellsDaniel Eklöf2020-07-14-9/+14
| | | | | | | | | | And refactor: break out spacer-writing code to a function, since we do exactly the same thing in two places.
| * selection: no need to try to detect multi-column chars at the end of the lineDaniel Eklöf2020-07-14-16/+1
| | | | | | | | | | This is handled by the generic foreach() functions, which now simply skips spacer cells.
| * grid: reflow: handle multi column character spacersDaniel Eklöf2020-07-14-2/+22
| | | | | | | | | | | | | | | | | | Ignore *old* cells containing spacers. Pad new grid with spacers if a multi-column character doesn't fit at the end of a line. Insert spacers after a multi-column character.
| * term: print: linewrap + insert *before* inserting SPACERSDaniel Eklöf2020-07-14-3/+4
| | | | | | | | Otherwise we end up overwriting the character in the last column
| * term: print: write special value CELL_MULT_COL_SPACER to extra cellsDaniel Eklöf2020-07-14-17/+16
| | | | | | | | | | | | When printing a multi-column character, write CELL_MULT_COL_SPACER instead of '0' to both padding cells (when character doesn't fit at the end of the line), and to the cells following the actual character.
| * term: rename COMB_CHARS_LO,HI -> CELL_COMB_CHARS_LO,HIDaniel Eklöf2020-07-14-13/+14
|/
* selection: recognize empty padding cells in a forced linewrapDaniel Eklöf2020-07-14-9/+45
| | | | | | | | | | | | | | When printing a multi-column character at the end of the line, and it doesn't fit, we currently insert a forced line-wrap. This means the last character(s) on the previous line will be empty, followed by a multi-column character in the first cell on the next line. Without special code to handle this, the selection text extraction code will insert a hard newline, since this is normally the correct thing to do. Add a TODO, to consider writing a special place holder value to these padding cells.
* selection: foreach: don't call callback for trailing multi-character cellsDaniel Eklöf2020-07-14-1/+6
|
* changelog: 'not' -> 'now'Daniel Eklöf2020-07-14-1/+1
|
* grid: reflow: always emit *all* cells of a multi-column characterDaniel Eklöf2020-07-14-1/+7
|
* term: remove assert, as we're already checking for this in the loop conditionDaniel Eklöf2020-07-14-1/+0
|
* term: print: manually increment cursor columnDaniel Eklöf2020-07-14-3/+4
| | | | | We know we're within bounds, and thus we don't need the extra overhead of term_cursor_right().
* grid: reflow: use width=1 for invalid charactersDaniel Eklöf2020-07-14-1/+1
|
* term: line-wrap: need to update grid->cur_row when we did *not* scrollDaniel Eklöf2020-07-14-0/+1
|
* changelog: prefix all C0 names with 'C0::'Daniel Eklöf2020-07-14-3/+3
|
* term: print: also require width > 1 when checking if we need to force-wrap or notDaniel Eklöf2020-07-14-1/+3
| | | | | | While this might seem like it would slow down things, it should in fact help the compiler optimize: the "normal" code path, that prints regular ASCII characters, always call term_print() with width == 1.
* term: line-wrap: manually set cursor row+colDaniel Eklöf2020-07-14-3/+7
| | | | | line-wrap is in the hot path, and term_cursor_down/left adds additional checks that we don't need.
* grid: reflow: force line-wrap if a multi-column character does not fit on current lineDaniel Eklöf2020-07-14-14/+1
|
* term: print: force line-wrap if a multi-column character does not fit on current lineDaniel Eklöf2020-07-14-0/+9
|
* csi: DECAWM: clear LCFDaniel Eklöf2020-07-14-0/+5
|
* csi: IND+RI now clears LCFDaniel Eklöf2020-07-14-0/+3
|
* term: print: manually increment cursor column for multi-column charsDaniel Eklöf2020-07-14-2/+2
| | | | | There's nothing wrong with using term_cursor_right(), but it is unnecessary since we already check for the end-of-line.
* term: insert: move assert() after checking whether insert mode is enabled or notDaniel Eklöf2020-07-14-2/+2
|
* term: linefeed: explicitly clear LCFDaniel Eklöf2020-07-14-2/+6
| | | | | | LF should always clear LCF. Previously, it was done implicitly in term_cursor_down(). I.e it was cleared as long as the cursor wasn't at the bottom of the scrolling region
* vt: change HT (horizontal tab) to *not* clear LCFDaniel Eklöf2020-07-14-0/+8
| | | | | | According to the specification, HT **should** clear LCF. However, nearly all emulators do not. In particular, XTerm doesn't. So we follow suite.
* term: line-wrap: use term_cursor_{down,left}Daniel Eklöf2020-07-14-4/+4
|
* term: rename term_formfeed() -> term_carriage_return()Daniel Eklöf2020-07-14-5/+9
|
* vt: implement C0::FF - processed in the same way as C0::LFDaniel Eklöf2020-07-14-0/+3
|
* vt: process C0::VT the same way we process C0::LFDaniel Eklöf2020-07-14-6/+5
| | | | | | | | Previously, C0::VT was implemented as a simple 'cursor down'. I.e. it would behave as LF **until** it reached the bottom of the screen, where instead of scrolling, it became a no-op. See https://vt100.net/docs/vt102-ug/chapter5.html
* vt: sort C0's in the switch statement, and use escaped character possibleDaniel Eklöf2020-07-14-16/+16
|
* input: keyboard: keymap: close(fd) on early-return when failing to mmapDaniel Eklöf2020-07-14-0/+1
|
* input: keyboard: keymap: use xkb_keymap_new_from_buffer()Daniel Eklöf2020-07-14-2/+4
|
* input: keyboard: detect failure to mmap keymapDaniel Eklöf2020-07-14-0/+17
|
* Merge branch 'merge-wl-surface-damage'Daniel Eklöf2020-07-14-77/+100
|\ | | | | | | Closes #35
| * changelog: mention fix for 'too many wl_surface_damage_buffer()' callsDaniel Eklöf2020-07-13-0/+2
| |
| * wayland: configure: do a regular resize instead of a force resizeDaniel Eklöf2020-07-13-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | The commit log says that was needed to get tiling in GNOME working. However, I don't know *which* extension that was. Force resizing in a configure event means we'll trash a perfectly valid buffer on e.g. 'activated' state changes. So, let's revert this for now, and if this breaks GNOME, let's try to find another solution. If worse comes to worse, we can detect if we're running under GNOME and do a force-resize then, but not on sane compositors.
| * term: set_fonts: describe why we force resizeDaniel Eklöf2020-07-13-0/+1
| |
| * render: render_margin: don't damage margins when rendering scroll damageDaniel Eklöf2020-07-13-12/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When applying scroll damage, we may have to re-render the margins. This is because when we SHM-scroll, we actually move the entire surface, and thus we end up overwriting the top margin area with old window content, and scroll in uninitialized memory in the bottom margin. But, we don't have to tell the compositor about this - the last frame always contains correct margins; i.e. there's no change between the last frame and current frame being rendered. TODO: we _could_ micro-optimize and only damage the margins after a surface resize. We do it slightly more often now, when dealing with state changes in screen flash or scrollback searching. But I don't think it's worth the effort.
| * render: doh! flush the last surface damage *outside* of the rendering loopDaniel Eklöf2020-07-13-8/+8
| |
| * main: free 'cwd' at exitDaniel Eklöf2020-07-13-1/+2
| | | | | | | | | | This fixes an issue where e.g. failing to initialize the Wayland backend would leave cwd un-free:d
| * render: render_margin: add 'damage_{top,bottom,left,right}' argumentsDaniel Eklöf2020-07-13-20/+24
| |
| * render: render_margin(): remove top/bottom argumentsDaniel Eklöf2020-07-13-24/+20
| | | | | | | | All calls to render_margin() set top=true and bottom=true anyway.
| * render: merge wl surface damage for consecutive dirty rowsDaniel Eklöf2020-07-13-38/+55
|/
* render: keep lock while pushing dirty rows to worker queueDaniel Eklöf2020-07-13-19/+3
| | | | | | | | | | | | | | | | Instead of locking the queue for each dirty row we append, and signaling a condition variable, just keep the lock while going through the visible rows. Release the lock once done. Since we take the lock *before* posting the 'start' semaphore, all workers will be waiting for the lock to be released. Then, one at a time they'll get the lock and pick a row to render. The queue will never get empty - when all rows have been rendered, each worker will pick a 'frame done' "job" from the queue, and break the rendering loop.
* Merge branch 'renderer-dont-special-case-cursor-cell'Daniel Eklöf2020-07-13-83/+52
|\
| * render: don't render cursor when it has been explicitly hiddenDaniel Eklöf2020-07-12-2/+2
| |
| * render: remove most of the special handling of cursor renderingDaniel Eklöf2020-07-12-83/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, we had to explicitly render the old cursor cell *before* applying scrolling damage. We then rendered all the dirty rows, *without* rendering the cursor - even if the cursor cell was among the dirty rows. Finally, when everything else was done, we explicitly rendered the cursor cell. This meant a lot of code, and unnecessary render_cell() calls, along with unnecessary wl_surface_damage_buffer() calls. This was a necessary in the early design of foot, but not anymore. We can simply mark both the old cursor cell, and the current one, as dirty and let the normal rendering framework render it. All we need to do is pass the cursor column to render_row(), so that it can pass has_cursor=true in the appropriate call to render_cell(). We pass -1 here for all rows, except the cursor's row, where we pass the actual cursor column. With this, there's no need to calculate whether the cursor is visible or not; just mark it's cell as dirty, and if that row is visible, the normal rendering will take care of it. This also simplifies the state needed to be saved between two frames; we only need a row pointer, and the cursor column index. Part of https://codeberg.org/dnkl/foot/issues/35
* | doc: foot.5: 'runtime' -> 'at runtime'Daniel Eklöf2020-07-12-2/+3
|/
* changelog: hollow cursor is now based on keyboard focus, not visual focusDaniel Eklöf2020-07-11-0/+2
|
* term: update cursor on kbd focus changes, not visual focus changesDaniel Eklöf2020-07-11-2/+2
|
* input: include seat name in debug log outputDaniel Eklöf2020-07-11-4/+4
|
* render: use kbd-focus instead of visual focus for hollow block cursorDaniel Eklöf2020-07-11-5/+5
| | | | | | When determining whether we should render a hollow block cursor, i.e. to signal that we're unfocused, base the decision on the terminals current keyboard focus, not visual focus.
* term: remove term_has_kbd_focus(), use term->kbd_focus insteadDaniel Eklöf2020-07-11-18/+5
|
* term: cache kbd-focused state, just like we cache visual focus stateDaniel Eklöf2020-07-11-2/+12
| | | | | | There's one difference however, when we receive a kbd unfocus call, *all* seats must have us unfocused before we actually change the state.
* Merge branch 'multi-seat'Daniel Eklöf2020-07-11-707/+893
|\ | | | | | | Closes #32
| * wayland: destroy cursor theme when removing pointer capabilityDaniel Eklöf2020-07-10-0/+4
| |
| * wayland: seat: instantiate pointer surface in capabilities eventDaniel Eklöf2020-07-10-6/+12
| | | | | | | | | | This way we only instantiate the surface for seats that actually have a pointer.
| * wayland: read XCURSOR_{THEME,SIZE} in reload_xcursor themeDaniel Eklöf2020-07-10-34/+16
| |
| * seat: use separate 'enter' serials for keyboard and mouseDaniel Eklöf2020-07-09-12/+14
| |
| * multi-seat: improve handling of multiple (mouse) pointersDaniel Eklöf2020-07-09-90/+97
| | | | | | | | | | | | | | | | * xcursor always set for all pointers * xcursor sometimes not updated when it should be * mouse grabbed state wasn't per seat, but global (i.e. "does at least one seat enable mouse grabbing") * selection enabled state wasn't per seat
| * readme: add multi-seat support to the feature listDaniel Eklöf2020-07-09-0/+1
| |
| * changelog: add multi-seat supportDaniel Eklöf2020-07-09-0/+1
| |
| * focus in/out: terminal checks whether it is a state change or notDaniel Eklöf2020-07-09-19/+7
| |
| * wayland: globals: destroy: seat: use keyboard/pointer listener interfacesDaniel Eklöf2020-07-09-17/+9
| |
| * wayland: globals: destroy: handle seats being destroyedDaniel Eklöf2020-07-09-2/+39
| |
| * input: only call term_kbd_focus_{in,out}() on actual state changeDaniel Eklöf2020-07-09-7/+24
| | | | | | | | | | | | That is, only call term_kbd_focus_in() if we're the *first* seat focusing that terminal, and only call term_kbd_focus_out() if we're the *last* seat that focused it.
| * wayland: log: be clear that these are the XCRUSOR_* environment variablesDaniel Eklöf2020-07-08-2/+1
| |
| * xcursor: trigger theme reload in pointer-enter eventDaniel Eklöf2020-07-08-9/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, we triggered a theme reload on output changes. This is completely wrong. We may get a new output with a scale different from the output the pointer is actually on. Now, we store the current scale along with the theme. We then trigger a call to reload the xcursor theme *every* time the pointer enters a surface. When it does, we use the current scale factor of the terminal that owns that surface. If the terminal covers multiple outputs, with different scale factors, we'll use the largest scale factor. This may not be 100% correct. But to fix that, we'd need to track which regions of a surface are mapped on which outputs. Too complicated I say.
| * wayland: seat: log keyboard/pointer capabilityDaniel Eklöf2020-07-08-1/+4
| |
| * multi-seat: re-enable OSC 52 supportDaniel Eklöf2020-07-08-15/+38
| |
| * multi-seat: re-enable selection support (excluding OSC 52)Daniel Eklöf2020-07-08-109/+104
| |
| * multi-seat: re-enable scrollback search supportDaniel Eklöf2020-07-08-29/+16
| |