5 ms·
After using Emacs for 10+ years, I've switched to VSCode for a really simple reason: fuzzy matching a file in a project. I've tried so many different plugins an
by rcconf 6y ago
After using Emacs for 10+ years, I've switched to VSCode for a really simple reason: fuzzy matching a file in a project. I've tried so many different plugins and hacks to get it to work, but it never did quite work. Searching for a filename either matches the wrong file, or new files that were freshly added are no longer there.
- Ixiaus 6y agoProjectile + Helm works extremely well for me, did you try those modes?
- mplanchard 6y agoThe default solution in doom emacs does this really well! I think it may be ripgrep-based, like VSCode’s, but I’m not positive.
- gen220 6y agoI’m a vim user, but I imagine there’s a similar way to do this in emacs... The secret is piping fd into fzf and opening the selected value from fzf. You can probably write a 2-liner in elisp that shells out. In my experience, this pipeline provides a faster and better matching experience than any IDE. Once I got this working, I never went back to VS Code. :)
- symlinkk 6y agoIf it’s so simple why don’t they build it into emacs?
- gen220 6y agoNot sure if this was asked sincerely, but fzf is a fairly new program, relative to emacs.
- ducktective 6y agohttps://www.youtube.com/watch?v=aXPQTesFdTI https://www.youtube.com/watch?v=aXPQTesFdTI
- wenc 6y agoWow so many people are switching to VS Code... I’ve been a vim user for 22 years and I switched over to VS Code last year but only for development. I have to grudgingly admit that it’s just a more productive environment. I do like VS Code. I still edit config files etc with vim though.
- noidesto 6y agoProjectile + helm (powered by fd) has worked wonders for me.