HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nvim-telescope
telescope.nvim
Lua2021–2025
nvim-telescope / telescope.nvim

telescope.nvim

Find, Filter, Preview, Pick. All lua, all the time.

20Distinct people
23Mentions
0Explicit recommenders
19.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Find, Filter, Preview, Pick. All lua, all the time.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year23 dated mentions

Observed mentions: 2021-04-15 04:38:58 UTC to 2025-02-26 09:05:15 UTC.

02468102021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC927
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC413
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

23 sources
I too share your sentiment about VS Code. Its extension API[0] is extensive and approachable, often with examples[1] for each API. Just a small anecdote: At work, I found it frustrating not being able to quickly locate where views for Django API endpoints were, so I wrote a simple extension that took the output of django-extensions' show_urls, parsed it, and displayed a quick pick list of all API endpoints, upon which selecting an endpoint would open the file and reveal the exact line in which the view for it was defined. Implementing this did not take much effort (in fact, TypeScript and JSDoc make everything a lot simpler as it's clear to see what each function in the API does and what arguments they accept), and now this is something I use almost every day and greatly improves my satisfaction when navigating the codebase if not my prod
Read the rest
uctivity in general. I have tried looking into implementing something similar in Neovim and came across the API for telescope.nvim[2], but found it a lot less intuitive to use. I do think Vim/Neovim shines when it comes to text manipulation and extensions built around it, but when it comes to more complex UI that often deals a lot more with graphical elements (e.g. tree views, hover text, notifications), it's hard to beat VS Code. [0]: https://code.visualstudio.com/api/references/vscode-api [1]: https://github.com/microsoft/vscode-extension-samples [2]: https://github.com/nvim-telescope/telescope.nvim/blob/master...
In I Made an Extended Version of Vimtutor – Introducing Vimtutor Sequel
This is indeed the main thing I use Spotlight/Alfred for on MacOS: I want to go to the window for this app, regardless of what virtual desktop it's on, and I don't want to hunt for it. I use that "text-based finder" approach _everywhere_: - Telescope in NeoVim (https://github.com/nvim-telescope/telescope.nvim) - The "Actions" (Cmd-Shift-A) and "Find Anything" (Shift-Shift) shortcuts in IntelliJ - Alfred on my work macbook - KRunner on my personal linux laptop (with KDE) - The `t` shortcut on github to jump to files - the `!` "bang" shortcuts on DuckDuckGo I have the hardcore vim brainworms of "don't make me touch the mouse", and in _spades_ if that mouse is a laptop trackpad. I haven't found a good equivalent on Windows, not because they don't exist, but because they're all focused on trying to do everything _bu
Read the rest
t_ launch fast and swap to the application I want...so they wind up taking 4-5 seconds between "hit keyboard shortcut that invokes it" and "start typing", because they're busy indexing the registry or my recycle bin or whatever.
In PowerToys Run: extensible quick launcher for power users
I actually find neovim to work better than VSCode when dealing with large codebases. Telescope [1] based fuzzy searching makes it easy to find stuff in a codebase and harpoon [2] can then be used to short list some important files and quickly navigate to them. There's definitely a bit of a learning curve and setting up your own keybindings before you feel like you're used to it. [1] https://github.com/nvim-telescope/telescope.nvim [2] https://github.com/ThePrimeagen/harpoon
In The Hammerhead Worm
Telescope[1] is pretty central to navigation in Neovim these days. Think Ctrl-P in VSCode, but for any entity in your editor or workspace, not just files. Files in workspace, buffers (open files), ripgrep results, LSP symbols / references, etc. Also provides a live preview of search results without having to open them. Plus easily add results to your quickfix list, making large-scale edits easy. [1]:https://github.com/nvim-telescope/telescope.nvim
In AstroNvim is an aesthetic and feature-rich Neovim config
I use a lot of them, many specific to my work, but here are some of the ones that I think will most improve the quality of life for most developers. - For a plug-in manager I user packer - For file/text search I recommend telescope (https://github.com/nvim-telescope/telescope.nvim) - Copilot (https://github.com/github/copilot.vim) - Nerd tree for file browsing (https://github.com/preservim/nerdtree) - commentary for commenting (https://github.com/tpope/vim-commentary) - ALE for linting (https://github.com/dense-analysis/ale) - Mason for installing LSP servers (https://github.com/williamboman/mason.nvim) Once you have the proper tooling in place you can do pretty much everything in vim that you are doing in vs code or intelliJ. I've just started using it for most of my dev work recently and I have found ThePrimeagen's youtube videos on vim
Read the rest
to be a great resource. Series on using vim as you editor (https://www.youtube.com/playlist?list=PLm323Lc7iSW_wuxqmKx_x...) Introduction to setting up your vim configuration (https://www.youtube.com/watch?v=x2QJYq4IX6M&t=512s) I recommend giving it a try. The process of learning it all was fun, and as you may have heard you can eventually get pretty quick using Vim.
In Ask HN: Is it still possible to live in a terminal?
> I’m finding myself doubting the amount of time I’m dedicating to configuring/practicing vim If it's not fun, then it's probably not worth it. It really depends on what VIM can do to improve your current workflow. So, you may need to drop the VSCode mindset while you start using VIM. > but now that I’m trying to navigate medium/large projects, I actually have trouble navigating large projects in VSCode. The buffer, tab, window model that Vim uses makes more sense to me (but it's unique to VIM afaik, so it may be jarring at first). Combine that with a fuzzy finder[1] and it allows: - rip-grep to search for files with text / file names - Searching through currently currently opened buffers Whenever I have to use VSCode (mainly for the live share feature, I find myself pretty lost with VSCode's tab based interface (I usually end up with l
Read the rest
ike 20 tabs cluttering my workspace, and tabs are local to a split, which is jarring for me). > the vim endgame looks like It never _really_ ends. Some VIM features that I miss when I use another editor are: - Really nice integration with terminal commands. One thing that I do very often is copy the name of the current file: `!echo % | xclip -sel clip` so I can use the filename as an argument in a terminal split (running tests for example) - Filters (`:help !`) so I can pass parts of a file in to a program that accepts standard input. Example: `'<,'>!jq` to prettify bits of JSON. - Global commands and macros. VSCode vim supports them, but I've noticed that they can run pretty slowly. - The buffer, tab, window, model (probably the biggest one I miss when I start using VSCode) For LSP support, I've tried to migrate to neovim's native LSP tools, but I still find COC to be a lot more intuitive. You should feel right at home with it since a lot of the plugins are similar to their VSCode counterpart. If you'd like a really general and guided tour of VIM, I'd recommend picking up Practial Vim[2] It really helped me understand the workflow a bit more. Approaching VIM with the mindset of another editor wont give you all the benefits of using VIM. Though, if the workflow doesn't click, then that's not a big deal. You can always go back to VSCode. [1] https://github.com/Shougo/denite.nvim (many people use Telescope: https://github.com/nvim-telescope/telescope.nvim) [2] https://www.amazon.com/Practical-Vim-Thought-Pragmatic-Progr...
In Ask HN: Is switching from VSCode to Vim worth it?

Showing the 15 most recent of 23 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.