vim-blueplanet
telescope.nvim
vim-blueplanet | telescope.nvim | |
---|---|---|
2 | 322 | |
10 | 14,191 | |
- | 4.4% | |
9.2 | 9.1 | |
about 2 months ago | 7 days ago | |
Lua | Lua | |
- | 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.
vim-blueplanet
-
FAVOURITE PLUGINS
To my knowledge vim-test has no out-of-the-box configuration for TypeScript. I forgot why. Anyway here is my configuration that adds mocha and jest as testers for TypeScript. Though it is mostly based on the existing JavaScript support of vim-test it adds some extra support for Vue testing and project local binaries. Finally ensure you enabled these testers in the vim-test configuration (g:test#custom_runners).
-
Do you use a single init.lua/.vim file or an organized directory structure? Just curious :)
You could take a look here at my configuration. Not sure if that is helpful. You should first read up native packages as it has been linked above. I don't explain the little sneaks and features here. But in its core I put file and directory structure above everything else. I barely import anything manually but fully rely on automated mechanisms. I use lazy loading heavily. I use a mix of .vim and .lua files depending on its content and which language is easier (e.g. mappings are simpler in VimL. In result I have hundreds of files in my configuration. My everything follows a structure. With tools like fzf or telescope it is too easy to open the file you search for. It's basically no overhead. It would be more work to find what I search for if I would have less files. Finally this keeps everything incredibly independent. I can add, change and especially remove thing very easily as most things are very separated and independent. I want to remove a plugin, all its config, mappings, highlights, signs, ... I just remove one directory. Nothing more and nothing less. Clean cut. If I want a plugin and everything around it (copy-paste from above) to be lazy loaded it just works out-of-the-box. It's very simple and elegant. In my opinion. Though you can easily dislike it if you don't agree that strong with the approach it's fundamental arguments.
telescope.nvim
-
Level Up Your Dev Workflow: Conquer Web Development with a Blazing Fast Neovim Setup (Part 1)
for telescope.nvim (optional) live grep: ripgrep find files: fd
-
Neovim: creating keymaps in lua
Here we have a configuration for telescope.nvim, a very popular fuzzy finder.
- What is the reason people 'touch' a file before writing it?
-
What are the plugins/settings to be able to view individual file or folder contents while scrolling through files or folders?
EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim
-
What are some plugins that you can't live without?
Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)
-
Telescope.nvim: Fully Customizable Layout!
Just landed on Telescope.nvim: https://github.com/nvim-telescope/telescope.nvim/pull/2572
-
telescope-sg: a new way to do structural search in neovim
This extension allows you to use the power of ast-grep to find code patterns in your editor, using the familiar and awesome interface of telescope.nvim.
- Telescope.nvim: Find, Filter, Preview, Pick. All Lua, All the Time
-
Benchmarking some of my favourite neovim plugins over time
telescope.nvim
-
Why does vim.lsp.buf.definition open this window instead of taking me to the styles file (the same with tsserver and Volar)?
My solution is using telescope.nvim with lsp extension, and map the vim.lsp.buf.definition keybinding to telescope one https://github.com/nvim-telescope/telescope.nvim
What are some alternatives?
material.nvim - :trident: Material colorscheme for NeoVim written in Lua with built-in support for native LSP, TreeSitter and many more plugins
fzf.vim - fzf :heart: vim
nvim - Simple and ready configuration for neovim(nvim) with LSP. Inited with rust and go support
fzf-lua - Improved fzf.vim written in lua
octo.nvim - Edit and review GitHub issues and pull requests from the comfort of your favorite editor
vim-fugitive - fugitive.vim: A Git wrapper so awesome, it should be illegal
vim-gitgutter - A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
telescope-fzf-native.nvim - FZF sorter for telescope written in c
nvim-dap - Debug Adapter Protocol client implementation for Neovim
Visual Studio Code - Visual Studio Code
nvim-tree.lua - A file explorer tree for neovim written in lua
fd - A simple, fast and user-friendly alternative to 'find'