Skip to content

Test container CI for neovim and the lsp ecosystem

License

Notifications You must be signed in to change notification settings

hihihippp/try.nvim

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

38 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

try.nvim

for learning and testing

use this for beginner of neovim a start point: just use it immediatelly. the IDE configureed neovim is very cool, but the process of configuration is almost impossible for beginer user of neovim. this project can be a proper start point of neovim user, especiallly for the vscode user.

Quickstart

  1. Ensure you have installed a container runtime such as podman (recommended) or Docker. See below for details.
  2. To launch any of the containers run the following
podman run --rm -it quay.io/nvim-lsp/try.nvim:nightly-lua

Available containers

Please see the nvim-lsp organization on quay for a list of available tags. Generally, the containers follow the schema ${release}-${language} where release is either nightly or stable (neovim builds) and language is the name of the language tooling provided in the container.

Installing podman

On Fedora/RHEL systems, podman should should pre-installed. Otherwise:

sudo dnf install podman  

On Debian or derivatives (Ubuntu):

sudo apt install podman  

On Arch:

pacman -Syuu podman

On macOS:

brew install podman


# Required on macOS to initialize QEMU VM. Only required once.
podman machine init

# Must be done each restart.
podman machine start

For other linux distributions, please consult the package repositories. For Windows, use Docker.

Containers

A container can be thought of as a "lightweight" virtual machine, except instead of virtualizing the hardware, a container virtualizes the operating system and its libraries. This is advantageous, as a container has very little runtime overhead compared to a virtual machine. It can share the operating system kernel, and thus requires less memory and resources compared to a VM.

In order to use a container, you need to have a container runtime installed (podman, Docker, containerd, CRI-O). We recommend podman, which is a rootless, daemonless alternative to Docker which ships pre-installed on Fedora/RHEL linux distributions.

Please read the following resources if you are interested in learning more:

About

Test container CI for neovim and the lsp ecosystem

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Languages

  • Lua 91.1%
  • Dockerfile 7.5%
  • Shell 1.4%