|
From: | Andrew Schwartzmeyer |
Subject: | bug#42101: icomplete-fido-ret doesn't always use minibuffer-default when input is empty |
Date: | Fri, 3 Jul 2020 22:22:41 -0700 |
I’m sorry so João, I had sent you a repro last week, but it again didn’t go through. It appears I have to leave TLS-sending guarantees disabled because the debbugs mail server is insecurely configured (for others who may be reading but offering no useful input, this is a security issue that does not exist with GitHub or other similar software). Perhaps we should move to emacs-devel which at least accepts email sent over TLS. Anyway, I can repro this in emacs -Q with: (defun fido-mode+ () (setq-local completion-styles '(basic))) (add-hook 'icomplete-minibuffer-setup-hook #'fido-mode+) (fido-mode) Basically (heh) this happens if the “basic” completion-style is used (or “partial-completion” or “substring” or any combination including one of those styles). It only doesn’t repro if “flex” is used by itself (the default for fido-mode, but should be able to be overridden). This also repros with icomplete-mode if “icomplete-show-matches-on-no-input” is t, as in: (defun fido-mode+ () (setq-local completion-styles '(basic) icomplete-show-matches-on-no-input t)) (add-hook 'icomplete-minibuffer-setup-hook #'fido-mode+) (icomplete-mode) Which explains why it’s readily apparent in fido-mode, where that’s set to t already. Unfortunately, I still have no clue how to fix it. I would appreciate your help! Being able to use the default styles in addition to flex makes the fido-mode experience smoother, because they return defaults for no input much faster, I find them to be more predictable, and it’s when they fail that flex tends to shine most. Thanks, Andy
|
[Prev in Thread] | Current Thread | [Next in Thread] |