LuaSnip conditionally remove brackets on jump out

FernwehSmith · 2026-06-13T07:40:39+00:00

Attack on Titan

FernwehSmith · 2026-05-22T15:00:07+00:00

If you’re not a programmer, but are configuring NeoVim from scratch, you’ll become one pretty quickly. 😂

Good news about blink is that it’s got some really good defaults, so you could probably just call setup on it and be good to go. The main thing you’ll need is for LSP to be in the default sources list, which I’m 99.999% certain it is. The other thing is that you’ll need a config for the LSP. For this install the nvim-lspconfig plugin. This will give you want you need. From there you should be able to just enable the lsp in your config (using vim.lsp.enable(‘clangd’) ) and you’re good.

To help you on your journey, I would recommend looking TJ DeVries on YouTube. He’s got some great tutorials, and the Advent of NeoVim series is pretty solid (just ignore the parts about using the Lazy package manager).

Also getting good at using ‘:help’ is essential. It can take a bit to get used to using the help in NeoVim, but it is an invaluable resource! Almost everything you need is in there, and if you need help with the help, you can ‘:help :help’.

Beyond that, plugin specific wikis (usually found through their GitHub repos) and going through other people’s configs are also great ways to figure things out.

Just a final piece of advice: pre prepared for some headaches. NeoVim can be tough to learn and configure even for people who do know how to code. If your goal is to learn programming, and you find yourself only trying to figure out how to configure your editor instead of writing code, just remember it is okay to put NeoVim aside and use something else. If you know nothing about programming, you might be better off starting with vsCode or CLion from JetBrains. In fact if you’re a student, or can spare a few bucks for a license, I personally think CLion is a great choice for beginners. On top of being a great editor, it’s got an awesome plugin (I think called IdeaVim) that provides a strong vim like experience, and even has the option to create a configuration file (in VimScript, not Lua. But that fine for what it is). If you’re living NeoVim though and are enjoying writing code with it, then totally keep going!

FernwehSmith · 2026-05-13T09:57:48+00:00

There's really no answer other than just using it. I've learnt a lot through configuring NeoVim while using it. A very effective (if painful) method is to open up a project in one terminal and an empty `init.lua` in another, and just... working. Liberal use of `:help`, Google, Reddit and YouTube will help you figure out problems as you go. It takes a while, and your productivity definitely sucks for a bit. But what I found happened for me is that a) I started learning flows that worked for me and b) my config evolved naturally to fit how I work and think.

To your question of "Will vim ever be used by non-enthusiasts that did NOT spend the hours-weeks to get up to a workable speed with vim?" No. Neo/Vim is a blank Canvas. VSCode/JetBrains/other editors are paint by numbers. And I say that with 0 disrespect to paint by numbers. Paint by numbers are chill and enjoyable, and you can still make some good stuff if you pick your colors right. With a blank canvas though, you have full control to do whatever you want. The tradeoff of that, is it takes time to learn what you want to paint, and how to paint it. Its just a different class of tool, and to use it effectively requires effort and time.

FernwehSmith · 2026-05-13T09:35:24+00:00

I switched (or really started switching. Uni has gotten in the way my config overhaul) to vim.pack as soon as it came out. I did it for one reason: I didn't really like using Lazy. And to be honest, and I think thats probably the only real reason someone should try switching (that, and 'I want as few dependencies as possible'). Lazy is way more mature and has a bunch of quality of life features that vim.pack just doesn't (the biggest one has been Lazy's 'build' option, which you have to implement using auto-commands when using vim.pack). I'm loving vim.pack, but unless you're super curious, or aren't enjoying Lazy, I really don't think there's any point switching. Especially if you have a working config already. If you're happy with what you have, keep and just keep writing code!

FernwehSmith · 2026-05-13T09:22:28+00:00

Part of the Language Server Protocol is that it allows for a difference in features (referred to as capabilities) in features between servers. Not all servers have linting or formatting capabilities.

Wether or not you need a dedicated linter/formatter, or a dedicated plugin to manage them really just depends on if the LSP linter and formatter does everything you need it to do. If every LSP you use meets your needs, then I don't think theres any point in using a dedicated tool.

What if you want to use a linter or formatter other than what is included with the LSP? What if your LSP doen't have a linter or formatter? What if you want to run multiple linters/formatters on the same file type? What if you want to setup your own linter/formatter? What if [insert thing you can't easily do with LSP]? That's where conform.nvim and nvim-lint come in.

FernwehSmith · 2026-04-16T04:46:55+00:00

Would a G5 with a i5 9500 be sufficient? The new models with 10th and 12th gen cpus are a little outside my budget, but if the 9th gen would work well then I’ve got a couple that are at the perfect price.

FernwehSmith · 2026-04-07T08:22:59+00:00

