Giter Club home page Giter Club logo

kickstart-modular.nvim's Introduction

kickstart-modular.nvim

Introduction

This is a fork of nvim-lua/kickstart.nvim that moves from a single file to a multi file configuration.

A starting point for Neovim that is:

  • Small
  • Modular
  • Completely Documented

NOT a Neovim distribution, but instead a starting point for your configuration.

Installation

Install Neovim

Kickstart.nvim targets only the latest 'stable' and latest 'nightly' of Neovim. If you are experiencing issues, please make sure you have the latest versions.

Install External Dependencies

External Requirements:

  • Basic utils: git, make, unzip, C Compiler (gcc)
  • ripgrep
  • Clipboard tool (xclip/xsel/win32yank or other depending on platform)
  • A Nerd Font: optional, provides various icons
    • if you have it set vim.g.have_nerd_font in init.lua to true
  • Language Setup:
    • If want to write Typescript, you need npm
    • If want to write Golang, you will need go
    • etc.

NOTE See Install Recipes for additional Windows and Linux specific notes and quick install snippets

Install Kickstart

NOTE Backup your previous configuration (if any exists)

Neovim's configurations are located under the following paths, depending on your OS:

OS PATH
Linux, MacOS $XDG_CONFIG_HOME/nvim, ~/.config/nvim
Windows (cmd) %userprofile%\AppData\Local\nvim\
Windows (powershell) $env:USERPROFILE\AppData\Local\nvim\

Recommended Step

Fork this repo so that you have your own copy that you can modify, then install by cloning the fork to your machine using one of the commands below, depending on your OS.

NOTE Your fork's url will be something like this: https://github.com/<your_github_username>/kickstart-modular.nvim.git

Clone kickstart.nvim

NOTE If following the recommended step above (i.e., forking the repo), replace dam9000 with <your_github_username> in the commands below

Linux and Mac
git clone https://github.com/dam9000/kickstart-modular.nvim.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim
Windows

If you're using cmd.exe:

git clone https://github.com/dam9000/kickstart-modular.nvim.git %userprofile%\AppData\Local\nvim\

If you're using powershell.exe

git clone https://github.com/dam9000/kickstart-modular.nvim.git $env:USERPROFILE\AppData\Local\nvim\

Post Installation

Start Neovim

nvim

That's it! Lazy will install all the plugins you have. Use :Lazy to view current plugin status. Hit q to close the window.

Read through the init.lua file in your configuration folder for more information about extending and exploring Neovim. That also includes examples of adding popularly requested plugins.

Getting Started

The Only Video You Need to Get Started with Neovim

FAQ

  • What should I do if I already have a pre-existing neovim configuration?
    • You should back it up and then delete all associated files.
    • This includes your existing init.lua and the neovim files in ~/.local which can be deleted with rm -rf ~/.local/share/nvim/
  • Can I keep my existing configuration in parallel to kickstart?
    • Yes! You can use NVIM_APPNAME=nvim-NAME to maintain multiple configurations. For example, you can install the kickstart configuration in ~/.config/nvim-kickstart and create an alias:
      alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
      
      When you run Neovim using nvim-kickstart alias it will use the alternative config directory and the matching local directory ~/.local/share/nvim-kickstart. You can apply this approach to any Neovim distribution that you would like to try out.
  • What if I want to "uninstall" this configuration:
  • Why is the kickstart init.lua a single file? Wouldn't it make sense to split it into multiple files?
    • The main purpose of kickstart is to serve as a teaching tool and a reference configuration that someone can easily use to git clone as a basis for their own. As you progress in learning Neovim and Lua, you might consider splitting init.lua into smaller parts. A fork of kickstart that does this while maintaining the same functionality is available here:
    • NOTE: This is the fork that splits the configuration into smaller parts. The original repo with the single init.lua file is available here:
    • Discussions on this topic can be found here:

Install Recipes

Below you can find OS specific install instructions for Neovim and dependencies.

After installing all the dependencies continue with the Install Kickstart step.

Windows Installation

Windows with Microsoft C++ Build Tools and CMake Installation may require installing build tools and updating the run command for `telescope-fzf-native`

See telescope-fzf-native documentation for more details

This requires:

  • Install CMake and the Microsoft C++ Build Tools on Windows
{'nvim-telescope/telescope-fzf-native.nvim', build = 'cmake -S. -Bbuild -DCMAKE_BUILD_TYPE=Release && cmake --build build --config Release && cmake --install build --prefix build' }
Windows with gcc/make using chocolatey Alternatively, one can install gcc and make which don't require changing the config, the easiest way is to use choco:
  1. install chocolatey either follow the instructions on the page or use winget, run in cmd as admin:
