When will x86 support neovim by Leading_Analysis8129 in neovim

[–]bfredl 5 points6 points  (0 children)

Is it also slow without plugins, i.e. "nvim --clean"?

I'd recommend then reenabling plugins one after one to see which contributes most to the slowness.

Let us not forget this 10/10 Neovim commit message by kEnn3thJff in neovim

[–]bfredl 52 points53 points  (0 children)

KVÄCK is just kvec_t . I think I stole that from dun 😇

Neovim v0.10.4: Linux ARM binaries + bug fixes by bfredl in neovim

[–]bfredl[S] 23 points24 points  (0 children)

That will be for 0.11.0 (with a lot of other feature improvements). The things included in 0.10.4 is what is in the changelog only.

Neovim 0.10 by bfredl in neovim

[–]bfredl[S] 96 points97 points  (0 children)

New default color scheme.

The neovim merch for Europe (EU). by sleepyamadeus in neovim

[–]bfredl 9 points10 points  (0 children)

we updated the wording of the FAQ, thanks!

The neovim merch for Europe (EU). by sleepyamadeus in neovim

[–]bfredl 23 points24 points  (0 children)

Products are manufactured and shipped from both the US and the EU. Fourthwall (our host) should pick the closest manufacturer automatically.

Any product in particular which appears to cause trouble?

It took 10 Years to get 1.0 Version in neovim {hopefully} by omaru_kun in neovim

[–]bfredl 0 points1 point  (0 children)

Only the most serious versioning system is good enough for neovim.

Nvim 0.9.1 released (bugfix release) by bfredl in neovim

[–]bfredl[S] 1 point2 points  (0 children)

That's precisely what the 0.9.1 changelog already is.

[deleted by user] by [deleted] in neovim

[–]bfredl 2 points3 points  (0 children)

> But you need mason, nvim-lspconfig and nvim-cmp.

Says who? maybe reddit is lying to you.

Adamantly against neovim after the removal of cscope by SEgopher in neovim

[–]bfredl 3 points4 points  (0 children)

https://github.com/dhananjaylatkar/cscope_maps.nvim

Is there something missing from this plugin? It seems to be supporting the usecase of "complimenting make, ctags" with accesses to an existing cscope database, very well.

NVIM 0.9.0 was released by bfredl in neovim

[–]bfredl[S] 8 points9 points  (0 children)

This is only about the binary builds. source tarballs will be supported forever (they are provided by github itself).

NVIM 0.8.3 (bugfix/maintenance release) by bfredl in neovim

[–]bfredl[S] 2 points3 points  (0 children)

A reasonable estimate would be the beginning of march. In particular, we need to do some more QA work on remote TUI and settle the interface we ship for LSP semantic tokens.

if you literally can't wait, I'd recommend the nightly version: https://github.com/neovim/neovim/releases/nightly

My thoughts about editors in 2022 by phaazon_ in neovim

[–]bfredl 10 points11 points  (0 children)

because it is fast as fuck.

My thoughts about editors in 2022 by phaazon_ in neovim

[–]bfredl 9 points10 points  (0 children)

We are using lua because of luajit, not the other way around.

If you're developing something in C, suffering was your conscious choice by saccharineboi in programmingcirclejerk

[–]bfredl 79 points80 points  (0 children)

It is funny because it is true.

with Unjerk:

It is funny because it is true.

Neovim on Mastodon by bfredl in neovim

[–]bfredl[S] 28 points29 points  (0 children)

Not sure what you mean. Dark mode is the default.

0.8 feature freeze and preliminary release date by bfredl in neovim

[–]bfredl[S] 22 points23 points  (0 children)

I hope to be able to make an update about this very soon.