diff options
| author | William Carroll <wpcarro@gmail.com> | 2020-01-27T11·26+0000 |
|---|---|---|
| committer | William Carroll <wpcarro@gmail.com> | 2020-01-27T11·26+0000 |
| commit | d1fdc9fa637a46c9dcc5eb996d5c16b5c9cc074b (patch) | |
| tree | 0317a2fafc3f7fbb68dcd544c908c8880165b7cc /configs/shared/.emacs.d/wpc/packages/wpc-ui.el | |
| parent | 11d0a6c794356b62a8ff7b9c68d01cf1c0cd4d68 (diff) | |
Enable ivy-mode globally
This takes care of my outstanding TODO of understanding why something ivy was
being used and other times it wasn't. It turns out that there is a generic
`completing-read` function that many Emacs packages consume. `ivy-mode` ensures
that when that function is called it is used instead of the default Emacs
completing package.
I'm still unsure of the difference between ivy and counsel. My best guess
currently is that counsel is the narrowing framework and ivy is the integration
of the narrowing framework with `completing-read`. Swiper must be the
integration with incremental {forward,backward} search.
Diffstat (limited to 'configs/shared/.emacs.d/wpc/packages/wpc-ui.el')
| -rw-r--r-- | configs/shared/.emacs.d/wpc/packages/wpc-ui.el | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/configs/shared/.emacs.d/wpc/packages/wpc-ui.el b/configs/shared/.emacs.d/wpc/packages/wpc-ui.el index 814bfed004..6ac587c465 100644 --- a/configs/shared/.emacs.d/wpc/packages/wpc-ui.el +++ b/configs/shared/.emacs.d/wpc/packages/wpc-ui.el @@ -100,9 +100,9 @@ ;; completion framework (use-package ivy - ;; TODO: Restore behavior where `counsel' is used everywhere. :config (counsel-mode t) + (ivy-mode t) (alist/set! #'counsel-M-x "" ivy-initial-inputs-alist) ;; prefer using `helpful' variants (progn |