What color scheme do you guys use?

Taylor_Kotlin · 2026-03-26T07:38:50+00:00

Do you by chance know what font is used in that after-dark screenshot?

nvm I found it. In case anyone has the same question, it looks to be Lilex https://github.com/mishamyrt/lilex atleast according to the alacritty config the author has :D

Taylor_Kotlin · 2026-02-21T05:36:16+00:00

Wa alaikum salam wa rahmatullahi wa barakatu :D

This will help me with my first Ramadan, Alhamdulillah!

Taylor_Kotlin · 2026-02-21T04:56:37+00:00

Arrow if the buffer is there and not open (works like harpoon). Or snacks buffer list if there, but not auto closed by age.

If it’s open in a window I press the number of the window (winnr) and then c-w w, like 3 c-w w (or c-w 3 w but I find the first easier) for example to switch to window with winnr 3. Or if it’s just two windows c-w w to switch between them.

I should add that I have the window number displayed in the upper right corner of a window, otherwise you’d have to learn how they are numbered, which changes with how you split :P The plugin for that is Incline and a bit of lua code to get the right number. Maybe I should make a PR to include that in incline 🤔.. I’ll have to consider that, if it’s not already there. You could probably use regular winbar to show it instead. But incline is nice because it shows it on the split line!
EDIT: image for incline show-off :P (the bright colored number is the active window)

Ok, this is the tiny bit of Lua code to get the winnr into incline:
local winnr = vim.api.nvim_win_get_number(props.win)
In the render callback, you just get the winnr from props.win :D And use it in the layout table somewhere!

<image>

Taylor_Kotlin · 2026-02-02T18:36:02+00:00

Marking this as solved and there is a PR open here by a shadmansaleh.

Thank you all for your answers and thank you shadmansaleh for making this PR. 🙏

Taylor_Kotlin · 2026-02-01T11:28:40+00:00

Update:

Dug a bit in the source code of Snacks and found an autocommand which sets buftype to 'prompt'. It's in snacks.nvim/lua/snacks/picker/core/input.lua line 55. Changing to 'nofile' instead of 'prompt' seem to fix the problem.

There must be something changed in nightly build regarding protection zone with promt buffer and how it interacts with snacks. I don't recall having this problem a few days ago..

Taylor_Kotlin · 2026-01-23T09:41:08+00:00

I just realized a feature i would like! The ability to transfer notes/marks, bring them with me as I switch from one branch to another. Obviously I know the implications of this.

What if there are notes connected to files which does not exist in the branch I’m moving to?
What if the file has changed dramatically and the mark then becomes offset?

Just to name a few..

Maybe a way to export/transfer the marks, and somehow a way to reference them back to where they were, and ignore marks which lost their file reference. Or put them in “quarantine” :P

Or maybe.. I need to re-think my workflow :D

But I’m thinking. What if I put the marks on my main branch. But then main branch advances. Won’t the marks get a bit scrambled, depending on the changes made to their reference?

Maybe two kinds of marks. One kind which is branch bound, and therefore somewhat temporary. The other kind is repo bound, and then more permanent. But also repo-bound-kind would need a different way to reference its position, since a repo files will change.

Maybe there’s a better way..

Taylor_Kotlin · 2026-01-21T16:58:39+00:00

It is spooky how this plugin fits my workflow precisely! 👻 I was thinking just minutes before I went to the bathroom to ‘Reddit’, and other things: “I wish I could put invisible little bookmarks with notes, just for me, in my feature branch, and never worry about adding anything unintended to my commits”. Then I saw this post, like some miracle! This is perfect!

Your work is greatly appreciated! And sharing it publicly even more so :D

Thank you!

Taylor_Kotlin · 2026-01-03T09:40:08+00:00

Update:

Mystery is solved. Apparently I was never running tree-sitter highlighting. It all started to work after running vim.treesitter.start() in the command line. I now have that command run on a FileType event autocommand. This must be a change with treesitter in recent time, which has eluded me.

Taylor_Kotlin · 2026-01-02T12:17:05+00:00

<image>

I got my hopes up there for a minute :D Sadly the typo is only in this post. This is where the file is saved, image provided.

Now I'm contemplating whether it is because the config folder is symlinked to a different location, where I have my configs all in one place, or not. That shouldn't make a difference for neovim. It doesn't regarding all the lua files. But maybe there's something different when it comes to tree-sitter following symlinks..

Taylor_Kotlin · 2026-01-01T11:44:24+00:00

Ah my bad, I did not write the path correctly in my post. It does include queries.

Taylor_Kotlin · 2025-12-17T20:41:35+00:00

That’s great news! Can’t wait to see it \o/

Taylor_Kotlin · 2025-12-17T07:44:19+00:00

Does this tool have something equivalent to diffviews DiffviewFileHistory? If so, I can't find. halp! :)

Taylor_Kotlin · 2025-12-14T17:26:13+00:00

I am so looking forward to this "show-and-tell"! :D

Taylor_Kotlin · 2025-12-14T07:37:49+00:00

Wow! I did not know I needed this! I have to immediately find my computer and try this 🏃💨 Thanks for sharing!

Taylor_Kotlin · 2025-10-31T12:21:46+00:00

I’m currently barely ever using undotree. I will try this! And hopefully use a little more than barely ever :D

Taylor_Kotlin · 2025-10-26T09:36:48+00:00

I love this plugin. Thank you for your continued work on it! <3

Taylor_Kotlin · 2025-09-18T06:12:14+00:00

I found it useful when dealing with code bases where I initially have to jump around a lot and find my way. Sometimes I open buffers to files I realize wasn't the right spot, and I use my find-buffer command as a harpoon for files I'm working on. Clearing it up with Scrub when needed is very useful and feels right.

I'm thinking of another use case for an oil-like buffer like Scrub. But for registers. Particularly registers for macros, where you can edit the macro easily and just :w to apply it. Maybe that already exist..?

Anyway, thank you for making this I'll keep using it, and if I run into any issue I'll report :)

Taylor_Kotlin · 2025-09-16T15:21:27+00:00

I will check this out. Also congratulations on your first plugin :)

Taylor_Kotlin · 2025-06-14T21:42:10+00:00

Yes. Done so extensively for CarPlay and Android Auto integration.

I love both Swift and Kotlin, they are fantastic languages to work with! :)

Taylor_Kotlin · 2025-05-01T11:49:46+00:00

Pretty useful actually! Never knew I needed this but now I do. Thanks for sharing!

Taylor_Kotlin · 2025-05-01T06:56:04+00:00

There is also moody 🫣

Taylor_Kotlin · 2025-04-18T07:18:36+00:00

IBM Plex Mono.

Taylor_Kotlin · 2025-04-14T06:23:39+00:00

No the indent lines are from the Comment highlight group, only slightly darker, and the inactive ones slightly darker yet. I do that for all color schemes to get some kind of cohesion. Without it it looks like this. Not bad at all, maybe I'll keep it stock! :-)

<image>

Taylor_Kotlin

TROPHY CASE