vim-blueplanet
targets.vim
vim-blueplanet | targets.vim | |
---|---|---|
2 | 48 | |
10 | 2,515 | |
- | - | |
9.2 | 0.0 | |
about 2 months ago | 6 months ago | |
Lua | Vim Script | |
- | 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.
targets.vim
-
How to move really efficiently in Vim?
targets is nice too.
-
Two Weeks into Vim: A Transformation
The thing that has the biggest impact on me is ci”, ca”, da”, etc.. so I suggested getting used to using those.. and then you can get more pedantic with it using https://github.com/wellle/targets.vim
-
Is there a shorcut to select words in quotes including the quotes?
I do recommend getting, targets.vim https://github.com/wellle/targets.vim .. which unlocks the n(ext) and l(ast) verbs(?) ..ahhhh it’s REALLY REALLY good, I use 2in” like a lot
-
Text-object selection works forward, but not backwards, and I'm curious about that
In fact, as /u/Chillbrosaurus_Rex points out, there's a plugin, targets.vim, that expands on Vim's built-in text objects, and one of the things it does is to provide this kind of forward and reverse direction functionality.
- Installing argtextobj.vim
- How to delete inside backtick pairs, e.g JS template strings.
-
neovim plugins that have improved your workflow
Hey, I use targets.vim, how does it compare with that?
-
Leap.nvim: Neovim’s Answer to the Mouse
You might benefit from targets.vim, it works well with your thought process. It adds a bunch of new really useful editing targets (which should be builtin imo).
https://github.com/wellle/targets.vim
-
Is there a textobject for `object.` in `object.property.another`?
Thanks for the through explanation. I has seen that and considered using it in the past. Can I ask how it compares to https://github.com/wellle/targets.vim? Would you consider mini.ai a replacement or complementary?
-
Why does ci" work from elsewhere on a line, but it doesn't for ci[ , ci{ ?
This is provided by targets.vim, along with a bunch of other useful text objects.
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
nvim-treesitter-textobjects
nvim - Simple and ready configuration for neovim(nvim) with LSP. Inited with rust and go support
wilder.nvim - A more adventurous wildmenu
octo.nvim - Edit and review GitHub issues and pull requests from the comfort of your favorite editor
todoist.nvim - A todoist extension for neovim
vim-gitgutter - A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
Neovim-from-scratch - 📚 A Neovim config designed from scratch to be understandable
nvim-dap - Debug Adapter Protocol client implementation for Neovim
harpoon
paq-nvim - 🌚 Neovim package manager
nvim-tree.lua - A file explorer tree for neovim written in lua