Is it possible to jump directly to files in mini.visits?

[kikidotdirectory]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.visits

Question

I tend jump between the same group of files a lot and while I appreciate the 'core' function of mini.visits, I was wondering if there is a way to jump specifically to a file I have in mind rather than sifting through a UI. Reading through the documentation, it seems a lot of the mappings are for assigning labels or structuring lists.

The primary use case that I have is for when working with static sites, I want to quickly jump between a components, content, or configurations file, either to edit or make a file action.

Ideally, I would be able to have something per project that could be navigated to through something like

<leader>vCc - config
<leader>vCp - partials
<leader>vCl - layouts

so on and so forth.

I had looked into similar applications in mini.files but couldn't find a reasonable way to do per-project bookmarks like this. Ideally, they would be set from the buffer and be persistent & the only way to set marks in mini.files is through the lua configuration.

My initial instinct was to use something like arrow.nvim for this but came across a discussion where someone was asked why they were using arrow.nvim over mini.visits so I wanted to ask in case I've overlooked something that's supported. The closest thing I saw was MiniVisits.iterate_paths which is more cycling rather than jumping.

[abeldekat]

Hello @kikidotdirectory,

Yes, this is possible and demonstrated in this example. You have already mentioned iterate_paths. That function also accepts an index as n_times

local jump_directly = function(i)
  MiniVisits.iterate_paths("first", nil, { filter = "your label", n_times = i })
end

In mini.visits, the order of the visits is not fixed by default though. The order changes with recency-frequency. Sometime ago I configured visits to work more closely like harpoon, see this discussion.

Nowadays, I use the defaults, but with a per-project visits file. The mappings for first, last, backward and forward are good enough for my use-case.

[echasnovski]

I've marked this as the answer, because it does describe how 'mini.visits' might work in this case. But I would like to maybe further discuss this part:

Ideally, I would be able to have something per project that could be navigated to through something like

<leader>vCc - config
<leader>vCp - partials
<leader>vCl - layouts

so on and so forth.

Do you want these to be usable per project (like if there is a single "config", "partials", and "layouts" per project) or per file (like if there are "complimentary files" for any file; "file.c" <-> "file.h" or similar)? The first one is more suited for 'mini.visits' case, but the second is also possible. In both cases, though, you'd have to manually add necessary labels.

Another thing to consider here is that 'mini.visits' implements a more general "labels" approach: each visit can have multiple labels and thus be used/present/navigated in different ways. Like you can add custom labels (like config, partials, layouts, etc.) or you can automatically compute the label.

The bottom line is that although 'mini.visits' does have some suggestions about how it can be used, it is initially designed flexible enough for users to be able to implement their own workflows.

[kikidotdirectory]

Correct, I'm looking for a per-project visits. I was aware of custom labels but I ran into the following issues:

• My understanding is that the only way to add keymaps for them is manually setting them in the plugin configuration which I don't want to do as I bounce between projects quite often (if I am following what you mean by "manually").
• When I was reading MiniVisits.select_label() and MiniExtra.pickers.visit_labels(), it wasn't immediately clear to me how to pass a specific label through it from the call, let alone having a function create mappings for that per-project.

I've been using MiniMax as a means of learning Neovim so while I've been reading through all the documentation, I'm still trying to learn how everything interacts with each other so writing custom behavior is a little beyond me at the moment. At the moment, what seems most viable is figuring out how to work with mini.visits defaults until I have a bit more time to sit down with Lua.

[kikidotdirectory]

In mini.visits, the order of the visits is not fixed by default though. The order changes with recency-frequency. Sometime ago I configured visits to work more closely like harpoon, see this discussion.

I saw this when I was looking through the discussions! I wanted to say it looks very cool but definitely seems to be much more fully-featured than what I am trying to achieve and seems much more out of my current depth.