aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
* PKGBUILD/meson: bump version to 1.0.01.0.0releases/1.0Daniel Eklöf2019-12-15-2/+2
|
* selection: optimize \r\n -> \n when receiving clipboard dataDaniel Eklöf2019-12-15-6/+14
| | | | | | Instead of first memmoving, possibly lots of data lots of times, the received buffer, and _then_ calling the callback, simply call the callback multiple times, and just skip the \r character(s).
* vt: add commented out cases for 8-bit C1 control charactersDaniel Eklöf2019-12-14-0/+35
| | | | | | | | | | XTerm seems to ignore these when in UTF-8 mode. Since we _only_ support UTF-8, we don't need to recognize these control characters at all. However, it may be good to have them here for reference. So add them, but commented out, along with their corresponding 7-bit versions (which we _do_ recognize and implement).
* csi: describe format of reply to tertiary DADaniel Eklöf2019-12-14-4/+10
|
* csi: Send Device Attributes, Tertiary DA: require Ps == 0Daniel Eklöf2019-12-14-4/+7
|
* client: strncpy() size limit must be less than destination sizeDaniel Eklöf2019-12-14-1/+1
|
* client: add missing break after handling -t,--termDaniel Eklöf2019-12-14-0/+1
|
* client: add 's:' to the list of recognized short optionsDaniel Eklöf2019-12-14-1/+1
|
* Merge branch 'server-socket-path'Daniel Eklöf2019-12-14-43/+76
|\
| * completions: zsh: footclient: add -s,--server-socketDaniel Eklöf2019-12-14-1/+2
| |
| * completions: zsh: foot: complete optional -s,--server PATH argumentDaniel Eklöf2019-12-14-2/+2
| |
| * doc: footclient.1: add -s,--server-socketDaniel Eklöf2019-12-14-0/+3
| |
| * doc: foot.1: update with optional PATH argument to -s,--serverDaniel Eklöf2019-12-14-2/+6
| |
| * client: initialize/deinitialize the logging systemDaniel Eklöf2019-12-14-0/+2
| |
| * client: add -s,--server-socket command line optionDaniel Eklöf2019-12-14-16/+34
| | | | | | | | | | This allows the user to override the default path (XDG_RUNTIME_DIR/foot.sock) we try to connect to.
| * main: allow server socket path to be set on the command lineDaniel Eklöf2019-12-14-3/+9
| | | | | | | | | | This adds an optional argument to -s,--server that allows the user to override the default socket path (XDG_RUNTIME_DIR/foot.sock).
| * server: use socket-path from configDaniel Eklöf2019-12-14-19/+2
| |
| * config: add 'server_socket_path' and set a default valueDaniel Eklöf2019-12-14-0/+16
|/
* server: log socket packetDaniel Eklöf2019-12-13-1/+3
|
* meson: we now require -lmDaniel Eklöf2019-12-05-1/+3
|
* wayland: include more output (monitor) details in the log outputDaniel Eklöf2019-12-05-10/+26
|
* term: determine cell width from the width of the space characterDaniel Eklöf2019-12-05-1/+2
|
* config: trim leading spaces from fontsDaniel Eklöf2019-12-05-2/+7
| | | | | | | | When splitting the font configuration into multiple font specifications, we now trim leading spaces. This makes no actual difference; fontconfig matched the fonts just fine anyway, but this looks better in the logs.
* PKGBUILD: require fcft 0.4.xDaniel Eklöf2019-12-05-1/+1
|
* meson: require fcft 0.4.xDaniel Eklöf2019-12-05-1/+1
|
* fcft: update to 0.4.0Daniel Eklöf2019-12-05-0/+0
|
* term: test: set font DPI to the highest DPI we findDaniel Eklöf2019-12-04-4/+17
| | | | | | | | | | | In most cases (i.e. when there's only a single output/monitor), this will be *the* DPI value. In other cases, well... The _right_ thing to do is track the outputs our window is actually mapped on, and re-instantiate fonts depending on the current output's DPI. But that's for the future...
* main: stop initializing a default set of fontsDaniel Eklöf2019-12-04-25/+0
|
* fcft: update to 0.3.5Daniel Eklöf2019-12-04-0/+0
|
* fcft: update to 0.3.4Daniel Eklöf2019-12-04-0/+0
|
* fcft: update to 0.3.3Daniel Eklöf2019-12-04-0/+0
|
* meson: we don't need -lm anymoreDaniel Eklöf2019-12-03-3/+0
|
* fcft: update to 0.3.2Daniel Eklöf2019-12-03-0/+0
|
* meson: we don't need -lm anymoreDaniel Eklöf2019-12-03-1/+1
|
* fcft: update to 0.3.0Daniel Eklöf2019-12-03-12/+6
| | | | | fcft now calculates the underline and strikeout integer positions, making our rendering code much simpler.
* search: match_to_end_of_word: reset end_col when done with a rowDaniel Eklöf2019-12-03-0/+2
|
* search: match_to_end_of_word: bug: reset end-col when bumping end-rowDaniel Eklöf2019-12-03-1/+3
| | | | | | | | When we calculate the end coords, we must reset end-col when we reach the end of the line and bump the end-row. This fixes an issue where bumping the row once lead to the end row being bumped for *each* remaining match character.
* search: bug: restore end-col/end-row adjustmentDaniel Eklöf2019-12-03-2/+4
| | | | | Turns out end_col *can* be exactly 0. In this case, we need to adjust the end-row too.
* render: limit size of search surface to parent windowDaniel Eklöf2019-12-03-4/+2
| | | | | | This shouldn't be necessary, but Sway acts up when the subsurface exceeds the parent surface (window, in this case) size, and extends the window size (if floating), leaving it with no content
* Merge branch 'scrollback-search-extend-to-end-of-word'Daniel Eklöf2019-12-03-110/+228
|\
| * search: bug: re-initialize start-row when attempting a new matchDaniel Eklöf2019-12-03-4/+4
| | | | | | | | | | | | When we've already found a partial match (but *not* a complete match), and that match spanned multiple lines, then when we continued with the next start-column we re-used a know-wrong row pointer.
| * render: don't allow negative coordinates of the search surfaceDaniel Eklöf2019-12-03-1/+2
| | | | | | | | | | | | While the protocol allows this, it appears Sway offsets (moves) the parent surface when this happens, resulting in a window half without content.
| * search: map ctrl+shift+w to match to end of word, spaces onlyDaniel Eklöf2019-12-03-4/+12
| | | | | | | | | | This works just like ctrl+w, except that the only space separating characters are whitespaces.
| * search: search_match_to_end_of_word: rename start_{row,col} -> end_{row,col}Daniel Eklöf2019-12-03-8/+10
| |
| * search: split up search_update() into twoDaniel Eklöf2019-12-03-68/+71
| | | | | | | | | | | | | | | | | | * search_find_next() searches the scrollback, continuing from the last match. The assumption is that the search buffer has changed. * search_update_selection() updates the selection and moves the view to ensure the selection is visible. Note that it doesn't verify the selection actually matches the search buffer.
| * search: rename search_update() -> search_find_next()Daniel Eklöf2019-12-03-3/+3
| |
| * README: describe ctrl+w while scrollback searchingDaniel Eklöf2019-12-03-0/+6
| |
| * search: map ctrl+w to 'extend current selection to end of word'Daniel Eklöf2019-12-03-0/+75
| | | | | | | | | | | | | | If the user has started a scrollback search and have some matching text, he can now press ctrl+w to extend that selection (and thus the search criteria too) to the end of the current word, or to the end of the next word if currently at a word separating character.
| * search: discard canceled compose sequencesDaniel Eklöf2019-12-03-0/+2
| |
| * Revert "search: discard canceled compose sequences"Daniel Eklöf2019-12-03-4/+0
| | | | | | | | This reverts commit f67733c0e3a4e4ba19e1c70bc36ee78af762868f.
| * search: discard canceled compose sequencesDaniel Eklöf2019-12-03-0/+4
| |
| * search: remove debug logDaniel Eklöf2019-12-03-1/+0
| |
| * search: don't line-wrap unless we actually have a match on the next rowDaniel Eklöf2019-12-03-4/+6
| | | | | | | | | | | | | | | | When matching characters, we moved on to next row directly after matching the last character in a row. This was wrong since if that last character was the last matching character, we tried to create a selection that was on the wrong row.
| * search: break out search buffer resize code to a new functionDaniel Eklöf2019-12-03-12/+21
| |
| * selection: break out isword() to a new fileDaniel Eklöf2019-12-03-21/+32
|/
* input: discard canceled compose sequencesDaniel Eklöf2019-12-02-0/+2
|
* Merge branch 'fcft-0.2.0'Daniel Eklöf2019-12-01-29/+26
|\
| * PKGBUILD: tllist is only a make dependency, bump fcft to 0.2.0Daniel Eklöf2019-12-01-2/+2
| |
| * meson: require fcft 0.2.0Daniel Eklöf2019-12-01-1/+1
| |
| * fcft: fixupDaniel Eklöf2019-12-01-0/+0
| |
| * Add missing includesDaniel Eklöf2019-12-01-0/+3
| |
| * fcft: font_from_name() no longer accepts a tllistDaniel Eklöf2019-12-01-26/+20
| |
| * fcft: bump to 0.2.0Daniel Eklöf2019-12-01-0/+0
|/
* meson: fcft: version must be 0.1.xDaniel Eklöf2019-12-01-1/+1
|
* fcft: bumpDaniel Eklöf2019-12-01-0/+0
|
* PKGBUILD/meson: add version requirements to tllist+fcftDaniel Eklöf2019-12-01-4/+4
|
* fcft: bumpDaniel Eklöf2019-12-01-0/+0
|
* fcft: bumpDaniel Eklöf2019-12-01-0/+0
|
* PKGBUILD: don't allow subproject fallbackDaniel Eklöf2019-12-01-1/+1
|
* meson: tllist/fcft: use system dependency first, fallback to subprojectsDaniel Eklöf2019-12-01-14/+3
|
* meson/PKGBUILD: we no longer depend directly on fontconfig/freetypeDaniel Eklöf2019-12-01-8/+2
|
* PKGBUILD: strip extra git revision data from checked in PKGBUILDDaniel Eklöf2019-12-01-1/+1
|
* fcft: include <fcft/fcft.h>, and use fcft/stride.h instead of local copyDaniel Eklöf2019-12-01-13/+4
|
* README: add tllist and fcft to list of required librariesDaniel Eklöf2019-12-01-0/+2
|
* PKGBUILD: add tllist and fcft dependenciesDaniel Eklöf2019-12-01-1/+2
|
* meson: tllist/fcft: oops, forgot to set 'required: false'Daniel Eklöf2019-12-01-2/+2
|
* Merge branch 'use-fcft'Daniel Eklöf2019-12-01-1510/+31
|\
| * PKGBUILD: don't error out on missing profile data count filesDaniel Eklöf2019-12-01-5/+1
| |
| * fcft: use fcft instead of local copy of font.c/font.hDaniel Eklöf2019-12-01-8/+22
| |
| * meson: tllist: try subproject first, then fallback to system dependencyDaniel Eklöf2019-12-01-1/+6
| |
| * tllist: add git submodule directly under subprojectsDaniel Eklöf2019-12-01-0/+3
| |
| * tllist: remove git submodule and local copy under subprojectsDaniel Eklöf2019-12-01-1497/+0
|/
* font: log fontconfig/freetype version when debug logging has been enabledDaniel Eklöf2019-12-01-0/+20
|
* Revert "font: ceil:ing the top value seems to look better when scaled"Daniel Eklöf2019-12-01-1/+1
| | | | This reverts commit 95d97b39734026e05f47b2064fe686da1ae40d20.
* font: ceil:ing the top value seems to look better when scaledDaniel Eklöf2019-11-30-1/+1
|
* font: fix estimated underline thickness; descent is typically negativeDaniel Eklöf2019-11-30-1/+1
|
* term: mouse reporting functions no longer take modifier stateDaniel Eklöf2019-11-30-20/+26
| | | | | | | | | | | | | | | | The mouse reporting functions are called from input when we receive Wayland mouse events. We used to pass the current keyboard modifier (shift, alt, ctrl, etc) to the terminal functions. This however is wrong, since we may receive Wayland mouse events without having keyboard focus. When we don't have keyboard focus, the modifier state doesn't apply to us. Remove the modifier arguments from the terminal mouse reporting functions. These functions now read this state directly instead, but only when the terminal instance in question has keyboard focus.
* term: add term_mouse_grabbed()Daniel Eklöf2019-11-30-30/+17
| | | | | | When this returns true, it means we have keyboard focus and are grabbing the mouse (for e.g. selections), regardless of whether the client has enabled mouse tracking or not.
* commands: scrollback: don't scrollback if mouse tracking is enabledDaniel Eklöf2019-11-30-0/+3
|
* input: doh! mouse_scroll: first argument to keyboard_key() is a struct waylandDaniel Eklöf2019-11-30-2/+2
| | | | This is the problem with void* user data pointers in callbacks...
* commands: scrollback: don't scrollback if mouse tracking is enabledDaniel Eklöf2019-11-30-0/+3
|
* input: mouse_scroll: cache XKB_KEY_Up and XKB_KEY_DownDaniel Eklöf2019-11-30-2/+9
|
* term: "raw" mouse mode requires shift only to be pressedDaniel Eklöf2019-11-30-3/+12
|
* render: fix underline/strikeout positioningDaniel Eklöf2019-11-30-19/+21
| | | | | | | | | | | | There were two errors: * We subtracted half the line width instead of adding it to the baseline * We rounded the line positioning and thickness before the positioning calculation. In particular, rounding the thickness before using it to adjust the position was wrong. Now we round just before the pixman call.
* render: font_baseline(): simply use the primary font's ascentDaniel Eklöf2019-11-30-16/+4
| | | | | | This is what we used as baseline for regular glyphs anyway. Thus, we can update that code to call font_baseline() now. This makes it easier to change how we define the baseline in the future.
* font: bug: bad multiplier when converting from 16.16 fixed floatDaniel Eklöf2019-11-30-1/+1
|
* term: define xcursor strings as global variablesDaniel Eklöf2019-11-30-3/+7
|
* font: cache_size -> glyph_cache_sizeDaniel Eklöf2019-11-30-4/+4
| | | | This makes it more clear it has nothing to do with the font cache.
* font: destructor: pop elements as we goDaniel Eklöf2019-11-30-1/+1
| | | | Otherwise we'll end up free:ing the same font over and over again.
* font: original -> requestedDaniel Eklöf2019-11-30-8/+8
|