dotfiles
vim-commentary
Our great sponsors
dotfiles | vim-commentary | |
---|---|---|
18 | 51 | |
63 | 5,687 | |
- | - | |
9.5 | 2.5 | |
19 days ago | 18 days ago | |
Vim Script | 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.
dotfiles
-
Whats Your VIMRC Setup For 2023?
I've just noticed my vimrc right now has exactly 600 lines... not counting the rest of files of course
-
any reference about plugins (from github preference) for wforrite using Markdown
I only really needed to set few settings + extend syntax folding to comfortably write Markdown
-
How to manage Vims dot files (version >8.2), if there are complete plugins inside .vim?
And I don't know anything about stow as I just use my own simple install script
-
hjkl vs jkl; - is it crazy to want to switch to the latter?
I have public GitHub repository with all my dotfiles under MIT license. On private machine I make changes to them; on work machine, I just clone/pull that public repo. Eventual changes done during work time I just remember to implement at home again.
-
Little vim window to paste to clipboard
Like this one I have in my dotfiles?
-
Share your vimrc with comments what you intended the changes for. Here's mine.
Well, I'm not gonna comment every tiny bit (as it's usually obvious from the code already), but if you are interested in reading others configs: my vimrc alongside the rest of my Vim configuration
-
What is your setup for developing in C?
Arch Linux (or WSL2 on Windows)
-
My Self-starting vim configuration
You start like this and end like this ;)
-
Should I use vanilla Vim instead of Vscode?
Read configs of more experienced users (here's Jorengarenar's, for example)
-
Language server protocol
I use vim-lsc (my config)
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?
ccls - C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
nerdcommenter - Vim plugin for intensely nerdy commenting powers
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nvim-comment - A comment toggler for Neovim, written in Lua
targets.vim - Vim plugin that provides additional text objects
tcomment_vim - An extensible & universal comment vim-plugin that also handles embedded filetypes
nvim-lspinstall - Provides the missing :LspInstall for nvim-lspconfig
kommentary - Neovim commenting plugin, written in lua.
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
vim-lsp - async language server protocol plugin for vim and neovim