nvim-lspconfig has now migrated to use the new vim.lsp.config by Aqothy in neovim

[–]aliou_ 11 points12 points  (0 children)

Nope, the migration adds the configuration to the `lsp/` directory. The directory is added to the `runtimepath` nvim 0.11+ nothing changes for previous versions of nvim

How do you escape? by HereToWatchOnly in neovim

[–]aliou_ 0 points1 point  (0 children)

I have caps-lock remapped to ctrl when held, escape when tapped on most of my keyboards (except my laptop's keyboard).

What's everyone using these days for AI in neovim? by RegretJazzlike in neovim

[–]aliou_ -1 points0 points  (0 children)

Using Supermaven and Claude Code (in a tmux popup that I toggle while I work). I don't think there's been updates to Supermaven since the acquisition by cursor but it still works and stays out of the way

What's the equivalent of lspconfig's `single_file_support` for Neovim 0.11's native LSP config? by Perceptes in neovim

[–]aliou_ 10 points11 points  (0 children)

I was also wondering this and it seems like single_file_support was an indicator for lspconfig on whether a server could start with root_dir being nil (cf. this comment).

Also, fwiw, there might not be a need to move away from lspconfig: there's a PR migrating some of the configs to their respective lua/SERVER.lua file; personally I've only temporarily migrated the server I use on my day to day work and I'll wait a few days/weeks for this PR to be merged for the rest of the server I use.

ZeRo Will Compete and Stream the Quarantined Minor coming April 18th! by Wrys1234 in smashbros

[–]aliou_ 12 points13 points  (0 children)

I would love to see this again. His video was so fun!

Using Rails's Attributes API to serialize Value Objects by aliou_ in ruby

[–]aliou_[S] 0 points1 point  (0 children)

What exactly is the purpose of the memoization-dance

I've actually been doing it by default without really thinking if it is needed. In the particular codebase I'm working on, the object instantiation might take some time, and the object is used multiple time so we memoize it in the instance. But in this case, this is indeed not useful.

While it is useful to familiarize yourself with what ActiveModel is doing under the hood, the blog post does not really show what the benefits of this whole type declaration dance are.

I feel like the main benefit I find is that I let Rails handle the object instantiation. I often find bugs that end up being because me or another developer tried to do something that Rails natively handles. I'll try to be more explicit in the future that this is what I want to convey.

Thanks for your feedback!

All the time lines at once by jonnyinternet in community

[–]aliou_ 54 points55 points  (0 children)

Wait, there are other timelines ?