#neovim — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #neovim, aggregated by home.social.
-
#neovim Development News
The 0.12 version updates `vim.ui.input()` interface to allow setting input scope (like `cursor`, `window`, `editor`, etc.).
PR:
- github.com/neovim/neovi...
feat(ui): add and use `opts.sc... -
#neovim Development News
The 0.12 version updates `vim.ui.input()` interface to allow setting input scope (like `cursor`, `window`, `editor`, etc.).
PR:
- github.com/neovim/neovi...
feat(ui): add and use `opts.sc... -
#neovim Development News
The 0.12 version updates `vim.ui.input()` interface to allow setting input scope (like `cursor`, `window`, `editor`, etc.).
PR:
- github.com/neovim/neovi...
feat(ui): add and use `opts.sc... -
#neovim Development News
The 0.12 version updates `vim.ui.input()` interface to allow setting input scope (like `cursor`, `window`, `editor`, etc.).
PR:
- github.com/neovim/neovi...
feat(ui): add and use `opts.sc... -
Is anybody using the VIS editor?
I’m really curious about it but I would need some bootstrap tutorial like "VIS for Vim users". I’m still really confused about it.
(yeah, I’m planning to leave Neovim. Will probably ends on Vim-classic once it is packaged in #debian ). Also like #kakoune a lot but Vim-muscle memory is too strong for now.
-
Is anybody using the VIS editor?
I’m really curious about it but I would need some bootstrap tutorial like "VIS for Vim users". I’m still really confused about it.
(yeah, I’m planning to leave Neovim. Will probably ends on Vim-classic once it is packaged in #debian ). Also like #kakoune a lot but Vim-muscle memory is too strong for now.
-
Is anybody using the VIS editor?
I’m really curious about it but I would need some bootstrap tutorial like "VIS for Vim users". I’m still really confused about it.
(yeah, I’m planning to leave Neovim. Will probably ends on Vim-classic once it is packaged in #debian ). Also like #kakoune a lot but Vim-muscle memory is too strong for now.
-
Is anybody using the VIS editor?
I’m really curious about it but I would need some bootstrap tutorial like "VIS for Vim users". I’m still really confused about it.
(yeah, I’m planning to leave Neovim. Will probably ends on Vim-classic once it is packaged in #debian ). Also like #kakoune a lot but Vim-muscle memory is too strong for now.
-
Is anybody using the VIS editor?
I’m really curious about it but I would need some bootstrap tutorial like "VIS for Vim users". I’m still really confused about it.
(yeah, I’m planning to leave Neovim. Will probably ends on Vim-classic once it is packaged in #debian ). Also like #kakoune a lot but Vim-muscle memory is too strong for now.
-
important clarification from the @neovim:
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
-
important clarification from the @neovim:
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
-
important clarification from the @neovim:
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
-
important clarification from the @neovim:
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
-
important clarification from the @neovim:
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
-
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
However, Neovim does NOT delete or corrupt Vim undofiles (nor has vim any problem with neovim undofiles), for two simple reasons:
1. By default, neovim have used a different path for state files than vim since a decade. Thus the two editors will just safely ignore each others state files, just like you used any pair of editors at the same time, like vim and emacs.
2. even if you forcibly override both neovim and vim to look for state files in the same directory, there is no risk for corruption. Both editors share a versioning logic for undofiles where incompatible versions are directly detected and left unread and unwritten. These are never overwritten without asking the user for confirmation.
-
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
However, Neovim does NOT delete or corrupt Vim undofiles (nor has vim any problem with neovim undofiles), for two simple reasons:
1. By default, neovim have used a different path for state files than vim since a decade. Thus the two editors will just safely ignore each others state files, just like you used any pair of editors at the same time, like vim and emacs.
2. even if you forcibly override both neovim and vim to look for state files in the same directory, there is no risk for corruption. Both editors share a versioning logic for undofiles where incompatible versions are directly detected and left unread and unwritten. These are never overwritten without asking the user for confirmation.
-
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
However, Neovim does NOT delete or corrupt Vim undofiles (nor has vim any problem with neovim undofiles), for two simple reasons:
1. By default, neovim have used a different path for state files than vim since a decade. Thus the two editors will just safely ignore each others state files, just like you used any pair of editors at the same time, like vim and emacs.
2. even if you forcibly override both neovim and vim to look for state files in the same directory, there is no risk for corruption. Both editors share a versioning logic for undofiles where incompatible versions are directly detected and left unread and unwritten. These are never overwritten without asking the user for confirmation.
-
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
However, Neovim does NOT delete or corrupt Vim undofiles (nor has vim any problem with neovim undofiles), for two simple reasons:
1. By default, neovim have used a different path for state files than vim since a decade. Thus the two editors will just safely ignore each others state files, just like you used any pair of editors at the same time, like vim and emacs.
2. even if you forcibly override both neovim and vim to look for state files in the same directory, there is no risk for corruption. Both editors share a versioning logic for undofiles where incompatible versions are directly detected and left unread and unwritten. These are never overwritten without asking the user for confirmation.
-
There has been the need to clarify some rumors that have been circulated on social media:
Yes, #neovim uses an different undofile format than #vim. In an ideal world we would not need this, but the way neovim implements buffer properties is completely different than vim, and this state is part of what is undo-able.
However, Neovim does NOT delete or corrupt Vim undofiles (nor has vim any problem with neovim undofiles), for two simple reasons:
1. By default, neovim have used a different path for state files than vim since a decade. Thus the two editors will just safely ignore each others state files, just like you used any pair of editors at the same time, like vim and emacs.
2. even if you forcibly override both neovim and vim to look for state files in the same directory, there is no risk for corruption. Both editors share a versioning logic for undofiles where incompatible versions are directly detected and left unread and unwritten. These are never overwritten without asking the user for confirmation.
-
#Neovim obviously uses a different LOCATION for undofiles than vim by default.
You only get in trouble if you SPECIFICALLY ASK vim and neovim to mess with each other by using the same cache directory.
Even then vim and neovim shares the same code which SAFELY refuses to touch incompatible files. -
#Neovim obviously uses a different LOCATION for undofiles than vim by default.
You only get in trouble if you SPECIFICALLY ASK vim and neovim to mess with each other by using the same cache directory.
Even then vim and neovim shares the same code which SAFELY refuses to touch incompatible files. -
#Neovim obviously uses a different LOCATION for undofiles than vim by default.
You only get in trouble if you SPECIFICALLY ASK vim and neovim to mess with each other by using the same cache directory.
Even then vim and neovim shares the same code which SAFELY refuses to touch incompatible files. -
#Neovim obviously uses a different LOCATION for undofiles than vim by default.
You only get in trouble if you SPECIFICALLY ASK vim and neovim to mess with each other by using the same cache directory.
Even then vim and neovim shares the same code which SAFELY refuses to touch incompatible files.