Sigh, I think I might have to switch away from #VisusalStudioCode. Seems the only stuff they work on is #AI, to the detriment of everything else.

Shall I move back to #vim? Or rather #neovim. Do I still have the patience to configure that just the way I like it?
I could also try out that newfangled #zed editor that is getting all the hype these days.

One must-have feature is it having good vim keybindings though, I'm lost without them.

#SoftwareDevelopment #golang #rustlang #rust

Historique des éditeurs texte que j'ai utilisés :

https://notes.sklein.xyz/Historique%20des%20%C3%A9diteurs%20texte%20que%20j'ai%20utilis%C3%A9s/

I might be switching from #neovim to #vim. Not that big of a switch but I think vim might be simpiler.

In the past couple of days I’ve finally had some time to work again on nvim-http.

It’s a #Neovim #Python plugin compatible with comparable HTTP client plugins in VsCode and IntelliJ - or a little #Postman that runs in your favourite editor.

While I was away I didn’t notice that the repo in the meantime has ammassed almost 100 stars and it had a dozen of outstanding issues - sorry!

The latest release includes many improvements and features:

• Fully migrated to the Neovim remote plugins API, now that Neovim has introduced breaking changes that make it incompatible with the old vim.async_run API.

• Better handling of HTTP requests that don’t end with newlines or comment headers.

• Added support for environent variables specified in .env files, either in the same directory as the .http file or in the current working directory of the editor. The plugin now also supports environment variables specified both in *.env.json files (VsCode compatibility) and .env files.

• Added support for inline shell commands, either in the environment variable or in the HTTP request, delimited by $(...).

• Added -h and -t options to the :Http command to display the output in a horizontal split or in a new tab (the default is a vertical split).

• Added --no-redirects option to :Http to avoid following redirects.

• Added -T/--timeout option.

https://github.com/blacklight/nvim-http

If you'd like to prank a fellow Vim user, send them a text file with `vim: revins` at the bottom and ask them to type some text in it... https://vimhelp.org/options.txt.html#%27revins%27

Unless they've turned off their `modeline` setting, something like this should happen:

After a recent update neovim doesn't seem to correctly active my colorscheme anymore. It applies it seemingly as :colorscheme shows me the correct colorscheme but only a second :colorscheme <name> does actually make it take affect. This is royally annoying. Has anyone experienced similar issues?

Oh, #neovim has a new version. Let's see whether this fixes the odd bug I keep having with #scnvim.

Hm, https://github.com/wsdjeg/SpaceVim seems to be the main #repository for #SpaceVim https://spacevim.org/ and it's listed as #archived on 2025-02-20, with no note anywhere about it
#vim #neovim

Vim이랑 Neovim은 어떻게 다를까?

https://hackers.pub/@kodingwarrior/2025/vim%EC%9D%B4%EB%9E%91-neovim%EC%9D%80-%EC%96%B4%EB%96%BB%EA%B2%8C-%EB%8B%A4%EB%A5%BC%EA%B9%8C

I think I found an easter egg in neovim just by chance, I typed ":smile" as a command and it gave me an ASCII art as the output.
Video below shows the output, I had to record the output because if I took only a screenshot more then half of the output would had been cut off. I know a screen cast is a bit too much just to show an ASCII art, but this is the only way that I can show the whole output.

#neovim 0.11 (released this week) introduces some nice convenience features for #lsp users - you can drop an LSP config into ~/.config/nvim/lsp/*.lua and if you call vim.lsp.enable with a table of LSP names, neovim will pick up your configs on startup.

What this means is that we can get rid of nvim-lspconfig and mason-lspconfig, simplifying and rationalizing config significantly

Hello, people who like to contribute and understand #Flatpak.

I need a hand with updating the #Neovim for version 0.11.0 and its dependences.

If you want to help;
Here is the repository: https://github.com/flathub/io.neovim.nvim
Here are the dependencies: https://github.com/neovim/neovim/blob/v0.11.0/cmake.deps/deps.txt
Here are the recipes: https://github.com/neovim/neovim/tree/v0.11.0/cmake.deps/cmake

Not sure I'll try right away the new #neovim ... there are breaking changes with LSP from what I read. can someone confirm ?

I'm reading the neovim 0.11 release notes and damn, they are cooking in neovim. Lots of good stuff

https://gpanders.com/blog/whats-new-in-neovim-0-11/

@gpanders has a really nice and concise post on what's new in #Neovim v0.11.0 along with code examples: https://gpanders.com/blog/whats-new-in-neovim-0-11/

BETTER EMOJI SUPPORT??? Most exciting #Neovim release ever?? https://lwn.net/Articles/1015496/

Meet me writing a 172-line POSIX shell script so that I can reduce the script that will install and run a binary distribution of #Neovim to five variables and a tar invocation.

https://codeberg.org/scy/dotfiles/commit/3413465d61dd87a85a211149504eae1203b64e44

The nice thing about this is that I can now write additional 10-line files to install other tools that I want but that aren't available on the servers I ssh into.

The bin/nvim → bin/shinst symlink will transparently download, verify, untar and then run Neovim based on .config/shinst/nvim.sh.

Neovim 0.11 has just been released!

https://github.com/neovim/neovim/releases/tag/v0.11.0

https://gpanders.com/blog/whats-new-in-neovim-0-11/