syntastic VS LunarVim

2) Syntax check https://github.com/vim-syntastic/syntastic 3) File navigation https://github.com/preservim/nerdtree 4) Autocomplete There are many autocomplete extensions. I haven't found one that I feel comfortable to recommend. Another way is to create a txt file with all the key words and lines in the languages you use, make an autocommand that adds the txt file to the buffer, and then use ctrl-n or ctrl-p to autocomplete. You can also use ctrl-x-ctrl-l to autocmplete entire lines. 5) Running code Add commands in your .vmrc to run the current file as a a whatever file. I use :J to run java files, :P to run python files, :C to run c files and so on. For example, this is my command to run a java file: command J execute "!java %:t"

I dropped into the Syntastic plugin repo a few minutes ago to check the documentation and noticed that the first section in the README is a deprecation notice. The commit message says "add deprecation note" and is dated 26 days ago.

I typically code in the terminal with vim + idf.py and I've been working heavily with esp-idf for a while now. Does anyone have any recommendations for some c-style linters and/or formatters? I typically use syntastic to do code linting but I haven't been able to find a syntax checker that doesn't have quirks with esp-idf code.

Syntastic - it appears they didnt actually support neovim to begin with, so I expect it will be left behind

I use https://ycm-core.github.io/YouCompleteMe/ for autocomplete and https://github.com/vim-syntastic/syntastic for syntax changing as well. For my python projects this was enough to move away from VS Code. There are other plugins I use to help me code with python with vim but this should answer most of your question.

I want to create a new vim syntax checker for a new programming language that is not used widely, first i tried to read the code of the follwing plugins neomake, syntastic , and Ale in order to understand how i can build my own syntax checker plugin but i could not really get it so i just want know what is the best and easy way to create syntax checker plugin for vim

My vim looks like most peoples, I guess. I have a few plugins to make things pretty, eg. LightLine and IndentGuides, and I use Syntastic for linting. I tried Ale but found it too annoying in practice.

