diff options
| author | João Távora | 2019-10-31 20:19:35 +0000 |
|---|---|---|
| committer | João Távora | 2019-11-02 02:35:45 +0000 |
| commit | 0bb97ad8b89af91e296ea791f34b46963323ce7a (patch) | |
| tree | a6c708979032da419350fbe6f8f8bbd64ff6c149 /src/bytecode.c | |
| parent | 88f193ed05649b8c622867b8b2623b8cb08fdc96 (diff) | |
| download | emacs-0bb97ad8b89af91e296ea791f34b46963323ce7a.tar.gz emacs-0bb97ad8b89af91e296ea791f34b46963323ce7a.zip | |
Fix icomplete-force-complete-and-exit for no-input situations
If there is no minibuffer input, but the user has already cycled some
pre-calculated completions, we should be calling
minibuffer-force-complete-and-exit instead of
minibuffer-complete-and-exit. The former is guaranteed to be fast in
this situation and yields the desired "selected" completion, while the
latter will just give us the default, ignoring all the cycling of
icomplete-{forward|backward}-completions.
* lisp/icomplete.el (icomplete-force-complete-and-exit): Add
comments and fix for empty input but some completions calculated.
Diffstat (limited to 'src/bytecode.c')
0 files changed, 0 insertions, 0 deletions