Doom-emacs: Fuzzy search for projectile find file

Created on 10 Jul 2019  路  4Comments  路  Source: hlissner/doom-emacs

I'm currently in the process of switching over to Doom from Spacemacs, and one of the most important thing for me is fuzzy matching when switching files using find-file.

How can I configure doom to have the same behavior as I had in spacemacs.
In spacemacs:
image

This does not even match in doom:
image

I have to write this in order to find the file:
image

question elisp resolved

Most helpful comment

You have two options:

Disable Ivy, enable helm and fuzzy search:

In your doom! block in ~/.doom.d/init.el:

  1. Uncomment :completion helm
  2. Enable the +fuzzy flag: :completion (helm +fuzzy)
  3. Comment :completion ivy
  4. Run ~/.emacs.d/bin/doom refresh
  5. Restart Emacs.

Or enable fuzzy support for ivy

   :completion
-  ivy
+  (ivy +fuzzy +prescient)

Then run ~/.emacs.d/bin/doom refresh and restart Emacs.

All 4 comments

You have two options:

Disable Ivy, enable helm and fuzzy search:

In your doom! block in ~/.doom.d/init.el:

  1. Uncomment :completion helm
  2. Enable the +fuzzy flag: :completion (helm +fuzzy)
  3. Comment :completion ivy
  4. Run ~/.emacs.d/bin/doom refresh
  5. Restart Emacs.

Or enable fuzzy support for ivy

   :completion
-  ivy
+  (ivy +fuzzy +prescient)

Then run ~/.emacs.d/bin/doom refresh and restart Emacs.

Thanks, works great!
Quick question though, is there a way to customize the colors when searching?
image

I would note you don't _need_ +prescient - and I've actually found it to be considerably worse than the default.

The relevant faces are:

    ivy-minibuffer-match-face-1
    ivy-minibuffer-match-face-2
    ivy-minibuffer-match-face-3
    ivy-minibuffer-match-face-4

You can look up their definition with SPC h F. A simple way to change them is with custom-set-faces!:

(custom-set-faces!
  '(ivy-minibuffer-match-face-1 :background "#000000")
  '(ivy-minibuffer-match-face-2 :background "#0000FF")
  ...)

In any case, I'll consider the original issue resolved.

Was this page helpful?
0 / 5 - 0 ratings