> AFAIU, it is because there is no common way to call a function after > ending a completing-read and/or completion-in-region call so we end up > needing a UI specific way to do so. The function records the selected > candidate, necessary for fuzzy(?) matching based on frequency and > recency ("frecency"). Hmm.. indeed we have no way in the framework to let the UI tell the completion-table or the completion-style which candidate was chosen in the end. The closest we have is the history variables (and that's only available for minibuffer completions). :-( Stefan
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4