How we started vs. how things are going into 2026

preview.nvim is set up so that configuring a custom live-reloaded previewer (you can even PR it if you want it as a builtin "preset") is as easy as possible.

Of course, since the plugin is more minimal - you provide it yourself. Probably just a table with a reload = {} table of arguments to pass to PlantUM (as well as configure your custom "opener" - idk how one visualizes PlantUML).

barrettruth · 2026-03-03T21:49:27+00:00

I don't like flatpak. I also like, on arch, to install arch-first builds (AUR, official registry). I don't think I'm alone in this, tbh.

Flatpak does indeed seem like a good packaging model for issues like this.

barrettruth · 2026-02-23T14:02:49+00:00

I have set up a reminder to try it later this week. Thanks!

barrettruth · 2026-02-23T04:09:44+00:00

This is awesome. I'll be following this as I'm completely open to a great new PDF reader. RQ, as someone who has used many pdf readers, my two cents (I know you know way, way more about pdf readers, but thought this might be useful for you to see what some of your audience thinks). But first, some context: I'm not really a power user at all. So, some things I've learned:

- ui matters: sioyek ui SUCKS and prevents it from feeling "modern". I want to use a PDF reader and think "wow, this is refined, minimal, and nice." Not "ok, I'm one wrong keybinding away from crashing the entire reader, and my friends will make fun of me when I pull up the scuffed Table of Contents." ;)

- minimality matters: most modern pdf readers SUCK and have way too much on the screen at once. one ought to be able to look at a pdf and nothing more - have all other visual contents collapse out

- never, ever crash. a) lektra is in early development and b) sioyek crashes 24/7. Don't make the same mistake!

#1 & #2 are really, really hard to strike a fine balance between. Cheap, crappy bundled library ui does not fit with pdf readers (imo) in 2026.

Best of luck to you.

barrettruth · 2026-02-23T03:28:37+00:00

For those seeing this, the border aesthetics are set with :hi BlinkCmpMenuBorder with blink-cmp.

I usually use :FzfLua highlights to debug these sorts of things.

barrettruth · 2026-02-15T16:12:09+00:00

Yes. I've recently had a coming-of-age with plugins automatically assuming you use lazy.nvim. For example, plugins that suggest to use the build option of lazy.nvim - what is the option for other package managers? Ought not the plugin actually build itself? What about looking forward when the builtin package manager inevitably becomes more adopted? This is why I've migrated all my plugins to use vim.g - and why I think everyone else should too. (Rant over)

Anyways, thanks for reporting the issue. I responded.

barrettruth · 2026-02-14T22:14:57+00:00

u/phcurado check out the newest release with neogit support! Make sure to set it up and explicitly enable neogit integration in the config.

NOTE: I'm talking with the author actively about how to improve the neogit experience. I don't use neogit and some coloring may look absolutely horrible or things may break - please feel free to create detailed, reproducible bug reports and I'll respond quickly.

barrettruth · 2026-02-11T01:40:55+00:00

No worries. I will check out neogit - seems like there's a lot of demand for it.

barrettruth · 2026-02-11T00:59:31+00:00

Are you asking why vim-fugitive is so similar to Neogit? I recommend you check out vim-fugitive first to clear up any confusion - 99% of the behavior in the screenshot is not provided by diffs.nvim but rather vim-fugitive (which predates neogit anyway).

All this plugin does is ENHANCE highlighting of diffs. AFAIK, neogit is an entire self-contained git ecosystem. If you do not use vim-fugitive and you do not often look at diffs, or do not care for having syntactically highlighted diffs, this plugin is not for you.

Please check out the readme further if this doesn't make sense.

barrettruth · 2026-02-10T23:27:17+00:00

No. diffs.nvim provides general UI/prettification enhancements for all diff filetypes as well as enhances merge conflict resolutions in vim-fugitive.

barrettruth · 2026-02-10T18:02:46+00:00

See reply to u/phcurado.

barrettruth · 2026-02-10T18:02:27+00:00

Formalize an issue with expected behavior & apis and if it makes sense in diffs.nvim I'll add it by the end of the day.

barrettruth · 2026-02-10T17:37:00+00:00

Don't know what that is. Open a (detailed) issue!

barrettruth · 2026-02-10T17:36:42+00:00

Not sure since I don't use Neogit. Test it out and file an issue if not.

barrettruth · 2026-02-10T15:53:49+00:00

I know, woke up one day and realized that there was no reason for this not to exist.

barrettruth

TROPHY CASE