libnvim, Nvim RPC API

futures/promises, async/await, concurrency, task pipelines

backport release-0.9

breaking-change

issues reporting wrong behavior

issue reporting a crash or segfault

wrong behavior that was introduced in a previous commit (please bisect)

wrong behavior inherited from vim

building and installing Neovim using the provided scripts

Enable CI for s390x

automation for build, test, and release

clipboard, paste

closed:duplicate

issues that are closed as duplicates of other issues

Issues that are closed as "invalid"

closed:question

issues that are closed as usage questions

current behavior is by design, and change is not desired

command line, also cmdwin

code style, practices, guidelines, patterns

sign/number column

compatibility with Vim or older Neovim

Nvim built-in (omni)completion

complexity:high

High-risk, potential for delicate/cascading effects

Low-risk. Do NOT ask "can I work on this", just read CONTRIBUTING.md

Nvim core functionality or code

issues or PRs involving changing the defaults

build dependencies (LuaJIT, LibUV, etc.)

packaging and distributing Nvim to users

Nothing to see here; move along

save/restore editor state: shada, context, ctx

feature request

user system environment (terminal, shell, tmux)

events, autocommands

extmarks, decorations, virtual text, namespaces

filenames, path manipulation

filetype detection, filetype.lua

floating windows

community: Google Summer of Code project

issue contains a stacktrace/ASAN log

issue has been tracked to a specific commit

issue contains minimal reproducing steps

issue is fixed in vim and patch needs to be ported

issue is not fixed but can be circumvented until then

OS processes, spawn

UI messages, log messages

A discussion has run its course and a decision has to be made how to proceed

needs a clear design proposal

needs:discussion

For PRs that propose significant changes to some part of the architecture or API

We need minimal steps to reproduce the issue

waiting for reply from the author

needs:vim-patch

upstream issue that needs to be fixed in vim first

fuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu

text objects, normal commands

issues reporting performance problems

issues specific to BSD descendants (please specify which in the issue)

platform:cygwin

issues specific to other supported platforms

platform:windows

plugins and Vim "pack"

project-management

Neovim project matters (release process, logo, etc.)

changes that are not features or bugfixes

remote UI, --remote commands

revisit-at-release

security or privacy implications

Nvim startup sequence (`:h startup`)

status:blocked-external

Needs a third-party / external change or fix

tabline, winbar, statuscolumn

regex syntax or non-regex parsing, lpeg, grammars

built-in :terminal or :shell

multi-threading, vim.uv.new_thread

automation: collect in one PR and then merge automatically on a schedule

ui-extensibility

UI extensibility, events, protocol

(multibyte) unicode characters

user experience

See https://github.com/neovim/neovim/wiki/Merging-patches-from-upstream-Vim

zombie 🧟‍♀️

drive-by advice from the walking dead

No labels found. Sorry about that.