nvim-telescope

telescope.nvim

Lua2021–2025

nvim-telescope / telescope.nvim

telescope.nvim

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

Developer Tools

Explore on GitHub Read Hacker News discussions

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:00:59 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.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	9	2	7
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	5	0	5
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	4	1	3
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	4	1	3
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	1	0	1

What Hacker News says

5 sources

Zizizizz·Dec 26, 2022

https://github.com/jesseduffield/lazygit (My favourite git interface. Can be used in neovim as well) https://github.com/nvim-telescope/telescope.nvim (Fuzzy finder plugin that uses ripgrep and fzf) https://github.com/ajeetdsouza/zoxide Smart replacement for `cd` https://github.com/be5invis/Iosevka My favourite font for coding, it's width lets me fit more text on the screen

In Ask HN: Products/Services you swear by – Dec. 2022

lizardking·Oct 15, 2022

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?

asdfqweqe12·Sep 30, 2022

Telescope is must have for me. https://github.com/nvim-telescope/telescope.nvim

In Neovim 0.8 Released

galoisscobi·Sep 10, 2022

I have a vi oriented solution. I use neovim+vimwiki(in markdown mode)+telescope[0] and that setup has been working well for me. I don’t do tags per se but telescope should be able to search those. [0] https://github.com/nvim-telescope/telescope.nvim

In Evolving my note-taking processes

pcvonz·Mar 29, 2022

> 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?