!rMMJVYqfOEOLttKGza:nixos.org

NixOS Matrix Suggestions

422 Members
Actionable suggestions for the Matrix space. Please hold discussion in #matrix-discussion:nixos.org, then bring the suggestion and context here. | https://pad.lassul.us/Nix-Matrix-Suggestions#139 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
25 Oct 2022
@sofo:matrix.org@sofo:matrix.org
In reply to @sandro:supersandro.de
jokes aside, vim and neovim are very close and you can with a few ifs re-use the config. vi is is no longer.
This is if you use the older viml over the new standard of lua in neovim. Most neovim configs are not possible to backport without serious investment. But neovim can run all plugins and configurations from vim.
16:09:56
@sofo:matrix.org@sofo:matrix.org
In reply to @sandro:supersandro.de
jokes aside, vim and neovim are very close and you can with a few ifs re-use the config. vi is is no longer.
* This is if you use the older viml (language) over the new standard of lua in neovim. Most neovim configs are not possible to backport without serious investment. But neovim can run all plugins and configurations from vim.
16:10:37
@kevincox:matrix.orgkevincox That was kind of the point. Using the name of one of the alive projects vim or nvim suggests priority for one over the other. If we want both in a channel as would likely be useful it makes sense to pick a name that is clearly not specific about either one. Hence vi. 16:11:36
@sofo:matrix.org@sofo:matrix.orgI see vim and neovim going further and further apart as tooling becomes more split. Like LSP integration, diagnostic tooling, and UI APIs.16:11:44
@sandro:supersandro.deSandro
In reply to @sofo:matrix.org
This is if you use the older viml (language) over the new standard of lua in neovim. Most neovim configs are not possible to backport without serious investment. But neovim can run all plugins and configurations from vim.
I use both and only lua because some plugins need it.
16:12:54
@sofo:matrix.org@sofo:matrix.org
In reply to @kevincox:matrix.org
That was kind of the point. Using the name of one of the alive projects vim or nvim suggests priority for one over the other. If we want both in a channel as would likely be useful it makes sense to pick a name that is clearly not specific about either one. Hence vi.
I could vouch for #vim, but #vi is a few decades too far out i think for people to realize its connection to neovim, which is what people are likely running today. Like calling Windows 10 of MSDOS-origin.
16:13:43
@k900:0upti.meK900Just call it #v16:14:16

Show newer messages


Back to Room ListRoom Version: 6