Search

Items tagged with: neovim


👋 #introduction

Front dev (React/TS) from France. Rest of the time I'm deep in my homelab and self-hosting way too much.

Big on split keyboards (Corne v4, Voyager) and a Neovim config that'll never be done. I live in the terminal.

Also build side projects, like Blindtus (blindtus.com), a daily movie & TV guessing game.

FR/EN, come say hi.

#Neovim #SplitKeyboards #SelfHosted #dev


We have math now! This is built into NorgUI and supports roll-your-own solutions.

I think there’s two things to do before release now:
⁃ Fix state management (I want to match what I have in other apps for maintenance)
⁃ Extract the editor to a library NorgEditor

#ios #iosapps #iosdev #neorg #norg #neovim


A minimalist logger for neovim users:

vim.api.nvim_create_autocmd({ "BufRead", "BufNewFile" }, {
pattern = "*.log",
callback = function()
vim.keymap.set("i", "<CR>", function()
return "<CR>" .. os.date("!%Y/%m/%d %H:%M: ")
end, { expr = true, buffer = true })
end,
})

Every time you press return, it prefixes the next line with a timestamp. So type in a callsign, wait for the next one, hit return, and start typing.

#amateurRadio #neovim









Sensitive content


Hey everyone! I know I've been quiet on here for a while. I've been working hard to finish and publish a project. I also documented it using Read the Docs.

Opal Version 3 is a command line framework for Bash users. There a new Bash scripting library that makes it much easier to write shell scripts, and a great way to power your dotfiles.

andrewwoods.net/blog/2026/opal…

Check it out!

#bash #shell #dotfiles #neovim #vim #developertools #MacOS #Linux #software


If you are seriously thinking about learning #Vim / #Neovim, do yourself a favor and proceed as follows:

1. Grok ed(1).
2. Grok vi(1).
3. Ask yourself whether you really need anything ed(1) and vi(1) don't provide.

If your answer to step 3 is "yes", go ahead. But first, do steps 1 and 2.

Here is how to do step 1: Read the man page (it's rather short), read "Ed Mastery" by @mwl (those two steps are interchangeable and even parallelizable), then use it consistently.

Here is how to do step 2: Read the man page (it's rather short as well, though not as short as ed's), then use it consistently.

Also, have a look at stackoverflow.com/a/1220118.

#vi #ed



What options should I use for rust programming for nvim?


I am very new to nvim in general, and lately I have been trying to see if I can get configured to work better for rust programming (simple stuff, like proper language highlights, automatic formatting, if not too much work have rust-analyzer to sometimes check what is being done once in a while).
I tried to check online what people post about this subject, and more often than not I am lead to guides and explanations that clearly do not work with the more recent versions of nvim. And in some cases, they shove so many plugins that I lose count (and many times tried to change stuff like init.lua just to end up with a broken install).

So my questions are:
- What options can be used by nvim itself that makes it more suitable for rust development (excluding plugins)?
- If plugins must be used to have more advanced features, what are they and what are the best practices to add them to nvim?

EDIT: typos


@t_var_s
I hate to be the bearer of bad news, but #vim and #neovim are ai slop now.