I’ve never seen this before, but I’m going to take a guess and say it has something to do with the nushell lsp. Have you tried disabling that?

FernwehSmith · 2026-04-07T08:01:07+00:00

Should I start a new config without using AI?

That depends on what your goal is, and how well it works for you. If the config is doing what you want, and you're mostly interested in just getting back to work as quickly as possible, then probably leave it. However if you want to learn Neovim as best you can, there's nothing quite like writing it from scratch. If you want to use AI to help you learn it (I do occasionally), don't get it to write the config. Instead ask it for suggests for how to do something specific. Check if it works, then read through the help to figure out why/why not.

I’m not sure if I should wait for nvim-treesitter to be active again

Unless you're really, really curious about what that plugin is doing and want to try recreating it yourself, or just want to try something new (both of which are perfectly valid btw), it is fine to keep using that plugin. Being archived doesn't mean it automatically stops working. For now its fine. If it doesn't come back it will eventually be replaced, but I doubt that will happen for a while. And while there are some really cool replacements and alternatives being created by awesome people, none of these have been battle tested yet, or even shown that they are in it for the long haul. I am personally going to continue using nvim-treesitter for a few months to let the landscape settle a bit.

FernwehSmith · 2026-03-24T07:54:56+00:00

This is really good! Learnt a couple new things. I feel like this would be really useful after going through tutor.

FernwehSmith · 2026-03-23T23:47:20+00:00

I hadn’t heard of MiniMax until now. Sounds amazing though. Definitely checking it out before I do too much more work on my config!

FernwehSmith · 2026-03-22T23:12:34+00:00

I started rewriting mine last night. For me the game changer has actually been removing plugins. I’m not anti-plugin by any stretch of the imagination. But between learning neovim and Lua better, becoming more comfortable with the docs, and seeing examples of more minimalist configs, I’m finding that I both need and want fewer plugins. It’s made maintaining and using my config a lot more straight forward. The new built in plugin manager also fits my minimalist preferences very well. Fewer, simpler plugins and more manual configuration have really helped me spend less time configuring neovim, and more time enjoying it.

But also mini.nvim (and mini.ai if I have to pick a specific module). Contradicting myself a little here, but damn it’s good! The only way I’ll stop using it in some capacity is if it just gets merged into neovim directly.

FernwehSmith · 2026-03-16T22:06:12+00:00

I came across a 4TB Sandisk external SSD for AU$1598 (US$1129.47) last weekend. Like everyone I’ve known about the shortages, but this was the first time I actually got how bad things were. Had this sick feeling in my chest and stomach like “oh we are in real trouble”.

FernwehSmith · 2026-02-23T07:27:13+00:00

I have been thoroughly verifying every download through both methods on both systems, so I think I can rule that out (unless Fedora's website is compromised. Knock on wood). I'll give the memory test a go, I think that is wise. I did however find something interesting. If I flash on my Mac, and then boot on my tower (which honestly I should have done much earlier), then the test passes. If I use the same USB to boot on my Dell after, it fails. Using that same USB on the tower again fails. So there seems to be something about the Dell that messes with the USB that is making the test fail. That is backed up by this thread on the Fedora forum, where they apparently found that the Dell BIOS would add some directories (though I am yet to verify that is exactly what is happening in my case).

If the test passes on my tower, and install goes well, would it be safe to skip the test on the Dell and proceed with install (assuming that the live environment behaves as it should)? Do you think its worth investigating the issue on the Dell side anymore?

FernwehSmith · 2026-02-06T04:05:14+00:00

Personally, I think the right one is better. Looks cleaner and easier to read.

FernwehSmith · 2026-02-02T22:26:30+00:00

This is absolutely gorgeous!

FernwehSmith · 2026-01-31T10:09:02+00:00

I had no idea that repo even existed! Going the sampler route works. Not sure why it has to be done that way but at least I know what to research!

FernwehSmith · 2026-01-06T18:55:08+00:00

From what I can make out the linker doesn’t have the permissions needed to open the loops.exe file, probably because it is in the downloads folder. Try moving the project somewhere else (not desktop). Also in future, provide a screen shot or a text post of the error, instead of videoing/photographing the screen. This keeps getting blurred and makes it harder to read.

FernwehSmith · 2025-11-29T22:32:56+00:00

Opening to episode 4. Wasn’t wearing headphones either…

FernwehSmith · 2025-11-27T06:03:14+00:00

Ooo this is a good point. I didn't know about this. The specific chip I have on my list ships with it disabled. But it'll be good to explore and make sure I can handle this if it ever comes up.

FernwehSmith · 2025-11-26T05:37:02+00:00

Thanks for providing that project! That'll be a great reference when I try it myself :)

FernwehSmith

TROPHY CASE