winget install --accept-source-agreements chocolatey.chocolatey
  1. install all requirements using choco, exit previous cmd and open a new one so that choco path is set, and run in cmd as admin:
choco install -y neovim git ripgrep wget fd unzip gzip mingw make
WSL (Windows Subsystem for Linux)
wsl --install
wsl
sudo add-apt-repository ppa:neovim-ppa/unstable -y
sudo apt update
sudo apt install make gcc ripgrep unzip git xclip neovim

Linux Install

Ubuntu Install Steps
sudo add-apt-repository ppa:neovim-ppa/unstable -y
sudo apt update
sudo apt install make gcc ripgrep unzip git xclip neovim
Debian Install Steps
sudo apt update
sudo apt install make gcc ripgrep unzip git xclip curl

# Now we install nvim
curl -LO https://github.com/neovim/neovim/releases/latest/download/nvim-linux64.tar.gz
sudo rm -rf /opt/nvim-linux64
sudo mkdir -p /opt/nvim-linux64
sudo chmod a+rX /opt/nvim-linux64
sudo tar -C /opt -xzf nvim-linux64.tar.gz

# make it available in /usr/local/bin, distro installs to /usr/bin
sudo ln -sf /opt/nvim-linux64/bin/nvim /usr/local/bin/
Fedora Install Steps
sudo dnf install -y gcc make git ripgrep fd-find unzip neovim
Arch Install Steps
sudo pacman -S --noconfirm --needed gcc make git ripgrep fd unzip neovim

kickstart-modular.nvim's People

Contributors

amtoine avatar anthony-fiddes avatar chillerdragon avatar dam9000 avatar dennisrall avatar feoh avatar folke avatar gangelop avatar kaminskypavel avatar kdheepak avatar luizcalliari avatar mech-a avatar nphyn1t3 avatar numkil avatar nwvi avatar pbnj avatar saccarosium avatar samposh avatar shashwatagrawal20 avatar slara avatar smiggiddy avatar sudo-tee avatar tjdevries avatar togglebyte avatar tsankotsanev avatar ttibsi avatar usernoemail-com avatar vladexa avatar vzaa avatar wommy avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

kickstart-modular.nvim's Issues

Pyright failed to install

Describe the bug

Pyright failed to install

To Reproduce

Just uncomment pyright in the servers table

Desktop

  • OS: WSL (Windows)
  • Terminal: Windows Terminal

Neovim Version

NVIM 0.9.4
Build type: Release
LuaJIT 2.1.1692716794
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/__w/neovim/neovim/build/nvim.AppDir/usr/share/nvim"

Update for nvim 0.10

On its 0.10 version nvim does not need comment plugin and has changed some stuff. Thanks in advance!

Defined colorscheme not loaded correctly.

Describe the bug

When mason installs something new, the colorscheme config seems to be applied as expected. After closing and opening nvim again, the colorscheme loaded, seems to be tokyonight instead of tokyonight-night as defined in the tokyonight.lua.

When checking :scriptnames in both cases, i see that when opening without any mason interaction the last script executed is ~/.local/share/nvim/lazy/tokyonight.nvim/colors/tokyonight.lua, while it is not when Mason is executed upon opening nvim.

To Reproduce

  1. Install the repo as nvim config
  2. Start nvim, mason installs a bunch of plugins
  3. The theme is tokyonight-night
  4. Close nvim
  5. Open nvim
  6. The theme is now tokyonight

Desktop

  • OS: Debian 12
  • Terminal: Gnome terminal

Neovim Version

NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1692716794

I have searched all lua files, i could find and there does not seem to be any hidden call to tokyonight, which would cause the default theme to be overwritten.
Any insight would be appreciated.

Mason failed to install stylua

Describe the bug

When I enter neovim mason fails to install stylua.

To Reproduce

  1. Open neovim in my /.config/nvim folder using nvim . You can se my config here.

Desktop

  • OS: Linux (WSL), Ubuntu
  • Terminal: Windows terminal

Neovim Version

NVIM 0.9.4
Build type: Release
LuaJIT 2.1.1692716794
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/__w/neovim/neovim/build/nvim.AppDir/usr/share/nvim"

How to override default configuration for formatters and linters?

Describe the bug

First it's not a bug, but more like a question:
conform and nvim-lint help don't say anything about overriding the default configuration or rules of any formatter or linter.
How can this be achieved? Do these plugins pickup config files inside a project? is there a way to add global configuration that these plugins will pick?
Perhaps it could be worth adding a NOTE with an exaple on how to do it for any language formatter/linter.

To Reproduce

Format or lint any filetype for which you have a formatter or linter set.

Desktop

  • OS: macOS Sonoma 14.4.1
  • Terminal: iTerm2

Neovim Version

NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1710088188
   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/opt/homebrew/Cellar/neovim/0.9.5/share/nvim"

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.