Skip to content

My personal nvim configuration for quick start on another machine

Notifications You must be signed in to change notification settings

vydramain/nvim-conf

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

44 Commits
 
 
 
 
 
 
 
 

Repository files navigation

nvim-conf

My personal nvim configuration for quick start on another machine: How to setup NeoVim for React and Typescript development:

Descripions:

Files from this repository are keeping in the ~/.config/nvim catalog.

Prerequisites:

Usages:

For start

NeoVim Plugin Manager:

  • Download vim-plug file.
  • Place the plugin inside autoload folder: /home/<user_folder>/.config/nvim/autoload/plug.vim

Required plugins:

The following content is init.vim temp-file content. The description is in the comment. Highly recommend to read the wiki in GitHub (For downloading s1n7ax's complete configuration)

Install dependencies

Before install plugins and start to use them intall dependencies.

For Fedora:

sudo dnf install python-neovim

For Debian:

sudo apt install python3-neovim

After install plugins you need to install coc.nvim's build. For that purpose go to the ~/.local/share/nvim/plugged/coc.nvim/build and start yarn building process:

yarn install

Some extensions for coc.nvim:

  • TSLint, Prettier, and TSServer extensions by default read project configuration files (.tslint, .prettier.config.js and tsconfig.json). Prettier TSLint capabilities can be enabled in the :CocConfig. For example, [coc-prettier](https://github.com/neoclide/coc-prettier):
:CocInstall coc-tsserver

Do not forget to install Silver Searcher

Depending on your Linux distribution, use one of the following methods to install The Silver Searcher.

On Debian and Ubuntu, use the following command:

sudo apt install silversearcher-ag

On AlmaLinux, CentOS 8 or later, and Fedora, use the following command:

sudo dnf install the_silver_searcher

Help records:

  • :CocConfig command runs coc configuration.
  • Default autocomplete is annoying since it’s controlled by arrow keys to select. Read completion with sources to configure it to tab.

How to debug note:

For each project we need to create vimspector.json which contains information about how to start a debugger session. This file is pretty simple, and you will usually just copy it between your projects with minimal changes. Here is an example content:

{
  "configurations": {
    "Launch": {
      "adapter": "vscode-cpptools",
      "configuration": {
        "request": "launch",
        "program": "${gadgetDir}/vscode-cpptools/debugAdapters/bin/OpenDebugAD7",
        "externalConsole": true
      }
    }
  }
}

If you have issues with not recognizing headers

Check ccls FAQ

Try to delete into the folder /usr/lib/gcc/x86_64-linux-gnu/ all libraries with the largest version number than you use.


Inspirated by:

About

My personal nvim configuration for quick start on another machine

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published