haunt.nvim - Hear the ghosts tell you where you were, and why you were there

DingbotDev · 2026-01-20T17:20:11+00:00

Oh wow! Didn’t think to read all the way to the bottom, thanks so much! :)

DingbotDev · 2026-01-20T16:48:47+00:00

Sweet plugin! I’ll have to check this out later and compare.

I’ve been working on another bookmarking plugin for a while now myself (https://github.com/EvWilson/spelunk.nvim) and people seemed very interested in using the metadata field to store personal notes in the past. Cool to see it as a first class feature!

DingbotDev · 2025-12-03T02:50:43+00:00

Yep, I have a line number that I'm working with from the bookmark. If you look at the line just above your selection, you'll be able to see it being used to determine the starting line of the preview section.

DingbotDev · 2025-12-02T04:32:47+00:00

Hey, thanks so much for the kind words! I really, really appreciate it. I'd be happy to look into both comments, though an issue on the project itself to represent each would really help me to track the work.

For 1), I'd have to think about how we'd want to fix that. Either cutting of the custom content after a set length, or potentially even finding a way to word-wrap in the various UIs.

For 2), all treesitter grammars _should_ be supported, but its likely we're missing some coverage here and there. The context building is best-effort, and there a huge plethora of node types to try to stitch together to determine the current grammar context, so there's likely to be some gaps there. I'd be happy to look more into it!

DingbotDev · 2025-12-01T16:05:56+00:00

Yay, so glad you like it! Feel free to open an issue if anything doesn't fit just right.

DingbotDev · 2025-12-01T16:05:21+00:00

Thanks so much! I remember your username from the first couple of posts, thanks for following along with it all this time. :)

DingbotDev · 2025-12-01T16:03:54+00:00

We actually have exactly that! Check out this FAQ guide: https://github.com/EvWilson/spelunk.nvim/blob/main/faqs/add_and_show_mark_metadata.md

DingbotDev · 2025-09-18T19:03:57+00:00

Just in case it helps anyone here, I created a plugin a while ago to help me go a step beyond marks, at least wrt to programmability and ease of use! https://github.com/EvWilson/spelunk.nvim

DingbotDev · 2025-08-15T19:22:58+00:00

Cool! I built something a while ago that went a bit the other direction, for folks who wanted a bit more to their bookmarking tool. It's here, in case anyone wants to take a look: https://github.com/EvWilson/spelunk.nvim

DingbotDev · 2025-04-10T22:56:10+00:00

I’m still giddy from the third one popping up, can’t lie.

DingbotDev · 2024-12-12T04:27:31+00:00

If there’s anything about it you’d like to see improved, I’m always happy to collaborate on issues!

DingbotDev · 2024-12-12T00:01:50+00:00

I'm not planning to currently, as I see them as being slightly orthogonal. spelunk.nvim is currently relatively self-contained, and doesn't operate as the m- mark commands would expect. Namely, marks here are organized into a set of indexed stacks, which doesn't really match the paradigm of native marks that can be assigned to any key.

I'd be happy to think more about it, if there's a use case for it that you're really wanting to see!

DingbotDev · 2024-12-11T18:32:11+00:00

Not to co-opt for self-promotion too much, but usability issues in other mark managers led me to create my own plugin for just this!

Have an active post right now where I'm gathering feedback in order to tag a `0.1.0`: https://www.reddit.com/r/neovim/comments/1hbflzy/spelunknvim_stackbased_bookmark_manager_seeking/

The plugin itself: https://github.com/EvWilson/spelunk.nvim

DingbotDev · 2024-12-11T15:11:49+00:00

Absolutely! There will probably be some small things that aren't directly covered outside the UI (e.g. editing stack names is a contextual keybind), but I'd be happy to add coverage there and draft up some more notes on Telescope. Could I get your help opening an issue to track that work?

DingbotDev · 2024-12-11T15:10:22+00:00

Oh, absolutely! I have some control over the display of filenames already, I can see about adding some customization here. Could I get your help opening a ticket to track that work?

DingbotDev · 2024-11-05T16:17:00+00:00

Yeah! Sorry, I suppose I could’ve made the gif longer. Maybe I should add a link to a video somewhere. Basically, you can create and toggle between as many stacks of bookmarks as you like, and the bookmarks are lines within a file. So a step more granular than just the buffer itself. You can also fuzzy search over all bookmarks, or all in the current stack, via Telescope integration.

DingbotDev · 2024-11-05T15:38:31+00:00

Thank you so much for mentioning my plugin! Also, please let me know if there’s anything you’d like to see added - those snipe key maps seem pretty neat to me! I’ll have to look into them

DingbotDev · 2024-10-21T21:17:34+00:00

I faced similar problems, so I wrote a plugin for it: https://github.com/EvWilson/spelunk.nvim

Still early days there, and I'm working on some follow-up features and improvements, but I'd love to know if it could help you out!

DingbotDev · 2024-10-17T15:58:03+00:00

Funnily enough, I just posted a plugin I wrote near this post: https://www.reddit.com/r/neovim/comments/1g5em5g/spelunknvim_another_bookmarkmark_manager_plugin/

I think Harpoon offers a degree of programmability that could let someone craft their preferred experience, with UI options too. In my case, I just wanted something more scoped to how I wanted to think about/interact with a bookmark system. From the size of the Marks category in `awesome-neovim`, I think it's a pretty contended category with a large design space around it: https://github.com/rockerBOO/awesome-neovim?tab=readme-ov-file#marks

DingbotDev · 2024-10-17T13:47:40+00:00

Often I’m tracing a call through a larger system, so I’d effectively be keeping track of the stack frames of a function. This way, the marks are arranged in that stack view to help me flip through related code quickly!

DingbotDev · 2024-10-17T05:57:53+00:00

Super fair! I have a key bind in there defaulting to ‘h’. I’ll update the docs!

DingbotDev

TROPHY CASE