| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
We can assume that string vectors generated by tofi are already
normalised, so don't waste time normalising them again.
Also make sure to validate strings from the user.
|
|
Also fix a potential segfault in character parsing found by AFLplusplus.
|
|
|
|
|
|
Each piece of text is now individually themable, with foreground and
background colours and optionally rounded background corners.
|
|
The list was getting far too long, and is about to get even longer with
text styling options. The user is instead directed to the manpage.
Also, don't print usage to stderr if `-h` was passed.
|
|
This change avoids warning about old compositors on newer versions of
Sway. Sway never actually supported version 4, and recently changed to
report only version 3 as supported.
|
|
|
|
|
|
|
|
This adds `_sorted` to the names of `string_vec_find` and
`desktop_vec_find`, to make it clear that these functions require their
input to already be sorted.
Also fix a potential bug from not sorting the list of desktops in drun
mode.
|
|
By using a hash table rather than binary search to find existing items,
we can avoid the need to sort the input.
|
|
Some of the string vec code was still assuming that it was just a list
of `char *`s, rather than `struct scored_string`s. Correcting that makes
future changes a little less error prone, and allows significantly
simpler history sorting for tofi-run.
|
|
This is a short-term workaround for history sorting not working, due to
the binary search used to find exiting items relying on the input
already being sorted.
|
|
|
|
|
|
|
|
|
|
|
|
This is required on e.g. FreeBSD to define S_IRUSR / S_IWUSR.
|
|
|
|
|
|
|
|
This fixes an issue where receiving multiple keypresses in the time
taken to draw a frame could cause input to be out of sync with the
display.
|
|
All text handling should now be explicitly UTF-8 or UTF-32, removing the
ambiguity around wchar_t and related functions.
|
|
|
|
|
|
Fuzzy matching could previously take a very long time for long input
lines, as the number of possible matches quickly explodes. This commit
sets a line length limit of 100 characters - longer lines will only
return the first fuzzy match, rather than the best one.
|
|
Also changed keyboard shortcuts to use physical keycodes, rather than
XKB keysyms. This means shortcuts don't shift when keyboard layout is
changed.
|
|
|
|
This should allow case-insensitive matching for non-Latin characters,
and fix matching for characters with diacritics.
|
|
|
|
This allows tofi to show up on top of fullscreen windows.
|
|
Also fix unbound keys and modifiers resetting the selection.
|
|
|
|
|
|
|
|
This isn't a great workaround, but the "correct" solution (implement
proper resizing logic and don't parse the config until our window is
shown) would incur significant extra complexity.
|
|
This allows config files to include other files, so you can e.g. split
style and behaviour options into different files.
|
|
This also stops font sizes from scaling when --scale=false is set.
|
|
|
|
|
|
|
|
|
|
|
|
Ctrl-u is just a whole line delete for now, as there's no sense of a
cursor position in tofi (so the whole line is "left" of the cursor).
|
|
Previously, tofi wouldn't scale pixel values by the output's scale
factor. This allows pixel-perfect sizes on displays with scale factors
>1, but means that configs need to be changed on a per-monitor basis,
and is at odds with how other applications (notable Sway) behave.
This commit adds a new option, --scale, to scale pixel values by the
output's scale factor. For backwards compatibility, this currently
defaults to false, and font scaling is performed regardless (the
existing behaviour). In the next release, this will default to true, and
font scaling will follow the same behaviour as everything else.
|
|
It will now always find the best score possible.
|
