diff options
| author | blasty <blasty@local> | 2026-07-23 21:39:08 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-23 21:39:33 +0200 |
| commit | a865213d04f621f3f87ad3d1873faea47709ed79 (patch) | |
| tree | 4b1f8c1bb2e3dc9c78157d5d51122ec10f843101 /server | |
| parent | views: highlight all occurrences of the token under the cursor (diff) | |
| download | ida-tui-a865213d04f621f3f87ad3d1873faea47709ed79.tar.gz ida-tui-a865213d04f621f3f87ad3d1873faea47709ed79.tar.xz ida-tui-a865213d04f621f3f87ad3d1873faea47709ed79.zip | |
listing: restore full-segment search load (find every match)
Revert the "search only the loaded portion" shortcut from f5aaf50 and go back to
a single, guarded background load_all before matching, so a search finds every
occurrence in the segment (not just whatever streamed in so far). The guard
(_search_loading + queued callbacks) shares ONE load across per-keystroke
updates instead of spawning/cancelling a worker each keypress.
The wedge that shortcut was meant to avoid turned out to be unrelated to the
search load: it is a pre-existing navigation bug (opening a function right after
scrolling to the bottom of another leaves the listing cursor out of range and
'/' fails to focus the search input, so typed chars leak into the view as
listing verbs, one of which is 'u'=undefine). Reproduces at 0c097f5, before any
of this work; tracked separately.
Verified in isolation: search 3.1s, matches found; search/mouse/func_banners/
listing_view/continuous_view/decomp_nav/follow_xrefs 45/0.
Diffstat (limited to 'server')
0 files changed, 0 insertions, 0 deletions
