aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
| * tllist: import static copy under 'subprojects'Daniel Eklöf2019-11-24-0/+603
| |
| * tllist: add git submodule under 'external'Daniel Eklöf2019-11-24-0/+4
| |
| * tllist: completely removeDaniel Eklöf2019-11-24-3/+0
|/
* generate-version: handle builds that aren't git clonesDaniel Eklöf2019-11-24-1/+1
|
* input: document why wayl->focused may be NULLDaniel Eklöf2019-11-23-1/+7
|
* wayland: change disconnected log type from err -> warnDaniel Eklöf2019-11-23-1/+1
|
* PKGBUILD: update url to point to new hosting serviceDaniel Eklöf2019-11-23-1/+1
|
* input: improve behavior when sway bugs outDaniel Eklöf2019-11-22-3/+17
| | | | | | | | | | | | | | | When we receive a keyboard_key or pointer_motion event without first having received a keyboard_enter or pointer_enter event (that being the "sway bugs" part), we generally don't know _which_ terminal window the event was intended for. However, if we only have *one* window open (always the case for a regular 'foot' process, or when there's a single footclient connected to a foot server process), then obviously we can "guess" which window the event was intended for... so do that. Now, the only time the event is ignored is when we're a server process with more than one window open (= more than one footclient connected).
* input: use xkb_keymap_key_repeats() to determine if we should start repeat timerDaniel Eklöf2019-11-22-19/+19
|
* input: keyboard_key: don't start repeater unless we generated outputDaniel Eklöf2019-11-22-54/+57
| | | | | | | | | | | I.e. what we're effectively doing is *not* repeating modifier keys. Besides being the "right" thing to do, this also works around another Sway 1.2 bug, where being in a focused foot window and then switching to a vt and back would cause us to be stuck in an endless key repeat loop that would only stop when unfocusing, focusing back and then unfocusing once again.
* input: workaround buggy Sway sending bad input eventsDaniel Eklöf2019-11-22-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Sway 1.2 has been seen sending keyboard_key() events without first sending a keyboard_enter() event. This can be triggered by: 1. start a foot terminal 2. unfocus it (move focus to another window) 3. switch to a vt 4. switch back to sway 5. focus the foot terminal At this point, Sway will *not* send the keyboard_enter() event, but instead send a keyboard_key() event. (furthermore, if you now unfocus the window again, sway will send a keyboard_leave() event, still without having sent a keyboard_enter() event). Sway has _also_ been seen crashing in wl_pointer_motion(). Though this was in a build without proper debug information, everything points to a similar issue - i.e. sway is sending a motion event without first having sent an enter event. Workaround this by detecting this and logging a warning the first time it happens. The event is then ignored.
* selection: text_to_clipboard: assert the clipboard serial is not 0Daniel Eklöf2019-11-22-0/+1
|
* selection: selection_to_clipboard: exit early on no-selectionDaniel Eklöf2019-11-22-0/+3
| | | | | When there's no selection, exit early to avoid trying to get grid data from row -1.
* selection: we already have a direct pointer to the clipboard structDaniel Eklöf2019-11-22-1/+1
|
* keyboard repeat: pass current input serial to keyboard_key()Daniel Eklöf2019-11-22-1/+3
| | | | | | | This fixes an assertion when holding in ctrl+shift+c (copy to clipboard); subsequent "presses" would set the clipboard serial to 0, which we would then assert on in the next iteration when we tried to cancel the previous copy.
* term: shutdown: handle *not* being unmappedDaniel Eklöf2019-11-21-0/+14
| | | | | | | | | | When we're shutting down a terminal, we destroy our Wayland window, and assume that will unmap us. There are cases when this isn't true (most likely when e.g. a screen locker is active, and the unmap is being deferred). Handle by explicitly setting focused to NULL.
* input: may get keyboard_exit() event with no focused terminalDaniel Eklöf2019-11-21-1/+5
| | | | | | | | This happens on Sway when exiting a screen locker. Or at least that's when we see the problem; it's unclear if the event occurs when starting the screen locker, or when exiting it. Or maybe its both. Anyway, don't try to unfocus a NULL-terminal.
* log: set syslog facility to LOG_DAEMON when run in server modeDaniel Eklöf2019-11-20-5/+17
|
* main: mention why we initialize a font setDaniel Eklöf2019-11-20-0/+1
| | | | | | | | | | | | Since fonts are destroyed and removed from the font cache when the last instance is destroyed, closing the "last" terminal window in server mode would destroy the fonts, and their glyph caches. By instantiating the set in main, we ensure the fonts, and the glyph caches, remain. This makes launching new terminals (much) faster. Note that in "normal" (non-server) mode, this isn't really necessary, but also doesn't have any penalty.
* README: here -> hear (doh!)Daniel Eklöf2019-11-20-1/+1
|
* Revert "PKGBUILD: set b_pgo=generate in first call to meson"Daniel Eklöf2019-11-20-1/+3
| | | | | | | | This reverts commit 7c2dd936905de7aa21a483646b3765cd8d59eb4e. Or repeated pkgbuilds will fail since the first meson call doesn't *re*configure an already configured build tree, causing us to build with pgo=use when we should be using pgo=generate.
* Revert "input: remove unneeded(?) term_reset_view() calls"Daniel Eklöf2019-11-20-2/+2
| | | | | | | | | | | | This reverts commit 739c5cf7f026bd7792f94276e8d6b2587a6ff597. The original commit stated: Not sure why these were added here; they don't appear to be needed (we're writing to the client - it's up to the client to echo stuff, in which case we redraw as usual). But, client output doesn't cause a scrollback/view reset.
* PKGBUILD: add check()Daniel Eklöf2019-11-20-0/+4
|
* PKGBUILD: run 'ninja test' in pgo=generate phaseDaniel Eklöf2019-11-20-0/+2
| | | | Otherwise the build fails in the pgo=use phase.
* PKGBUILD: set b_pgo=generate in first call to mesonDaniel Eklöf2019-11-20-3/+1
| | | | This avoids a meson re-configure right off the bat.
* font: don't spam failures to lookup glyphsDaniel Eklöf2019-11-20-2/+2
|
* fonts: use 'weight' and 'slant', not 'style' when loading fontsDaniel Eklöf2019-11-19-6/+6
|
* doc: foot.1: highlight 'command' in the synopsisDaniel Eklöf2019-11-19-1/+1
|
* osc: copy to/from clipboard: alias 's' to 'p'Daniel Eklöf2019-11-19-5/+4
| | | | | | 'p' means 'primary', while 's' means 'selection'. Thus, a client can now request 'selection' clipboard data and will receive it from the primary selection.
* doc: foot.1: fix highlighting of reference to footclientDaniel Eklöf2019-11-19-1/+1
|
* README: add 'server mode' to the indexDaniel Eklöf2019-11-18-0/+1
|
* README: write a section about the server modeDaniel Eklöf2019-11-18-0/+34
|
* README: mention 'server mode' in the feature listDaniel Eklöf2019-11-18-0/+1
|
* tllist: switch to codeberg repo + bumpDaniel Eklöf2019-11-18-1/+1
|
* ci: run unit testsDaniel Eklöf2019-11-18-0/+2
|
* ci: verbose ninja outputDaniel Eklöf2019-11-18-2/+2
|
* meson: add 'version' dependency to footclientDaniel Eklöf2019-11-18-1/+1
| | | | | footclient (`client.c`, to be precise) includes `version.h`, which is a generated file.
* tllist: bumpDaniel Eklöf2019-11-18-0/+0
|
* terminfo: add tab stop related entries, hts and tbcDaniel Eklöf2019-11-18-0/+2
| | | | | hts - Horizontal Tab Set (?) tbc - Tab Clear
* csi: implement "Send Device Attributes (Tertiary DA)"Daniel Eklöf2019-11-18-0/+18
|
* csi: adjust reply to primary DADaniel Eklöf2019-11-18-1/+1
| | | | | | | | | | Report us as being VT220, as VT420 causes vttest to send a DECRQSS. This is a DCS request that we don't implement (there's no DCS handling *at all* - all DCS strings are ignored). Should be ok as no one appears to care about this one. Other terminals report a much lower level (urxvt for example, replies with vt100. We used to reply with vt102, which also was fine).
* csi: improve "Send Device Attributes (Primary DA)"Daniel Eklöf2019-11-18-2/+32
| | | | | | | Pretend we're a VT420, with a couple of supported features indicated. Note that I haven't verified we support *everything* that each features entails - or even what exactly a feature *is* (locator port?)
* csi: document "Send Device Attributes (Secondary DA)"Daniel Eklöf2019-11-18-0/+20
|
* csi: implement 'Query Device Status'Daniel Eklöf2019-11-18-0/+5
| | | | By replying with "Device OK"
* term: report_mouse_click(): legacy mode only supports rows/cols up to 223.Daniel Eklöf2019-11-18-2/+8
| | | | | | In the legacy mouse reporting mode, line and column numbers are limited to 223 (255-32). In case the current coordinate falls outside this, simply ignore it (don't report it).
* csi: add debug logs for the various mouse reporting modesDaniel Eklöf2019-11-18-1/+4
|
* term: assert(false) on MOUSE_X10Daniel Eklöf2019-11-18-3/+15
| | | | | This mouse mode is never enabled. I.e. we don't support it. Add asserts to catch usage of it, should we ever decide to implement it.
* tllist: is now an external "library", so use <> includesDaniel Eklöf2019-11-17-4/+7
|
* tllist: use tllist from external git repositoryDaniel Eklöf2019-11-17-182/+7
|
* term: try to improve on a performance regressionDaniel Eklöf2019-11-17-29/+17
| | | | | | | | When support was added for DECOM (absolute/relative row addressing), a small but noticeable (~3.5%) performance regression was introduced. Try to improve the situation by simplifying the relative-to-absolute conversion; only the row needs to be transformed.
* Revert "term: new function: term_autowrap()"Daniel Eklöf2019-11-17-16/+0
| | | | This reverts commit 686405b7031736445eeb35206e4a797a8dd78d91.
* Revert "vt: replace pre_print() with term_autowrap()"Daniel Eklöf2019-11-17-2/+14
| | | | This reverts commit fd8a3992745b9ec51b6e6c1dfc39faf01369b680.
* csi: implement 'CHT' - Cursor Horizontal TabDaniel Eklöf2019-11-17-0/+16
|
* vt: replace pre_print() with term_autowrap()Daniel Eklöf2019-11-17-14/+2
|
* term: new function: term_autowrap()Daniel Eklöf2019-11-17-0/+16
| | | | | | | Adds a linebreak (+ scroll if necessary) if we're in a deferred wrap and auto-margins are enabled. Return true when we wrapped, false otherwise.
* csi: implement 'CPL' - Cursor Previous LineDaniel Eklöf2019-11-17-0/+6
|
* csi: implement 'CNL' - Cursor Next LineDaniel Eklöf2019-11-17-0/+6
|
* csi: implement 'HPR' - Horizontal Position RelativeDaniel Eklöf2019-11-17-0/+1
|
* csi: fix bad implementation of CBT (back tab)Daniel Eklöf2019-11-17-6/+14
| | | | | | | * It takes a parameter, that indicates the number of tab stops to move through * Use the tab stops defined in the tab stops list, not hard coded mod 8 columns.
* csi: implement 'HPA' - Horizontal Position AbsoluteDaniel Eklöf2019-11-17-0/+1
|
* vt: bug (tab regression): don't get stuck on the same tab stopDaniel Eklöf2019-11-17-2/+2
| | | | | | | | | | | There were actually two bugs here: * When checking for a tab stop, make sure the new tab stop is at a different column. Otherwise you can't tab away from a tab stop. * When there aren't any tab stops configured, or when we're already beyond the last tab stop, then tab to the last column (at least I think that's what we're supposed to do).
* term: save/restore charsets on save/restore cursor+attributesDaniel Eklöf2019-11-17-6/+4
|
* term: convert anonymous 'charsets' struct to a named structDaniel Eklöf2019-11-17-4/+6
|
* term: move charset variables into an anonymous structDaniel Eklöf2019-11-17-14/+23
|
* term: restore_cursor: restore lcf flagDaniel Eklöf2019-11-17-0/+1
|
* term: move lcf flag into 'cursor' structDaniel Eklöf2019-11-17-16/+16
|
* term: add struct cursorDaniel Eklöf2019-11-17-99/+103
|
* term: rename: print_needs_wrap -> lcf (Last Column Flag)Daniel Eklöf2019-11-17-16/+16
|
* csi: el/ed/dch/ich/ech: reset 'print_needs_wrap' (lcf)Daniel Eklöf2019-11-17-0/+9
| | | | | This makes the result of 'wraptest', by Mattias Engdegård, match the behavior of 'DEC' (the architectural behavior of DEC terminals).
* term: cursor_{up,down}: limit cursor movements based on origin modeDaniel Eklöf2019-11-16-2/+8
|
* Merge branch 'tab-stop'Daniel Eklöf2019-11-16-67/+110
|\
| * vt: execute: \t: use tab stops from tab stop listDaniel Eklöf2019-11-16-3/+8
| | | | | | | | | | Instead of assuming hardcoded 8-width tab stops, use the tab stops from the tab stop list.
| * vt: implement ESC H - set tab stop at current columnDaniel Eklöf2019-11-16-0/+11
| |
| * tllist: update to latestDaniel Eklöf2019-11-16-27/+50
| | | | | | | | In particular, pull in tll_insert_{before,after}
| * selection: buffer may be empty if only empty cells where selectedDaniel Eklöf2019-11-16-0/+6
| |
| * csi: implement CSI 0g and CSI 3gDaniel Eklöf2019-11-16-0/+26
| | | | | | | | | | * 0g - clear tab stop at current column * 3g - clear all tab stops
| * vt: remove commented out codeDaniel Eklöf2019-11-16-37/+0
| |
| * render: configure default tab stops when resizing the terminalDaniel Eklöf2019-11-16-0/+5
| |
| * term: add tab-stop list to terminal structDaniel Eklöf2019-11-16-0/+4
|/ | | | This list is intended to store tab stop columns
* vt: DECALN: render at bottom of terminal, not in viewDaniel Eklöf2019-11-14-1/+1
|
* csi: CSI ?4h enables smooth scrolling, ?4l enables jump scrollingDaniel Eklöf2019-11-05-2/+7
|
* server: disable debug outputDaniel Eklöf2019-11-05-1/+1
|
* vt: implement VT - Vertical TabDaniel Eklöf2019-11-05-0/+5
| | | | Despite its name, it always moves down exactly one line.
* vt: always use hex (not octal)Daniel Eklöf2019-11-05-2/+2
|
* vt: log hex version of printed character tooDaniel Eklöf2019-11-05-1/+1
|
* vt: always disable state_names[] arrayDaniel Eklöf2019-11-05-1/+1
| | | | It isn't used anywhere, even with LOG_ENABLE_DBG
* csi: implement DECOM - switch cursor origin between absolute and relativeDaniel Eklöf2019-11-05-14/+64
| | | | | | | | | | | The default is absolute mode, where 0,0 is the upper left corner of the screen. In relative mode, the origin is relative the top scroll margin. Internally, we always track the current cursor position in absolute mode. Every time we the client *sets* or *queries* the cursor position in relative mode, we translate it to absolute.
* csi: DECCOLM erases screenDaniel Eklöf2019-11-05-0/+15
|
* vt: esc dispatch: implement DECALNDaniel Eklöf2019-11-05-65/+118
| | | | | | | In esc dispatch: * Switch on private first, then final * Recognize ESC #8 (DECALN), and implement it
* csi: CSI ?3h enables 132 column mode, CSI ?3l 80 column modeDaniel Eklöf2019-11-05-2/+6
|
* csi: implement force cursor positionDaniel Eklöf2019-11-05-0/+1
|
* scan-build: fix a couple of minor warnings from a scan-build runDaniel Eklöf2019-11-05-5/+7
|
* server/client: harden reading of initialization data, and make asyncDaniel Eklöf2019-11-05-33/+111
| | | | | | | | | | | | | | | | | | | | * Client terminal initialization data is now received asynchronously. To facilitate this, a couple of minor changes to the protocol was made: - The client now starts with sending a 4-byte unsigned integer with the *total* size of the initialization data (*not* including the size field itself. - Strings (TERM variable + argv) are now sent NULL-terminated * The server allocates a single buffer, and fills it asynchronously. When full (as indicated by the initial 'total size' integer), we parse it (taking care not to read outside boundaries etc, and verifies the lengths (of the TERM variable and argv array) indicated by the client matches the actual lengths of the strings received. * The server now ignores 'unexpected' data received from the client, after the terminal has been instantiated.
* server: workaround evil clientsDaniel Eklöf2019-11-05-0/+6
| | | | | If the clients attempt to send more data after we've instantiated the terminal, just consume the data but ignore it.
* server: don't cache argc/argv in client contextDaniel Eklöf2019-11-05-17/+18
|
* main: destroy cached SHM buffers *after* terminals have been destroyedDaniel Eklöf2019-11-05-2/+2
|
* terminal: ptmx: ignore *both* EPOLLIN and EPOLLOUT on EPOLLHUPDaniel Eklöf2019-11-05-5/+11
|
* selection: document the asynchronous behavior of text_from_{primary,clipboard}Daniel Eklöf2019-11-05-1/+17
|
* selection: make text_from_{clipboard,primary} asyncDaniel Eklöf2019-11-05-61/+84
|
* selection: initialize 'ctx' before jumping into its scopeDaniel Eklöf2019-11-05-2/+2
|