dotfiles
vim-commentary
dotfiles | vim-commentary | |
---|---|---|
21 | 51 | |
48 | 5,732 | |
- | - | |
9.0 | 3.4 | |
2 days ago | about 2 months ago | |
Shell | Vim Script | |
- | - |
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
-
How do you organise your snippets?
You put your snippets in a lua file, like here (with syntax according to the luasnip documentation) and invoke such file somewhere in your configuration so that it's required (i. e. "loaded").
-
Function: Attempt to call global 'xxx' (a nil value)
Without knowing your precise folder structure and where you are requiring what is a little hard to understand. However, I do something similar but I have a functions file in my lua folder (without any nested subfolder) and I just require all the .lua stuff in my init.lua here.
-
Select filetype based on Filename?
Some examples here, but as other users suggested it's vim.filetype.add().
-
which snippet engine are you using?
You can find my snippets here: to be honest they are rather simple, so creating such doesn't take me too long. In general I would say either style is fine (or equally ugly :p).
-
I refactored my lua structure and have lost some UI styling ?
Whilst at the moment I do not have time to go through your config, this is my noice config and my lsp. You can copy&paste, I have borders set and normal highlight window. It works, so just copy it and then work back till you add yours.
-
lsp handlers textDocument issue after update Noice
If it can be of help this is my noice configuration and lsp setup. It is working fine for me and I tested updating everything right now.
-
TreeSitter Code Highlight
See examples here.
-
minimal config for sessions management
Here - it is just a config file with a few functions: use it as inspiration! The code is probably not optimised yet (I just got it working and I wanted to share, do let me know if you can make it better): mappings to operate
-
your favorite cheatsheet app ?
I use navi and I am very satisfied: it's very easy to create your own cheatsheets, see for instance what I do here.
-
...and now gh-i to search for issues interactively!
It is macOS with iTerm2 and zsh as shell. The DE is the standard one that comes pre-installed, I didn't make changes; you can find my configurations here
vim-commentary
- html css commenting things out
-
A very simple way to comment/uncomment lines and visual selections.
Also, tpope/vim-commentary
-
Plugin for comments
https://github.com/tpope/vim-commentary does what you expect!
-
My Solution to Block Comments
I've replaced most of my custom maps for commenting with tpope's commentary plugin. It's a great plugin. However, I wasn't happy with the lack of multi-line/block comment abilities so I created some maps to compliment the commentary plugin. Here are some maps that can be used with autocmd, FileType and for JavaScript comments.
-
Vim plugin for wrapping/unwrapping line comments
commentary.vim + :h gq?
-
Favorite vimrc configs for coding?
Having said this, there are some useful language independent extensions: jiangmiao/auto-pairs, tpope/vim-commentary, preservim/tagbar, junegunn/vim-peekaboo
-
Neovim config from scratch (Part II)
vim-commentary comment code comfortably with motions and visual selections alike.
-
Anybody have a keymap/config for folding and unfolding a block of code? Also how to comment lines of selected code?
With a plugin like vim-commentary or comment.nvim
-
Colored statusline doesn't load at start; I need to manually source $MYVIMRC
" This file contains common and basic plugins too essential not to include " See https://github.com/junegunn/vim-plug/wiki/tutorial " Auto install vim-plug (if not already installed) if empty(glob('~/.config/nvim/autoload/plug.vim')) silent !curl -fLo ~/.config/nvim/autoload/plug.vim --create-dirs \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim autocmd VimEnter * PlugInstall endif " Run PlugInstall if there are missing plugins autocmd VimEnter * if len(filter(values(g:plugs), '!isdirectory(v:val.dir)')) \| PlugInstall --sync | source $MYVIMRC \| endif " enable Vim-Plug: call plug#begin('~/.config/nvim/plugged') " Install/update plugins Plug 'https://github.com/tpope/vim-commentary.git' Plug 'https://github.com/morhetz/gruvbox' " Better C/C++ syntax highlighting; Plug 'https://github.com/jackguo380/vim-lsp-cxx-highlight' call plug#end() "---------- Basic configs ---------------------------------------------------- autocmd vimenter * ++nested colorscheme gruvbox " Enable transparent background let g:gruvbox_transparent_bg = 1
-
Neovim config from scratch (Part I)
Commentary Tim pope's comment plugin
What are some alternatives?
noice.nvim - 💥 Highly experimental plugin that completely replaces the UI for messages, cmdline and the popupmenu.
nerdcommenter - Vim plugin for intensely nerdy commenting powers
navi - An interactive cheatsheet tool for the command-line
nvim-comment - A comment toggler for Neovim, written in Lua
indent-blankline.nvim - Indent guides for Neovim
tcomment_vim - An extensible & universal comment vim-plugin that also handles embedded filetypes
vimspector - vimspector - A multi-language debugging system for Vim
kommentary - Neovim commenting plugin, written in lua.
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
dotfiles - My Dotfiles
vim-lsp - async language server protocol plugin for vim and neovim