Neovim
Neovim is a refactor, and sometimes redactor, in the tradition of Vim. It is not a rewrite but a continuation and extension of Vim. Neovim is built for users who want the good parts of Vim, and more.
Here are 4,204 public repositories matching this topic...
-
Updated
Apr 1, 2020 - TypeScript
-
Updated
Apr 21, 2022 - Lua
I want to preemptively start this thread to survey for suggestions. A cursory search lead me to this promising repository https://github.com/enigo-rs/enigo
Since closing the window is a common point of failure, that will be the focus for the first pass of testing as I learn how to use the library.
Components for testing:
- bridge
- editor
- renderer
- settings
- wind
-
Updated
Apr 19, 2022 - Swift
Description
I can not find the way by docs
Neovim version
0.6.1Operating system and version
macos 12.0.1
checkhealth telescope
-- This file can be loaded by calling `lua require('plugins')` from your init.vim
-- Only required if you have packer configured as `opt`
vim.cmd [[packadd packer.nvim]]
return require('packer').startup(function()-
Updated
Apr 7, 2022 - Vim script
-
Updated
Apr 19, 2022 - Vim script
-
Updated
Apr 21, 2022
-
Updated
Apr 20, 2022 - Lua
-
Updated
Apr 10, 2022 - TeX
Currently, the lockfile only contains the commit hash of a parser. This is fine for the most part, but if we switch parsers for a language in parsers.lua, this will not be picked up by :TSUpdate, leading to a broken installation.
Instead, the lockfile should contain the full URL of the parser (repo and branch), and that should be checked (and kept updated via the CI action).
-
Updated
Apr 21, 2022 - Vim script
-
Updated
Feb 15, 2022 - Vim script
-
Updated
Apr 12, 2022 - TypeScript
Sometimes a plugin (or multiple plugins) might fail to update/install.
It would make sense to add a retry option (perhaps mapped to R, since r is already mapped to revert).
-
Updated
Apr 21, 2022 - Lua
-
Updated
Mar 19, 2022 - Vim script
For the longest time I was able to access the pry console while running tests using :TestNearest, but it hasn't been working of late. I am able to run tests using :TestNearest and the other vim-test commands. My issue is that if I throw in a binding.pry in the test, I don't see the pry console open up anymore in the test window. That used to work before, and I can't figure out why. I'm
Jest on windows
Created by Thiago de Arruda
Released January 31, 2014
Latest release 6 days ago
- Repository
- neovim/neovim
- Website
- neovim.io
- Wikipedia
- Wikipedia


Is your feature request related to a problem? Please describe.

Much like with packer: