aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Revert highlight patchHEADmasterSam Chudnick2023-02-262-44/+3
|
* Apply xresources patchSam Chudnick2023-02-253-8/+67
|
* Apply rejectnomatch patchSam Chudnick2023-02-253-2/+21
|
* Apply password patchSam Chudnick2023-02-254-5/+21
|
* Apply highlight patchSam Chudnick2023-02-254-3/+44
|
* Apply fuzzymatch patchSam Chudnick2023-02-255-2/+92
|
* Apply alpha patchSam Chudnick2023-02-254-21/+84
|
* bump version to 5.2Hiltjo Posthuma2022-10-041-1/+1
|
* dmenu: use die() to print the usage messageTom Schwindl2022-10-011-3/+2
|
* remove workaround for a crash with color emojis on some systems, now fixed ↵Hiltjo Posthuma2022-09-171-14/+0
| | | | | | in libXft 2.3.5 https://gitlab.freedesktop.org/xorg/lib/libxft/-/blob/libXft-2.3.5/NEWS
* fix a regression in the previous commit for tab completeHiltjo Posthuma2022-09-021-1/+1
| | | | Reported by Santtu Lakkala <inz@inz.fi>, thanks!
* tab-complete: figure out the size before copyingNRK2022-09-021-2/+2
| | | | | | | | | we already need to know the string length since `cursor` needs to be adjusted. so just calculate the length beforehand and use `memcpy` to copy exactly as much as needed (as opposed to `strncpy` which always writes `n` bytes).
* readstdin: use getline(3)NRK2022-09-021-7/+7
| | | | | | | | | | | | | currently readstdin(): - fgets() into a local buffer, - strchr() the buffer to eleminate the newline - stdups() the buffer into items a simpler way is to just use getline(3), which will do the allocation for us; eliminating the need for stdup()-ing. additionally getline returns back the amount of bytes read, which eliminates the need for strchr()-ing to find the newline.
* sync code-style patch from libslHiltjo Posthuma2022-08-081-11/+12
|
* Makefile: add manual path for OpenBSDHiltjo Posthuma2022-05-011-0/+1
|
* fix incorrect comment, math is hardHiltjo Posthuma2022-04-301-1/+1
|
* inputw: improve correctness and startup performance, by NRKHiltjo Posthuma2022-04-291-8/+2
| | | | | | | | Always use ~30% of the monitor width for the input in horizontal mode. Patch adapted from NRK patches. This also does not calculate inputw when using vertical mode anymore (because the code is removed).
* drw_text: account for fallback fonts in ellipsis_widthNRK2022-04-161-2/+4
| | | | | additionally, ellipsis_width (which shouldn't change) is made static to avoid re-calculating it on each drw_text() call.
* drw_text: don't segfault when called with 0 widthNRK2022-04-161-1/+1
| | | | | | | | | this patch just rejects *any* 0 width draws, which is surely an error by the caller. this also guards against cases where the width is too small for the ellipsis to fit, so ellipsis_w will remain 0. reported by Bakkeby <bakkeby@gmail.com>
* fix UB with the function iscntrl()Hiltjo Posthuma2022-03-261-1/+1
| | | | From commit 6818e07291f3b2913e687c8ec3d3fe4711724050 by NRK, thanks
* Revert "avoid redraw when there's no change"Hiltjo Posthuma2022-03-261-3/+2
| | | | | | This reverts commit 6818e07291f3b2913e687c8ec3d3fe4711724050. This broke keys such as ^W to delete-backward-word
* avoid redraw when there's no changeNRK2022-03-251-2/+3
| | | | | | | | | | | | | while i was timing the performance issue, i noticed that there was lots of random redrawing going on. turns out there were coming from here; if someone presses CTRL/ALT etc without pressing anything else, nothing will be inserted, so nothing will change. but the code will `break`, go down and do a needless redraw. this patch changes it to simply return if the keypress iscntrl() also avoid potential UB by casting *buf into an unsigned char.
* free all allocated items, use %zu for size_tNRK2022-03-251-3/+6
| | | | | `items` itself is not checked for NULL as calling free on NULL is defined to be a no-op.
* drw_text: improve performance when there's no matchNRK2022-03-251-1/+12
| | | | | | | | | | | | | | | | | | | | | | | this was the last piece of the puzzle, the case where we can't find any font to draw the codepoint. in such cases, we use XftFontMatch() which is INSANELY slow. but that's not the real problem. the real problem was we were continuously trying to match the same thing over and over again. this patch introduces a small cache, which keeps track a couple codepoints for which we know we won't find any matches. with this, i can dump lots of emojies into dmenu where some of them don't have any matching font, and still not have dmenu lag insanely or FREEZE completely when scrolling up and down. this also improves startup time, which will of course depend on the system and all installed fonts; but on my system and test case i see the following startup time drop: before -> after 60ms -> 34ms
* inputw: improve correctness and startup performanceNRK2022-03-251-10/+9
| | | | | | | | | | | | | | | | a massive amount of time inside readstdin() is spent trying to get the max input width and then put it into inputw, only for it to get clamped down to mw/3 inside setup(). it makes more sense to calculate inputw inside setup() once we have mw available. similar to the last patch, i see noticeable startup performance improvement: before -> after 160ms -> 60ms additionally this will take fallback fonts into account compared to the previous version, so it's not only more performant but also more correct.
* significantly improve performance on large stringsNRK2022-03-251-3/+10
| | | | | | | | | | | | | | | this replaces inefficient pattern of `MIN(TEXTW(..), n)` with drw_fontset_getwidth_clamp() instead, which is far more efficient when we only want up to a certain width. dumping a decently sized (unicode) emoji file into dmenu, I see the startup time drop significantly with this patch. before -> after 360ms -> 160ms this should also noticeably improve input latency (responsiveness) given that calcoffsets() and drawmenu() are pretty hot functions.
* introduce drw_fontset_getwidth_clamp()NRK2022-03-252-2/+18
| | | | | | | | | | | | | getting the width of a string is an O(n) operation, and in many cases users only care about getting the width upto a certain number. instead of calling drw_fontset_getwidth() and *then* clamping the result, this patch introduces drw_fontset_getwidth_clamp() function, similar to strnlen(), which will stop once we reach n. the `invert` parameter was overloaded internally to preserve the API, however library users should be calling drw_fontset_getwidth_clamp() and not depend upon internal behavior of drw_text().
* drw_text: improve both performance and correctnessNRK2022-03-251-28/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | this patch makes some non-trivial changes, which significantly improves the performance of drawing large strings as well as fixes any issues regarding the printing of the ellipsis when string gets truncated. * performance: before there were two O(n) loops, one which finds how long we can go without changing font, and the second loop would (incorrectly) truncate the string if it's too big. this patch merges the overflow calculation into the first loop and exits out when overflow is detected. when dumping lots of emojies into dmenu, i see some noticeable startup time improvement: before -> after 460ms -> 360ms input latency when scrolling up/down is also noticeably better and can be tested with the following: for _ in $(seq 20); do cat /dev/urandom | base64 | tr -d '\n' | head -c 1000000 echo done | ./dmenu -l 10 * correctness: the previous version would incorrectly assumed single byte chars and would overwrite them with '.' , this caused a whole bunch of obvious problems, including the ellipsis not getting rendered if then font changed. in addition to exiting out when we detect overflow, this patch also keeps track of the last x-position where the ellipsis would fit. if we detect overflow, we simply make a recursing call to drw_text() at the ellipsis_x position and overwrite what was there. so now the ellipsis will always be printed properly, regardless of weather the font changes or if the string is single byte char or not. the idea of rendering the ellipsis on top incase of overflow was from Bakkeby <bakkeby@gmail.com>, thanks! however the original patch had some issues incorrectly truncating the prompt (-p flag) and cutting off emojies. those have been fixed in here.
* remove false-positive warning for int comparison as boolHiltjo Posthuma2022-03-011-1/+1
| | | | | | Reported by Prathu Baronia <prathu.baronia@praton.me>, patch slightly changed. Thanks!
* bump version to 5.1Hiltjo Posthuma2022-02-112-2/+2
|
* code-style: rm newline (oops)Hiltjo Posthuma2022-02-081-1/+0
|
* revert using strcasestr and use a more optimized portable versionHiltjo Posthuma2022-02-082-2/+21
| | | | | | ... compared to the old cistrstr(). Thanks for the feedback!
* follow-up fix: add -D_GNU_SOURCE for strcasestr for some systemsHiltjo Posthuma2022-02-071-1/+1
|
* improve performance of case-insensitive matchingHiltjo Posthuma2022-02-071-12/+1
|
* Revert "Improve speed of drw_text when provided with large strings"Hiltjo Posthuma2021-08-201-5/+2
| | | | | | | This reverts commit c585e8e498ec6f9c423ab8ea07cf853ee5b05fbe. It causes issues with truncation of characters when the text does not fit and so on. The patch should be reworked and properly tested.
* add support for more keypad keysHiltjo Posthuma2021-08-091-0/+11
| | | | | | The keypad Enter key was already supported. On some keyboard layouts like my laptop the page-up and page-down key is more comfortable to use. This adds a few lines but no complexity.
* Improve speed of drw_text when provided with large stringsMiles Alan2021-08-091-2/+5
| | | | | | Calculates len & ew in drw_font_getexts loop by incrementing instead of decrementing; as such avoids proportional increase in time spent in loop based on provided strings size.
* remove always true condition in if statementGuilherme Janczak2021-07-251-1/+1
|
* bump version to 5.0Hiltjo Posthuma2020-09-022-2/+2
| | | | ... and bump LICENSE year.
* Fix memory leaks in drwHiltjo Posthuma2020-06-111-0/+1
| | | | | Synced from dwm. Patch by Alex Flierl <shad0w73@freenet.de>, thanks.
* revert IME supportHiltjo Posthuma2019-03-031-12/+3
| | | | | | | dmenu will not handle IME support (st will, atleast for now). revert parts of commit 377bd37e212b1ec4c03a481245603c6560d0be22 this commit also broke input focus.
* improve xopenim error messageHiltjo Posthuma2019-02-121-1/+1
| | | | die() already prints a newline.
* make dmenu_path script executableHiltjo Posthuma2019-02-121-0/+0
| | | | (as dmenu_run is)
* fix crash when XOpenIM returns NULLHiltjo Posthuma2019-02-121-2/+11
| | | | for example when IME variables are set, but the program is not started (yet).
* Close when the embedding window is destroyedQuentin Rameau2019-02-042-2/+7
|
* Prepared 4.9 release.Anselm R Garbe2019-02-023-4/+18
|
* dmenu.1: document improved fastgrab behaviour from previous patchHiltjo Posthuma2019-01-271-2/+2
|
* Use slow path if stdin is a ttydok2019-01-271-3/+1
| | | | | If stdin is a tty and dmenu is ran with the fast option then it's impossible to close stdin because the keyboard is already grabbed.
* dmenu_path: always use the cachedirQuentin Rameau2018-07-211-6/+6
|
* Makefile: just show the compiler outputHiltjo Posthuma2018-06-021-38/+28
| | | | Don't be fancy and just show the actual output so debugging is simpler.