From d1fdc9fa637a46c9dcc5eb996d5c16b5c9cc074b Mon Sep 17 00:00:00 2001 From: William Carroll Date: Mon, 27 Jan 2020 11:26:10 +0000 Subject: 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. --- configs/shared/.emacs.d/wpc/packages/wpc-ui.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'configs') diff --git a/configs/shared/.emacs.d/wpc/packages/wpc-ui.el b/configs/shared/.emacs.d/wpc/packages/wpc-ui.el index 814bfed004c0..6ac587c46567 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 -- cgit 1.4.1