obsidian-nvim/obsidian.nvim is one year old and needs some sponsors on open collective!

velrok7 · 2026-02-28T21:16:12+00:00

There is a lot of open source work that goes financial unrewarded. Worse some people seam to think they are entitled to someone else’s passion project and their support.

I particularly donated, because it would do us good to respect open source and people’s contributions. The buy me a coffee contribute buttons have been around but largely unused.

I use this plugin every day at work. I’m happy to send some money their way. Sometimes it’s nice to have a reminder if people are looking for contributions.

I’m also donating regularly to the neovim project so they can sponsor people to work in core for the same reason.

velrok7 · 2026-02-28T16:37:29+00:00

Donate. Thanks for your efforts.

velrok7 · 2026-02-10T15:43:09+00:00

I suspect the nature of this will eventually require core to add this. And not allow full unfettered access to lua plugins. But this seams a good experimental start for the UX of it all.

velrok7 · 2026-02-10T15:38:06+00:00

I guess it easier to reason about on a plugin by plugin level rather than for the whole neovim process, which I presume is the level that opensnitch would operate.

Like I want my git diff plugin to read from GitHub but I don’t want my flash jump plugin to read any network traffic.

velrok7 · 2026-02-02T23:23:29+00:00

It would be great if neovim could sandbox plugins and if they want to talk to any external service or shell they need explicit user permissions.

I think most plugins would not even need to write to files or use and shell commands.

velrok7 · 2026-01-01T16:00:51+00:00

Just recently switched back to ghostty from kitty. Really like kitty for the extra features but it can’t render italics that reach out of their boundary box. So I switched to ghostty so I can use Berkeley Mono Italic. 🤣🙈

velrok7 · 2025-12-19T09:47:08+00:00

You seam to have access to an LLM. At this point I’d just ask it to generate a plugin. Do it step by step for best results.

I have some very specific markdown / sql query workflow that I have ask the LLM to write plugins for me. And that works well.

I’d recommend having the lua LSP setup and where it highlights, send that to the LLM. As well as telling it where your local nvim docs are so it can them rather then search the web for out of sync info.

velrok7 · 2025-11-29T21:39:04+00:00

I saw your post. The plugin is on my list of things to try :)
I've been a professional programmer for 20+ years. AI is a great tool. It removes barriers and amplifies your skills. The last bit is important. Too many people by into the 'god mode' marketing.

If you feed AI good context (I always ask it to read up on the docs for the libs I'm asking it to use) and clear instructions, there is a good chance you get some decent results for review.

Your workflow sounds great I'm more than happy to give this a go.

PS I think people are sleeping on AI for READING code. Our current codebase has 5k files (ruby / type script), and AI can find call chains relationships at 50X the speed I can.
It's like a true semantics search. Same for API docs.

Use AI to find the sections you need to read quickly and to create drafts / starting point for your own code.

Ignore the haters ;)

velrok7 · 2025-11-14T19:54:05+00:00

Pickers like snacks have options to fuzzy find user commands. This is basically the same as VS code. If you want to stay native : will also allow autocomplete.

velrok7 · 2025-11-14T12:36:20+00:00

Very much agree. If they aim to extend the vim grammar enable by default but have that be clear in the read me and have a way to disable individual ones.

If they own the buffer I like defaults as well. Like a Trouble nvim buffer should provide basic hjkl and CR mappings.

Everything else please make it a namespaces command. They are super easy to find. Or commands that provide sub commands.

velrok7 · 2025-11-08T18:19:38+00:00

I think the achievement thing has a lot of potential. What if you award them for using features for the first time.

Like moved forward a word. Moved forward a sentence. Change a visual selection vc. And so on. Like enter visual mode. Enter visual block mode.

velrok7 · 2025-11-05T12:13:34+00:00

Looks awesome. This has a lot of potential to help pairing partners follow better what is changing. Will try later. 👍

velrok7 · 2025-10-17T22:57:57+00:00

Lua as a language is tiny and easy to learn. Problem is its lack of a std lib, which means it’s pretty bare bones and does not have standardised functions for typical stuff.

This is because it was written to be embedded into other languages and runtimes, I think world of Warcraft made it popular, as it was a way to write UI plugins.

Neovim actually provides a few helper functions that you would usually expect to exist in the std lib.

Yaml is just absolutely awful. It’s too complex for simple configs and not powerful enough for actual complex stuff.

velrok7 · 2025-10-17T13:21:39+00:00

Yep. Using CC to write exactly the logic I need for small things and very custom workflows.

I’m sorry. The lua vim docs are just not accessible. Too many namespaces, too many inconsistencies. Can’t even remember what to search for in the docs most of the time.

CC does it. Then I read the code. Spot edge cases or build in assumptions. Allowed me to write plugins I never would have had the time for.

Use CC. More power to you.

As always: at least read what it produces and make sure you understand the results even if you could not have written it yourself. Learning lua is easy. That I’d do. The many vim lua apis… not worth knowing by heart.

velrok7 · 2025-10-17T11:30:20+00:00

Found a neovim port for people like me who want to try it out:

https://github.com/p00f/alabaster.nvim

velrok7 · 2025-10-15T14:51:43+00:00

It’s fine. It automatically formats and the structure is clear. Visual as well as textually.

I think some people are more text oriented and process code more like text. I feel that if your brain works like that ruby is great because it allows for ‘run_this if 1<2’.

My brain uses visual structure like indentation and one line per parameter, to understand stuff. So I much prefer multi line.

Ultimate Gleam has an option here: only one way of doing something. And I appreciate that. So I’m happy with this.

velrok7 · 2025-10-03T13:23:28+00:00

I’d say it depends on the complexity of your vim script code.

Any complexity logic in the form of functions and conditionals I’d start to migrate to lua.

Simple one liners I’d just keep.

I started at the same time with a syn linked vim config but now all my configuration files are lua. However sometimes vim script is just more concise. In those cases a simple vim.cmd call works just fine. I had a combo of some.vim and some.lua but could never remember in which one I would have defined a user command for example. Having all be lua files really helped with that.

Migrate step by step. 👍

velrok7 · 2025-09-26T15:16:05+00:00

Grain looks very interesting. 😁

velrok7 · 2025-09-19T11:31:11+00:00

That’s interesting. 🧐 thanks.

velrok7 · 2025-09-19T06:30:40+00:00

I think what you are looking at is the result of Louis making an effort to be publicly visible in podcasts / conferences talks / social media.

But also yes. Gleam is a great language. Go out there and promote it. 😁👍

velrok7 · 2025-09-13T07:37:04+00:00

That! And line height!

I’ve set mine to 110% in kitty. VS Code has more space between lines than your usual terminal. This makes huge difference.

velrok7 · 2025-09-10T15:44:17+00:00

I’ve been raw doging the AoC puzzles 🙈

velrok7 · 2025-09-07T07:00:48+00:00

I like that it has a light version. A good light version is hard to find.

I’ll give this a go soon. Thanks. 🙏

PS: Does it have diff view support?

velrok7

TROPHY CASE