aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
* doc: foot.5: we support “real” urgency through XDG activationDaniel Eklöf2021-10-22-9/+6
| | | | | | Foot has been signaling window urgency through the (new) “XDG activation” protocol for some time now. Update the documentation to reflect this.
* changeloge: style fixesDaniel Eklöf2021-10-22-5/+6
|
* term: ignore window title updates if title is un-changedDaniel Eklöf2021-10-22-0/+5
|
* Merge branch 'update-input-serial-on-each-keypress'Daniel Eklöf2021-10-21-0/+4
|\ | | | | | | Closes #753
| * input: update serial on each key press/release and mouse buttonDaniel Eklöf2021-10-20-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The serial is used when copying/pasting data from the clipboard. Up until now, we’ve used the serial from the keyboard/mouse enter events. This works in most cases, but breaks in the following example: $ wl-copy WLCOPY /* Ctrl+Shift+v works fine (pastes "WLCOPY") */ $ printf "\033]52;c;eHl6\a" /* Ctrl+Shift+v pastes "WLCOPY" instead of "xyz" */ Shifting focus away and then back to the foot window, and re-executing the printf works, suggesting the “enter” serial is no longer valid after another process(?) has copied something to the clipboard. Updating the serial on key press/release (and the corresponding mouse serial on mouse button events) seems to fix this. I’ve also tested that “normal” copy/paste operations, within the same foot instance, and between foot and other applications, are still working. In at least river (wlroots based), and GNOME/mutter. Closes #753
* | config: error out on invalid grapheme-width-method valuesDaniel Eklöf2021-10-21-0/+7
| |
* | render: tab -> spacesDaniel Eklöf2021-10-20-6/+6
|/
* Merge branch 'parse-rgb-strlen'Daniel Eklöf2021-10-20-4/+5
|\
| * osc: use STRLEN() macro to make parse_rgb() more self-documentingCraig Barnes2021-10-20-4/+5
| | | | | | | | | | The empty literals in the macro are to ensure the argument itself is a string literal, so it can't be used on anything else.
* | Merge branch 'warn-not-to-use-single-letter-key-bindings-in-url-mode'Daniel Eklöf2021-10-20-1/+10
|\ \
| * | doc: foot.5: warn user to be careful with single letter key bindings in url modeDaniel Eklöf2021-10-20-1/+10
| | |
* | | Merge branch 'osc-bel'Daniel Eklöf2021-10-20-6/+19
|\ \ \ | |/ / |/| |
| * | osc: use BEL terminator in OSC replies to BEL-terminated OSC queriesCraig Barnes2021-10-20-6/+19
| |/ | | | | | | | | | | | | | | | | This matches the documented (and observed) behavior in xterm: > XTerm accepts either BEL or ST for terminating OSC sequences, and > when returning information, uses the same terminator used in a query -- https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Operating-System-Commands
* | Merge branch 'clipboard-convert-carriage-ret-to-new-line'Daniel Eklöf2021-10-20-0/+7
|\ \ | |/ |/| | | Closes #752
| * selection: convert \r -> \n when reading clipboard dataDaniel Eklöf2021-10-19-0/+7
|/ | | | | | | | This fixes an issue where pasting (using e.g. OSC-52) in client applications that doesn’t do this conversion themselves, like tmux, doesn’t work. Closes #752
* Merge branch 'nordiq'Daniel Eklöf2021-10-18-0/+25
|\
| * add Nordiq themearmin2021-10-18-0/+25
|/
* pgo: full-inner: add --override tweak.grapheme-shaping=noDaniel Eklöf2021-10-16-1/+8
| | | | | | | | | Grapheme shaping is now enabled by default in foot. However, when generating the profiling data in PGO builds, this results in skewed optimizations. The end result is worse benchmark results regardless of whether grapheme-shaping is enabled or not (when running the benchmarks).
* doc: foot.1: reporting bugs: move “search existing issues”Daniel Eklöf2021-10-16-2/+4
|
* readme: reporting bugs: move “search existing issues”Daniel Eklöf2021-10-16-2/+4
|
* doc: foot.1: reporting bugs: re-order and tweakDaniel Eklöf2021-10-16-5/+8
| | | | | * Tell people to search existing bugs first (open + closed) * Re-order instructions: most important ones first
* readme: reporting bugs: re-order and tweakDaniel Eklöf2021-10-16-6/+8
| | | | | * Tell people to search existing bugs first (open + closed) * Re-order instructions: most important ones first
* Merge branch 'enable-grapheme-shaping-by-default'Daniel Eklöf2021-10-16-16/+17
|\
| * config: enable grapheme shaping by defaultDaniel Eklöf2021-10-13-16/+17
|/ | | | | | | | This changes the default value of tweak.grapheme-shaping to “yes”, thus enabling grapheme shaping by default. It also changes the default value of tweak.grapheme-width-method to “wcswidth”, for maximum compatibility with terminal applications.
* Merge branch 'generate-version-handle-repo-not-having-any-tags'Daniel Eklöf2021-10-11-6/+18
|\
| * ci: run “foot --version” and “footclient --version” after each buildDaniel Eklöf2021-10-11-0/+10
| |
| * generate-version: handle git repo not having any tagsDaniel Eklöf2021-10-11-6/+8
| |
* | doc: ctlseq: improve text formatting in CSI and SGR sectionsCraig Barnes2021-10-11-10/+10
| | | | | | | | | | | | | | | | Using underlining for parameters allows the angle brackets to be removed while still keeping a visual separation between literals and parameters. The removes any uncertainty about whether the angle brackets are part of the sequence or not. It also mirrors the formatting used further down in the document.
* | doc: ctlseq: fix SGR table headingCraig Barnes2021-10-11-2/+2
|/ | | | | The other tables that contain only params also use the heading "Parameter" rather than "Sequence".
* ci: limit builds to the master branch (and pulls targeting it)Daniel Eklöf2021-10-10-0/+4
|
* ci: codeberg CIDaniel Eklöf2021-10-10-0/+88
|
* foot.ini: add commented out default value of colors.scrollback-indicatorDaniel Eklöf2021-10-10-0/+1
|
* Merge branch 'configurable-indicator-colors'Daniel Eklöf2021-10-10-1/+36
|\
| * changelog: list scrollback.indicator-color additionfeeptr@codeberg.org2021-10-09-0/+2
| |
| * doc: document indicator-colorfeeptr@codeberg.org2021-10-09-0/+7
| |
| * config, render: scrollback indicator: allow configuring scrollback indicator colorsfeeptr@codeberg.org2021-10-09-1/+27
|/
* Merge branch 'use-pixman-renderer'Daniel Eklöf2021-10-09-2/+2
|\
| * pgo: Use pixman renderer by default for PGO buildsStanislav Ochotnický2021-10-08-2/+2
| | | | | | | | | | | | | | | | | | | | Without pixman renderer override pgo builds in cage/sway require access to actual render devices. In Gentoo's case the builds are run as ordinary user and within a "sandbox" which prevents and logs access outside of predefined places during build. So let's default to pixman renderer for the PGO builds. Hopefully that won't matter for the pgo optimizations to do the right thing within foot.
* | doc: benchmark: 1.9.2 results, laptopDaniel Eklöf2021-10-09-11/+11
| |
* | doc: benchmark: 1.9.2 results, beefy desktopDaniel Eklöf2021-10-09-1138/+11
|/
* Merge branch 'fix-0px-csd-crash'Daniel Eklöf2021-10-08-2/+6
|\
| * changelog: mention csd.size=0 fixfeeptr@codeberg.org2021-10-08-0/+1
| |
| * fix crashes when resizing after CSD enabled at runtime with csd.size = 0feeptr2021-10-04-2/+5
| |
* | Merge branch 'notify-focus-inhibit'Daniel Eklöf2021-10-07-8/+27
|\ \
| * | notify: add the notify-focus-inhibit config optionMitja Horvat2021-10-06-8/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | foot doesn't show desktop notifications (via OSC777) if the current terminal has keyboard focus. This is probably a sane default, but there are use cases where showing a notification regardless of the focus status may be desired. For example, a completion notification of a long running task inside a non-focused tmux window. This PR adds the notify-focus-inhibit option which can be used to disable inhibition of notifications when the window has focus. The default value is `yes`, which retains the old behavior.
* | | Merge branch 'mouse-modifiers-regression'Daniel Eklöf2021-10-07-15/+28
|\ \ \ | |/ / |/| | | | | Closes #736
| * | input: filter out non-significant modifiers when matching mouse bindingsDaniel Eklöf2021-10-06-15/+28
|/ / | | | | | | Closes #736
* / pgo: verify source dir really is a foot source dir before proceedingDaniel Eklöf2021-10-06-0/+5
|/
* input: check for ‘effective’ modifiers, not ‘depressed’Daniel Eklöf2021-10-02-6/+12
| | | | | | | When reading XKB modifier state, use XKB_STATE_MODS_EFFECTIVE, not XKB_STATE_MODS_DEPRESSED. This fixes handling of ‘sticky’ modifier keys.
* install: improve readability of the PGO LC_CTYPE paragraphDaniel Eklöf2021-10-02-2/+2
|
* pkgbuild: mention that “partial” produces a slower binary than “full”Daniel Eklöf2021-10-02-1/+3
|
* pkgbuild: spelling: procude -> produceDaniel Eklöf2021-10-02-1/+1
|
* changelog: add a new ‘unreleased’ sectionDaniel Eklöf2021-10-02-0/+11
|
* Merge branch 'releases/1.9'Daniel Eklöf2021-10-02-12/+5
|\
| * meson/pkgbuild: bump version to 1.9.21.9.2releases/1.9Daniel Eklöf2021-10-02-2/+2
| |
| * changelog: prepare for 1.9.2Daniel Eklöf2021-10-02-10/+3
| |
| * Merge branch 'master' into releases/1.9Daniel Eklöf2021-10-02-5/+52
| |\ | |/ |/|
* | pgo: full-inner: do not set LC_CTYPE=en_US.UTF-8Daniel Eklöf2021-10-02-5/+41
| | | | | | | | | | | | | | That locale may not exist. Instead, require the user/build script to explicitly set an UTF-8 locale. Document this in INSTALL.md, and in the bundled PKGBUILD.
* | changelog: add a new ‘unreleased’ sectionDaniel Eklöf2021-10-01-0/+11
| |
* | Merge branch 'releases/1.9'Daniel Eklöf2021-10-01-7/+6
|\|
| * meson/pkgbuild: bump version to 1.9.11.9.1Daniel Eklöf2021-10-01-2/+2
| |
| * changelog: prepare for 1.9.1Daniel Eklöf2021-10-01-5/+4
| |
| * Merge branch 'master' into releases/1.9Daniel Eklöf2021-10-01-468/+1031
| |\ | |/ |/|
* | Merge branch 'hacktober-theme'Daniel Eklöf2021-10-01-0/+22
|\ \
| * | Rename to Hacktobergrtcdr2021-09-26-0/+0
| | |
| * | add hacktoberfest themegrtcdr2021-09-22-0/+22
| | |
* | | Merge branch 'line-wise-selection-with-soft-line-wrapping'Daniel Eklöf2021-10-01-16/+85
|\ \ \ | | | | | | | | | | | | Closes #726
| * | | selection: line-wise selection now handles soft line-wrappingDaniel Eklöf2021-09-30-16/+85
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, soft-wrapped lines were not selected correctly, as the selection logic was hardcoded to simply select everything between the first and last column on the current terminal row. Now, we scan backward and forward, looking for hard-wrapped lines. This is similar to how word-based selection works. Closes #726
* | | Merge branch 'static-color-table'Daniel Eklöf2021-09-26-46/+33
|\ \ \
| * | | config: add comments to default_color_table[] about color channel valuesCraig Barnes2021-09-25-0/+2
| | | |
| * | | config: simplify initialization of color table in config_load()Craig Barnes2021-09-25-46/+31
|/ / /
* | | Merge branch 'non-dpi-aware-if-any-output-uses-scaling'Daniel Eklöf2021-09-24-27/+59
|\ \ \ | |/ / |/| |
| * | term: only scale using DPI if *all* monitors have a scaling factor or oneDaniel Eklöf2021-09-24-27/+59
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With dpi-aware=auto (the default), scale fonts using DPI *only* if *all* available monitors have a scaling factor of one. The idea is this: if a user, with multiple monitors, have enabled scaling on *at least* one monitor, he/she has most likely done so to match the size of his/hers other monitors. For example, if the user has one monitor with a scaling factor of one, and another one with a scaling factor of two, he/she expects things to be twice as large on the second monitor. If we (foot) scale using DPI on the first monitor, and using the scaling factor on the second monitor, foot will *not* look twice as big on the second monitor (this was the old behavior of dpi-aware=auto). Part of #714
* | doc: foot.ini: remove stray double quote characterDaniel Eklöf2021-09-22-1/+1
| |
* | readme: avoid having two “see...” right next after each otherDaniel Eklöf2021-09-22-1/+1
| |
* | doc: foot.ini: font: add reference to dpi-aware optionDaniel Eklöf2021-09-22-1/+2
| |
* | doc: foot.ini: mention how dpi-aware interacts with :pixelsize=NDaniel Eklöf2021-09-22-0/+7
| |
* | doc: foot.ini: mention how dpi-aware interacts with bitmap fontsDaniel Eklöf2021-09-22-5/+11
| |
* | box-drawing: repair debug logsDaniel Eklöf2021-09-19-4/+3
| |
* | Merge branch 'eflag'Daniel Eklöf2021-09-19-4/+31
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | Closes #184 Closes #257 Closes #313 Closes #596 Closes #625 Closes #716
| * | main/client: add no-op "-e" command-line optionCraig Barnes2021-09-18-4/+31
|/ /
* | main/client: replace some uses of printf() with puts() in print_usage()Craig Barnes2021-09-18-27/+28
| | | | | | | | | | | | FOOT_DEFAULT_TERM is a string literal passed as a -D argument to the compiler, so it can just be concatenated with the other string literals, instead of being formatted with printf().
* | log: simplify Boolean logic for setting "colorize" var in log_init()Craig Barnes2021-09-15-1/+1
| |
* | Merge branch 'braille'Daniel Eklöf2021-09-14-39/+185
|\ \ | | | | | | | | | Closes #702
| * | box-drawing: braille: prefer increasing spacing over dot widthDaniel Eklöf2021-09-14-17/+20
| | | | | | | | | | | | | | | | | | | | | | | | Too large dots make them harder to distinguish, when the spacing between them is small. Prefer increasing the spacing, instead of increasing the dot size. This looks better at small font sizes in particular.
| * | term: turn ‘box-drawings’ array into three dynamically allocated arraysDaniel Eklöf2021-09-14-42/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The box_drawings array is now quite large, and uses up ~4K when *empty*. This patch splits it up into three separate, dynamically allocated arrays; one for the traditional box+line drawing and block elements glyphs, one for braille, and one for the legacy computing symbols. When we need to render a glyph, the *entire* array (that it belongs to) is allocated. I.e this is one step closer to a dynamic glyph cache (like the one fcft uses), but doesn’t go all the way. This is especially nice for people with ‘box-drawings-uses-font-glyphs=yes’; for them, the custom glyphs now uses 3*8 bytes (for the three array pointers), instead of 4K.
| * | box-drawing: NOINLINE brailleDaniel Eklöf2021-09-12-1/+1
| | |
| * | render: codespell: aquire -> acquireDaniel Eklöf2021-09-12-1/+1
| | |
| * | box-drawing: add braille charactersDaniel Eklöf2021-09-12-7/+105
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Render braille ourselves, instead of using font glyphs. Decoding a braille character is easy enough; there are 256 codepoints, represented by an 8-bit integer (i.e. subtract the Unicode codepoint offset, 0x2800, and you’re left with an integer in the range 0-255). Each bit corresponds to a dot. The first 6 bits represent the upper 6 dots, while the two last bits represent the fourth (and last) row of dots. The hard part is sizing the dots and the spacing between them. The aim is to have the spacing between the dots be the same size as the dots themselves, and to have the margins on each side be half the size of the dots. In a perfectly sized cell, this means two braille characters next to each other will be evenly spaced. This is however almost never the case. The layout logic currently: * Set dot size to either the width / 4, or height / 8, depending on which one is smallest. * Horizontal spacing is initialized to the width / 4 * Vertical spacing is initialized to the height / 8 * Horizontal margins are initialized to the horizontal spacing / 2 * Vertical margins are initialized to the vertical spacing / 2. Next, we calculate the number of “remaining” pixels. That is, if we add the left margin, two dots and the spacing between, how many pixels are left on the horizontal axis? These pixels are distributed in the following order (we “stop” as soon as we run out of pixels): * If the dot size is 0 (happens for very small font sizes), increase it to 1. * If the margins are 0, increase them to 1. * If we have enough pixels (need at 2 horizontal and 4 vertical), increase the dot size. * Increase spacing. * Increase margins. Closes #702
* | Merge branch 'pgo-script'Daniel Eklöf2021-09-12-74/+258
|\ \ | | | | | | | | | Closes #701
| * | changelog: pgo build scriptsDaniel Eklöf2021-09-12-0/+3
| | |
| * | install.md: document pgo/*.sh scriptsDaniel Eklöf2021-09-12-0/+26
| | |
| * | pgo.sh: set -x *after* verifying inputDaniel Eklöf2021-09-12-1/+3
| | |
| * | pkgbuild: add back --prefix --wrap-mode=nofallbackDaniel Eklöf2021-09-12-1/+1
| | |
| * | pkgbuild: add ‘auto’ to the list of possible PGO valuesDaniel Eklöf2021-09-12-1/+1
| | |
| * | pgo: pgo.sh: remove both gcc and clang generated profile statsDaniel Eklöf2021-09-12-1/+8
| | |
| * | pkgbuild: the pgo script erases the old profdata filesDaniel Eklöf2021-09-12-1/+0
| | |
| * | pgo: pgo.sh: add meson bld/src dir arguments lastDaniel Eklöf2021-09-12-1/+1
| | |
| * | pgo: pgo.sh: run ‘find’ in the build-directory, not cwdDaniel Eklöf2021-09-12-1/+1
| | |
| * | pgo: pgo.sh: allow a pre-existing build directoryDaniel Eklöf2021-09-12-4/+4
| | |