vim-easy-align VS vim-gutentags

As part of my journey to moving to Lua, I'm trying to move from vim-easy-align to mini.align.

Not exactly what you are asking for, but table formatting is usually enough with general purpose align plugins: - mini.align - junegunn/vim-easy-align - godlygeek/tabular

For aligning text table data I usually used this plugin

I am happy to announce the release of mini.align - module of mini.nvim for aligning text interactively (with or without live preview). This is mostly designed after junegunn/vim-easy-align, but is implemented in Lua and has slightly different alignment specification and user interaction lifecycle.

call plug#begin() " The default plugin directory will be as follows: " - Vim (Linux/macOS): '~/.vim/plugged' " - Vim (Windows): '~/vimfiles/plugged' " - Neovim (Linux/macOS/Windows): stdpath('data') . '/plugged' " You can specify a custom plugin directory by passing it as the argument " - e.g. `call plug#begin('~/.vim/plugged')` " - Avoid using standard Vim directory names like 'plugin' " Make sure you use single quotes " Shorthand notation; fetches https://github.com/junegunn/vim-easy-align Plug 'junegunn/vim-easy-align' " Any valid git URL is allowed Plug 'https://github.com/junegunn/vim-github-dashboard.git' " Multiple Plug commands can be written in a single line using | separators Plug 'SirVer/ultisnips' | Plug 'honza/vim-snippets' " On-demand loading Plug 'scrooloose/nerdtree', { 'on': 'NERDTreeToggle' } Plug 'tpope/vim-fireplace', { 'for': 'clojure' } " Using a non-default branch Plug 'rdnetto/YCM-Generator', { 'branch': 'stable' } " Using a tagged release; wildcard allowed (requires git 1.9.2 or above) Plug 'fatih/vim-go', { 'tag': '*' } " Plugin options Plug 'nsf/gocode', { 'tag': 'v.20150303', 'rtp': 'vim' } " Plugin outside ~/.vim/plugged with post-update hook Plug 'junegunn/fzf', { 'dir': '~/.fzf', 'do': './install --all' } " vim-airline " display the statusline at the bottom of the vim Plug 'vim-airline/vim-airline' Plug 'vim-airline/vim-airline-themes' " ale " check syntax on the contents of text buffers Plug 'dense-analysis/ale' " Initialize plugin system call plug#end() "================ " General settings "================ syntax on set cursorline set backspace=indent,eol,start " Show line numbers " set number " Show command in bottom bar " set showcmd " Visual autocomplete for command menu set wildmenu " Redraw only when necessary, speeds up macros set lazyredraw set hlsearch " system clipboard set clipboard=unnamed " remove all trailing whitepsace " https://vim.fandom.com/wiki/Remove_unwanted_spaces au BufWritePre * :%s/\s\+$//e " The NERD Tree noremap 1 1gt noremap 2 2gt noremap 3 3gt noremap 4 4gt noremap 5 5gt noremap 6 6gt noremap 7 7gt noremap 8 8gt noremap 9 9gt noremap 0 :tablast au BufNewFile,BufRead * set expandtab au BufNewFile,BufRead * set shiftwidth=4 au BufNewFile,BufRead * set softtabstop=4 au BufNewFile,BufRead * set tabstop=4 "=========================== " Language specific settings "=========================== " Python au BufNewFile,BufRead *.py set expandtab au BufNewFile,BufRead *.py set shiftwidth=4 au BufNewFile,BufRead *.py set softtabstop=4 au BufNewFile,BufRead *.py set tabstop=4 " Markdown au BufNewFile,BufRead *.md set expandtab au BufNewFile,BufRead *.md set shiftwidth=4 au BufNewFile,BufRead *.md set softtabstop=4 au BufNewFile,BufRead *.md set tabstop=4

vim-easy-align - I haven't yet found a Lua-based equivalent with the same flexibility.

Also does this plugin support operator-pending mode like vim-easy-align does? For instance doing gaip, ("go align in paragraph; commas) in normal mode aligns all commas in the current paragraph.

Regarding your last question, there’s this: https://github.com/junegunn/vim-easy-align

https://github.com/ludovicchabant/vim-gutentags/issues/139 has some background.

Hi everyone. I'm looking to have a better setup for Rust in neovim. I do have rust-analyzer installed for useful lsp things but I was hoping to get tags working for it as well. I was using vim-gutentags (https://github.com/ludovicchabant/vim-gutentags) for navigating useful functions and stuff but couldn't quite get it to work for rust. Is there a simple way to do it or do I need rusty-tags and some aucommand to get it to work?

use tags, I like https://github.com/ludovicchabant/vim-gutentags for this. I might use my local .vimrc to tweak the config (exclude compiled source files and other uninteresting things)

guttentag: https://github.com/ludovicchabant/vim-gutentags

Without more information, it's hard to point you in the right direction. The tags file could be out-of-date, in which case you can try to re-generate it (vim-gutentags for tags auto-generation). You could have 2 function declarations with the same name, in which case you can try :tag to cycle through tags (supports partials, like :tag F which will suggest FOO, FAR, FAB ...etc) or :tag to see a list of possible options (supports partials, like :tag F which will list FOO, FAR, FAB, ...etc) for various matching tags you can jump to (fzf.vim provides a tags fuzzy finder via :Tags). Maybe you're experiencing :h tag-priority?

ludovicchabant/vim-gutentags - Tags

You can then use :cnext and :cprev (or focusing the window and selecting an entry) to navigate between them.

As others have stated, you can also use ctags (plugins like https://github.com/ludovicchabant/vim-gutentags are useful for refreshing tags in a project), but for some languages you may need to add a tag definition (e.g. for something like rust or zig). For older languages like C you should be fine.

Not sure if it will help in this case, but I also depend on ctags for when the lsp fails (e.g. code it doesn't compile for some reason). Here you let a program create a tags file, e.g. I use https://github.com/universal-ctags/ctags (it seems it can parse json files, though I'm not sure what kind of tags are generated from this and if they will be useful to you) with https://github.com/ludovicchabant/vim-gutentags to update the tags file. The tags file just contains symbol names with locations where they are defined, and vim has builtin functionality to use these tags files :h tag and they (can) work filetype independent. For example if I mention a C type in a markdown document I can just use ctrl-[ to jump to its definition in the C source file. Possibly you can generate tags files yourself from the json files to help with this, the tags file format is not very complicated. Tags also are not very intelligent and depend on unique names for them to work well, there is the :h g_CTRL-] that can help, but for symbols that are very common (e.g. init or something that potentially has like 20+ definitions) it doesn't really work.