Dotfiles
denite.nvim
Our great sponsors
| Dotfiles | denite.nvim | |
|---|---|---|
| 9 | 3 | |
| 76 | 2,054 | |
| - | - | |
| 3.0 | 4.3 | |
| 11 months ago | about 1 month ago | |
| Lua | Python | |
| MIT License | GNU General Public License v3.0 or later |
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.
Dotfiles
-
A config using fennel .
Makefile -> https://github.com/beauwilliams/Dotfiles/commit/c10dad3ea6c126ac8be5afd29d1bd942b07fc16d
-
Command then Mapping pattern
Commands Mappings
- Really missing vim's :sh
-
NvimTree completely stopped working
See the commit I made to support the new update here
-
VSCode user thinking about switching.
I've attempted to document my dotfiles as I go. So hopefully this comes in use for you!
-
Looking for a neat Neovim config for wilder.nvim
AFAIK I just pasted the entire config right into a file in my /plugin directory. Works great. https://github.com/beauwilliams/Dotfiles/blob/master/Vim/nvim/plugin/wilder.vim
-
Recommend config repos that I can use to structure my config?
If you want some dotfiles that are well documented, check these out
-
Why use splits?
This auto-resizing function was a piece of vimscript originally, you can find that in my init.vim line 434
-
How can I improve my vim productivity?
See my vimrc for an example of a well documented rc. This one is designed so that other people can quickly pick up from my own configs :) Vim Config
denite.nvim
-
Ask HN: Is switching from VSCode to Vim worth it?
- 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)
-
Looking for a neat Neovim config for wilder.nvim
cpsm doesn't use ctrlp.vim, it's a matcher initially targeted at ctrlp, but has since been adapted for use in other fuzzy matching plugins, e.g. denite.nvim
-
Converting from an IDE, biggest issue is navigating between files efficiently
Highly recommend Denite. It gives you a graphical way to easily switch between buffers. It's super intuitive and fast.
What are some alternatives?
wilder.nvim - A more adventurous wildmenu
fzf.vim - fzf :heart: vim
focus.nvim - Auto-Focusing and Auto-Resizing Splits/Windows for Neovim written in Lua. A full suite of window management enhancements. Vim splits on steroids!
vim-projectionist - projectionist.vim: Granular project configuration
nvim-tree.lua - A file explorer tree for neovim written in lua
vim-vinegar - vinegar.vim: Combine with netrw to create a delicious salad dressing
dotfiles - The best and strongest dotfiles. Editor: Neovim; Shell: zsh(zinit, powerlevel10k); Terminal: wezterm; Desktop: hyprland/sway, ulauncher, dunst; OS: ArchLinux (Ubuntu/Fedora/CentOS)
vim-autoimport - A vim plugin for adding import statements (for python and more) without LSP
telescope-fzy-native.nvim - FZY style sorter that is compiled
nvim-treesitter-textobjects
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.