Q&A
How to work with git? - LazyGit and tutorial
I have to write to file with :w every time when I want to save? - Yes, if you want to control this process. No, you should setup autosaving, for example this:
How to setup eslint and prettier prompts? - :Mason plugin for setup LSP servers, DAP servers, linters, and formatters
example:
:Mason —> find typescript-language-server —> press i for install
Tutorial - Linting and Formatting
If you already have files: .eslintrc.js, .prettierignore, .prettierrc, tsconfig.eslint.json - everything connecting automatically, and you can see errors instantly, and prettier make code prettier after every :w command.
Other pluses:
➕ Working with usual IDE seems more overwhelming than vim, you can enable only necessary plugins for you current needs depend on language
➕ It is very good if you want to split up and modify your developing tools
➕ Since vim consumes much less resources than IDE, It gives you more resources for emulator and debugger
➕ Really fast
Shortcut сrib sheet
iTerm shortcuts:
Cmd+left arrow, Cmd+right arrow navigates among tabs
Cmd+number navigates directly to a tab
Cmd+Option+Number navigates directly to a window
Cmd+Option+Arrow keys navigate among split panes
Cmd+] and Cmd+[ navigates among split panes in order of use
NEO TREE shortcuts:
shift + ? = menu
a/A - add new file or folder
shift + h - show hidden files
LazyGit:
click on commit + y = for copy commit id
Comments.nvim shortcuts:
Normal mode:
`gcc` - Toggles the current line using linewise comment
`gbc` - Toggles the current line using blockwise comment
`[count]gcc` - Toggles the number of line given as a prefix-count using linewise
`[count]gbc` - Toggles the number of line given as a prefix-count using blockwise
`gc[count]{motion}` - (Op-pending) Toggles the region using linewise comment
`gb[count]{motion}` - (Op-pending) Toggles the region using blockwise comment
Visual Mode:
`gc` - Toggles the region using linewise comment
`gb` - Toggles the region usi
Eslint shortcuts:
[d and ]d —> navigating between errors
space + xx —> launch trouble plugin to see all error messages in the project
space + sd —> for diagnostic errors in the buffer
space + cd —> diagnostic for specific line (if you type cd again, you can jump through the messages)
space + ud —> disable all diagnostics
space + ca —> to fix problem automatically
space + cA —> fix all errors