execute pathogen#infect() syntax on set number set incsearch filetype plugin indent on "" System """"" Ale let g:ale_sign_column_always = 1 let g:ale_sign_error = '>>' let g:ale_sign_warning = '--' " Set this. Airline will handle the rest. let g:airline#extensions#ale#enabled = 1 let g:ale_echo_msg_error_str = 'E' let g:ale_echo_msg_warning_str = 'W' let g:ale_echo_msg_format = '[%linter%] %s [%severity%]' """" Tagbar nmap :TagbarToggle """" AutoComplete " It needs https://github.com/prabirshrestha/asyncomplete-lsp.vim inoremap pumvisible() ? "\" : "\" inoremap pumvisible() ? "\" : "\" inoremap pumvisible() ? asyncomplete#close_popup() : "\" "" Force refresh imap (asyncomplete_force_refresh) " allow modifying the completeopt variable, or it will " be overridden all the time let g:asyncomplete_auto_completeopt = 0 set completeopt=menuone,noinsert,noselect,preview autocmd! CompleteDone * if pumvisible() == 0 | pclose | endif """" Syntastic " https://github.com/vim-syntastic/syntastic "set statusline+=%#warningmsg# "set statusline+=%{SyntasticStatuslineFlag()} "set statusline+=%* "let g:syntastic_always_populate_loc_list = 1 "let g:syntastic_auto_loc_list = 1 "let g:syntastic_check_on_open = 1 "let g:syntastic_check_on_wq = 0 """" LSP if executable('clangd') au User lsp_setup call lsp#register_server({ \ 'name': 'clangd', \ 'cmd': {server_info->['clangd', '-background-index']}, \ 'whitelist': ['c', 'cpp', 'objc', 'objcpp'], \ }) endif function! s:on_lsp_buffer_enabled() abort setlocal omnifunc=lsp#complete setlocal signcolumn=yes if exists('+tagfunc') | setlocal tagfunc=lsp#tagfunc | endif nmap gd (lsp-definition) nmap gs (lsp-document-symbol-search) nmap gS (lsp-workspace-symbol-search) nmap gr (lsp-references) nmap gi (lsp-implementation) nmap gt (lsp-type-definition) nmap rn (lsp-rename) nmap [g (lsp-previous-diagnostic) nmap ]g (lsp-next-diagnostic) nmap K (lsp-hover) inoremap lsp#scroll(+4) inoremap lsp#scroll(-4) let g:lsp_format_sync_timeout = 1000 autocmd! BufWritePre *.rs,*.go call execute('LspDocumentFormatSync') " refer to doc to add more commands endfunction augroup lsp_install au! " call s:on_lsp_buffer_enabled only for languages that has the server registered. autocmd User lsp_buffer_enabled call s:on_lsp_buffer_enabled() augroup END "" Folding set foldmethod=expr \ foldexpr=lsp#ui#vim#folding#foldexpr() \ foldtext=lsp#ui#vim#folding#foldtext() """" Nerdtree " https://github.com/preservim/nerdtree nnoremap n :NERDTreeFocus nnoremap :NERDTree nnoremap :NERDTreeToggle nnoremap :NERDTreeFind " Start NERDTree and put the cursor back in the other window. autocmd VimEnter * NERDTree | wincmd p " Close the tab if NERDTree is the only window remaining in it. autocmd BufEnter * if winnr('$') == 1 && exists('b:NERDTree') && b:NERDTree.isTabTree() | quit | endif " If another buffer tries to replace NERDTree, put it in the other window, and bring back NERDTree. autocmd BufEnter * if bufname('#') =~ 'NERD_tree_\d\+' && bufname('%') !~ 'NERD_tree_\d\+' && winnr('$') > 1 | \ let buf=bufnr() | buffer# | execute "normal! \w" | execute 'buffer'.buf | endif " Design let g:NERDTreeDirArrowExpandable = '▸' let g:NERDTreeDirArrowCollapsible = '▾' """" NerdCommenter " Create default mappings let g:NERDCreateDefaultMappings = 1 " Add spaces after comment delimiters by default let g:NERDSpaceDelims = 1 " Use compact syntax for prettified multi-line comments let g:NERDCompactSexyComs = 1 " Align line-wise comment delimiters flush left instead of following code indentation let g:NERDDefaultAlign = 'left' " Set a language to use its alternate delimiters by default let g:NERDAltDelims_java = 1 " Add your own custom formats or override the defaults let g:NERDCustomDelimiters = { 'c': { 'left': '/**','right': '*/' } } " Allow commenting and inverting empty lines (useful when commenting a region) let g:NERDCommentEmptyLines = 1 " Enable trimming of trailing whitespace when uncommenting let g:NERDTrimTrailingWhitespace = 1 " Enable NERDCommenterToggle to check all selected lines is commented or not let g:NERDToggleCheckAllLines = 1 """" IndentLine "let g:indentLine_setColors = 0 "let g:indentLine_defaultGroup = 'SpecialKey' " Vim let g:indentLine_color_term = 239 " GVim let g:indentLine_color_gui = '#A4E57E' " none X terminal let g:indentLine_color_tty_light = 7 " (default: 4) let g:indentLine_color_dark = 1 " (default: 2) " Background (Vim, GVim) let g:indentLine_bgcolor_term = 202 let g:indentLine_bgcolor_gui = '#FF5F00' let g:indentLine_char_list = ['|', '¦', '┆', '┊'] """" bufexplorer " https://github.com/jlanzarotta/bufexplorer

LunarVim

I would suggest to start getting into vim by first trying out popular vim keybinding plugins available on your favorite code editor and get used to those first. Then, if you want to dive deeper into the power of Neovim, try out popular configs like LazyVim, LunarVim, NvChad... Taking Neovim from a mere text editor to a full-featured IDE with features like intellisense, debugging, testing, etc... on your own takes quite a lot of work and configuration.

I used Helix for a while due to its support for LSP out-of-the-box, which my Vim config at the time couldn't live up to. I switched back to NeoVim after finding LunarVim[1] which had everything I was trying to get setup in my own config.

[1] https://www.lunarvim.org/

I'll admit I didn't look into it, but Helix sounds like something like LunarVim (https://www.lunarvim.org/)

Personally I much prefer that the editor NOT ship with something like that by default, especially when it's so easy to set up. I have several different vim config I use, including a pretty bare-bones one for headless systems, and I much prefer the ability to customize something very specifically.

Build tools that can compose together, rather than a single do-it-all tool. That is the power of the low level editors vs IDE's.

I can't comment on any implementation details, but at least with LunarVim (which I use for daily coding), a slowdown when interacting with LSP is very noticeable. Some others have attested to this on a GitHub issue.

I'm not doubting your experiences with the lack of a slowdown, but there is truth that others do experience it. That might be more of a problem with LunarVim itself rather than Vim, but how likely am I (as someone who would like to avoid what he calls "config hell") or other newcomers to avoid whatever pitfalls there are, if a distribution designed for ease of use by people who know better fall into them?

https://github.com/LunarVim/LunarVim/discussions/3359

Anyways, although i have not used them, LazyVim and LunarVim comes highly recommended. You can try these and see what suits you .