Neovim, e/plugins

684 posts

Neovim, e/plugins banner
Neovim, e/plugins

Neovim, e/plugins

@Neovim

Posts refer to Nvim 0.13 (dev build). Discuss usage/config/ideas at: https://t.co/mfM6kFnSfE

/usr/bin/nvim Katılım Mart 2014
15 Takip Edilen44.9K Takipçiler
Neovim, e/plugins
@its_just_ahmed ":help nvim-quickstart" has some notes, including popular distros #nvim-quickstart" target="_blank" rel="nofollow noopener">neovim.io/doc/user/nvim/…
English
0
0
1
39
أحمد
أحمد@its_just_ahmed·
@Neovim i mean i want to replace vscode but there're lots of options that make distraction to me
English
1
0
0
29
أحمد
أحمد@its_just_ahmed·
@Neovim guys i need 2 use vim as an editor. which easy ricing do i need to use & start with?
English
1
0
1
219
Kito ☭🏳️‍🌈✊
@Neovim caaralhowww funciona através da minha instalação do nvim ou é uma implementação a parte?
Português
1
0
0
217
Neovim, e/plugins retweetledi
Wes Higbee
Wes Higbee@g0t4·
love extmarks in @neovim so darn easy to show errors right next to my cursor (when command fails)!
Wes Higbee tweet media
English
0
1
16
3.6K
Neovim, e/plugins
Neovim, e/plugins@Neovim·
on nightly, these builtins now delegate to vim.ui.select: :tselect (tags/symbols) z= (spell suggest) if your picker (fzf-lua, etc) provides vim.ui.select(), it will just work.
English
1
0
88
6.6K
Neovim, e/plugins
Neovim, e/plugins@Neovim·
Nvim 0.13 gained vim.ui.img, a stdlib interface for displaying images. - useful for markdown files, directory browse, picker preview, ... - ~small interface + impl cost. mostly a protocol change. - placement will be handled by extmarks or floating windows. - no builtin codec, not going to vendor a jpeg library.
justinmk@justinmk

the vim.ui.img API for displaying images is now merged to @Neovim master. the result is a nice simple interface, despite a lot of pull in the other direction. idk why, but somehow these PRs for new modules always start with the most insanely complex implementations, instead of asking "what are the primitives that we absolutely need", and leaving the rest for later. this PR started with: - support for sixel, iterm2, kitty - new "provider" layer - async support?? - different concepts and "address spaces" for placement vs data and it ended with: -- Create: local id = vim.ui.img.set(…) -- Update: vim.ui.img.set(id, { row = 8, col = 12 }) -- Get: local opts = vim.ui.img.get(id) -- Delete: vim.ui.img.del(id) yeah, an LLM would have been fine (ecstatic!!) with rev1. think about that.

English
5
26
274
26K
Neovim, e/plugins
Neovim, e/plugins@Neovim·
@clauconstantin it's a small-cost, high-leverage change, not frivolous. > small interface + impl cost. mostly a protocol change. > no builtin codec, not going to vendor a jpeg library.
English
0
0
4
618
rex
rex@clauconstantin·
@Neovim doing some fanservice for the unix ricers?
English
1
0
3
785
芦屋道満
芦屋道満@douman_ash·
@Neovim Restart command doesn't respect my `autocmd vimenter` so I still prefer to just close it and reopen
English
1
0
0
25
Neovim, e/plugins
Neovim, e/plugins@Neovim·
on Nvim nightly (0.13) we have taken the first step in the trash-goblin sidequest, "fix filepath separators on Windows". this will unify and simplify path-handling internally. tl;dr: - use "/" slashes almost everywhere - convert to "\" slashes at the "edge" feedback from nightly Windows users is appreciated! github.com/neovim/neovim/…
English
1
4
97
6.6K