fd
telescope.nvim
fd | telescope.nvim | |
---|---|---|
183 | 332 | |
34,040 | 15,919 | |
- | 2.6% | |
8.8 | 9.1 | |
6 days ago | 10 days ago | |
Rust | Lua | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fd
-
One-Liner for Finding Typos
However, if it catches too many typos in changelogs/README instead of the actual code, try using the fd command to specify file extensions or exclude directories. For example, the following command searches only for .cr files and excludes the lib directory:
-
Command Line Tools I Like (2022)
Oh right, we didn't know this, most of the tools install guides have nix-env like fd, lychee, gtrash, etc and others we listed which we just use for installation.
https://github.com/lycheeverse/lychee?tab=readme-ov-file#nix...
https://github.com/sharkdp/fd?tab=readme-ov-file#on-nixos--v...
https://github.com/umlx5h/gtrash?tab=readme-ov-file#nixpkgs-...
- fd - A simple, fast and user-friendly alternative to 'find'
- Techniques I Use to Create a Great User Experience for Shell Scripts
-
The Modern CLI Renaissance
Disagree all you want, you still shouldn't be surprised people aren't expecting this
fd: https://github.com/sharkdp/fd/issues?q=gitignore+
And I stand by it is strictly better for the __default__ to be unfiltered. This is what people expect in general.
> tailored for the common use cases today.
- Show HN: Vomitorium – all of your project in 1 text file
-
Eza: A modern, maintained replacement for ls
NOTE OF WARNING:
BY DEFAULT these ignores anything included in your `.gitignore` folder. So if you think it is a straight find replacement, you'll likely be surprised. fd discussion here[0]
Just make sure that when recommending people these tools that this is clear because if they don't read the docs (lol who does) they'll miss this part.
This is a pet peeve of mine. I wish the people that make these replacement coreutils (and others) would leave the defaults as very similar to the original tool. I do really like the new functionalities but if you market it as "an alternative" ("It is a simple, fast and user-friendly alternative to find") then they should respect the defaults of the original because it reduces new user surprise. I mean aliases exist... So it is better to have in your ~/.${SHELL##*/}rc file to have `alias fd='fd --ignore'` than `alias fd='fd --no-ignore'`.
Side note/pro tip: use `\command` if you want to use an unaliased version. An example of this is that I have `alias grep='grep --color=always --no-messages --binary-files=without-match` but this can sometimes be problematic because the color option can change the character representation so if you pipe this into `curl` you will get errors. This is not the case in all piping, but it is a shocking and confusing experience when you first encounter it. You can validate this by `echo "Hello world" | \grep --color=always "Hello" | hexdump` and then `!!:s^always^never`
[0] https://github.com/sharkdp/fd/issues/612
-
How to Fuzzy Search: Finding File Names and Contents using Bash Scripting and Commandline Tools
1. fd command
-
Customizing Your Lazyvim Setup for Personal Preferences
find files: fd
-
🐚🦀Shell Commands Rewritten in Rust
fd
telescope.nvim
- telescope.nvim: Find, Filter, Preview, Pick. All Lua, All the Time
-
Neovim for beginners
I personally use Telescope as my fuzzy finder. Again, here's the docs for telescope and here's my config:
-
Don't use “dependencies” in lazy.nvim
For example, telescope.nvim, that is also one of the most popular plugins, has a note in README that describes the way to use with lazy.nvim.
-
(Youtube blogpost) Building Tree Link app with Svelte and Tailwind CSS
for telescope.nvim (optional) live grep: ripgrep find files: fd
-
I Made an Extended Version of Vimtutor – Introducing Vimtutor Sequel
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 productivity 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...
-
PowerToys Run: extensible quick launcher for power users
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)
-
PowerShell Development in Neovim
Quick file nav: telescope
-
Ultimate Neovim Setup Guide: lazy.nvim Plugin Manager
nvim-telescope/telescope.nvim: Highly extendable fuzzy finder over lists.
-
I a Avid Vim User, Finally Migrated to Neovim! How does it work, what do I gain from it?
Fzf is good, but as I said above, Neovim offers a lot of new plugins with new implementations. And among them, a supercharged fzf: Telescope! It allows you to search for files, and even text patterns, while offering an interface with file previews! A must have , quite simply.
-
My Flow and Productivity has Improved with the Simplicity of Neovim
I don't think many Neovim users could live without Telescope. Maintained by TJ DeVries, this is a fuzzy find, LSP integrator, and so many other things. I use it constantly to find open buffers, grep my codebase, look through Git logs, and pull up references. The image below shows how I'm using it to find Workspace Symbols.
What are some alternatives?
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
fzf.vim - fzf :heart: vim
fzf - :cherry_blossom: A command-line fuzzy finder
fzf-lua - Improved fzf.vim written in lua
exa - A modern replacement for ‘ls’.
vim-fugitive - fugitive.vim: A Git wrapper so awesome, it should be illegal
skim - Fuzzy Finder in rust!
telescope-fzf-native.nvim - FZF sorter for telescope written in c
vim-grepper - :space_invader: Helps you win at grep.
Visual Studio Code - Visual Studio Code
watchexec - Executes commands in response to file modifications —— Maintenance status: on hold. I have no time for OSS currently; back late 2024.
nvim-tree.lua - A file explorer tree for neovim written in lua