Neovim - Telescope: a highly extendable fuzzy finder

[@darksinge]

I have used a Vim extension in VSCode for years because I'm so much more productive using my vim keybindings, but feel completely lost when leaving the safety of vscode and using neovim. I finally snapped when I started working on a large Typescript project and had to constantly wait a good 1-2 seconds for vscode to catch up to my typing. This series has been a lifesaver. These videos are blowing my mind away. I FINALLY feel like I have the tools to say goodbye to vscode! Thank you thank you thank you thank you.

[@nintF1link_Daniel]

Right now, with all vids that Chris is uploading, I think Chris is not at machine anymore, Chris is the machine

[@Jack-tc8mc]

Thanks for all videos! Helped a lot with creating my own neovim config

[@MrRhonin7]

:telescope planets no longer has moon, possibly because of this video. Really disturbing they took that approach rather than just adding pluto

[@vipulrajan83]

pluto hasn't been a planet since about 2008ish

[@xGshikamaru]

apparently telescope-media-files has a dependency over uberzug, which has gone unmaintained by its maintainer.

[@ivv3393]

I have problem with live grep not working and give me error.

[@leonwatson4002]

I ran into a problem with live grep. Installed `brew install ripgrep` and it started working hope it helps

[@fdumontmd]

You can have pluto in the list of planets; it's a config option (planets.show_pluto = true)

[@chrisatmachine]

should be true by default

[@kkh0101]

in mappings to clear input with ctrl+u add this to your mappings:i: [""] = false, -- clears input

[@cristhianjhlcom]

Finally i found a series that really helps me with my neovim configuration, thanks so much! 😁😁

[@Comradin]

Nice video! I agree that the moon has nothing to do with the planets. While the absence of Pluto is easily explained, it isn't listed as a planet anymore. It is classified as a dwarf planet and in fact there are other dwarf planets in that realm of space and some of them are even larger than Pluto is.

[@yuhaohan1451]

what desktop environment and windows manager is this?

[@abdallahalsahhar9511]

Usually when working on a big project, I'm interested in a particular directory and I just want telescope to search under that directory and nothing else, Is there a way to do that? also Is there a way to tell Telescope to search in multiple directories, like two sibling directories?

[@jesusmarcano4848]

this is a great serie of videos, realy thank you! one question, how did you configure ligatures in alacritty?

[@jesusmarcano4848]

sorry I just looked at your config files, question auto answered :)

[@hassanhafiz44]

On Mac things work but I get some errors, like didn't send parameters to the function etc.

[@tarikzaki5442]

File Preview is not showing by default, anyone knows what's the cause of this issue??

[@startup-streak]

For me, telescope file search is too slow when used in bigger projects. I also have node_modules and a couple of other things ignored in the settings, but they appear for like a blink of an eye and this bothers me a lot. For those reasons, I went back to VS Code with the Neovim extension, and I'm so familiar with the shortcuts that I'm as fast or even faster than Neovim. But I miss configuring NVIM so much that I'm tempted to go back to Neovim. Do you also face the slow file search problem?

[@AWatProduction]

When did you last experiment with telescope? There was a big update about a year ago, where telescope finally became async, which improved performance a lot. Alternatively, you could also try out fzf, which should be faster.

[@startup-streak]

​@@AWatProduction The last time I tried was indeed last year. I will try to update it and see if it has improved. Thanks for your suggestion.

[@qwerty-or1yg]

@@startup-streak how did it go?

[@greyshopleskin2315]

Yeah fzf should be faster. But you can use it with telescope. There should be a fzf picker for telescope

[@zinda__bad]

there's a show_pluto flag for in the planet command options

[@paulogsf76]

@3:50 because of Lua, of course

[@rubempacelli6815]

Amazing!!! Thank very much!

[@lethanhan9084]

How are you able to preview the planets? Mine just says it's a binary and it cant be viewed

[@supportpixelstorm7319]

lol, planets.

[@themohmand]

How do you get that Telescope icon right behind the search bar?

[@mitchbet]

Does anyone know how to navigate the list when searching files (without using arrow keys)? According to the key display in the top right of the video, he's using Ctrl+k. But when I do that, I just get "^k"'s in my search box

[@db5552]

What window manager is he using? Thanks.

[@markas85]

How do you get such scrollable completion dropdown in command line?

[@sidtronics]

press Tab on command line

[@shaffoudhi]

Thankk you for this serie, it's really helping me a lot! I was wondering where can I find your current terminal colorscheme ?

[@akshitthakur3842]

Live grep doesn't work anyone?

[@f.b.t.3769]

Same for me. Solved the following way (don't know if this will work for anybody else): 1. Added a plugin: use "BurntSushi/ripgrep" 2. Installed rg (ripgrep), since it was missing in my Manjaro installation

[@lucasmarinzeck7028]

@@f.b.t.3769 It worked here, i just added to my arch dist. Thanks

[@JalukOne]

@@f.b.t.3769 thanks bro Fedora 36 > sudo dnf install ripgrep

[@cpuccino]

First of all, thanks for this awesome series man. This the the first time I've configured neovim in lua, and it's going pretty awesome so far. Just curious if you've ever talked about the packer_compiled file yet? I think I remember you mentioned it in an earlier tutorial, I might have missed it though. Also curious if there's a way to package the neovim version along with it's dependencies and plugins? I'm running into some issues where newer versions of neovim breaks when used with packer - the deps are installed in a different manner so I have to specify which is a dependency of which. I don't expect things to stabilize any time soon since everyone is just starting to implement their plugins, but if there's a way to containerize it I guess, without specifying the hash for each plugin and the neovim version?? that would be pretty cool.

[@munzutai]

About the packer_compiled file: He talked about it in the video about plugins: kzbin.info/www/bejne/nZXCqJSmebFjjJI

[@yohanntumpling7721]

When doing an update with nvim or your packages, you can take a look at the command :checkhealth, and :h deprecated too I guess. As @Munzu said, Chris maid a video about packer.nvim, you can specify required packages if needed. Otherwise, I am not aware about a way to containerize it 😕

[@alexjak19]

Now that you have tried both fzf and telescope for neovim, which one is better? If I had to chose one fuzzy finder for neovim, which would you recommend? Some googling gave me that telescope is more configurable, while fzf is faster. Your experience?

[@someone-worker]

How is telescope detect a root or top folder?

[@alt-chan-]

use vim-rooter extension, it automatically sets all your files cwd (current working directory) to the detected root project folder

[@izitorg]

b5833a6 fix: move the moon behind show_moon option and update documentation (#2072) (#2079) lol

[@officialmarcv]

hey neovim peeps. You guys might like my electronic music!

[@paracelsus_rose6934]

Was anyone able to get keymap("n", "fp", ":Telescope projects", opts) working? Been trying to figure out how for a day now. Any help would be huge. Appreciate the videos beyond chris.

[@Torvating]

The way you pronounce Überzeug is so funny XD (It's a german word)

[@mentalmarvin]

Ybertsoyg?

[@jcbritobr]

Why people cant just show how things works without configuration?

[@ipekposet8639]

Almost 777777777777777777777

[@epistemocrat]

oh yeah of course, a fuzzy finder.... .... tha fuck is a fuzzy finder?