[mini.files] How to not change focus on j/k when navigating back

[myzb]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.files

Question

I hope I worded the title somewhat right.

I wanted to ask if there is a way to configure mini.files to not jump focus when you press j/k after navigating back.

It's hard to explain but, basically, this scenario:

• you have opened many windows, beyond what your screen/terminal width can display at a time
• you can navigate back and forth and focus naturally moves one window at a time
• You are now on e.g. window 4 and navigate back to window 3
• You press j/k
• Window 3 becomes window 4 and focus jumps

At least in my case navigating back (to window 3) and then pressing j/k to navigate to something within that window and then having focus "suddenly" jump and window 3 now suddenly becomes window 4 (and moves right) completely messes with my brain.

This is how I have set up mini.files in case it matters.

-- File Explorer
require("mini.files").setup({
	windows = { width_focus = 40, width_nofocus = 40, width_preview = 40 }
})

Link: https://github.com/myzb/dotfiles/blob/f2586b4a431eb733ab856cd4a93eb01d12c1ec36/.config/nvim/init.lua#L119-#L122

Edit: @drowning-cat made a nice video.

[drowning-cat]

Demo:

demo.mp4

[echasnovski]

Yes, this behavior is intentional. It is the result of the combination of the following goals:

• Keep any window's current line (i.e. "current file system entry") aligned with what is shown on the right. Otherwise it feels a bit confusing. This is responsible for right part of the currently navigated branch to get trimmed if cursor is moved from its position.
• Fit as much data on the screen as possible. This results into windows shifting to the right if right part of the branch is trimmed.

There are several solutions (from most to least robust):

• Use "go out plus" action (which is H by default) instead of just "go out" (which is h by default). This will trim the right part of the branch after each "go out" action. You can switch default keys similar to how it is shown for "go in" action.
• Manually trim the right part of the branch when needed. Use "trim right" action (> by default).
• Set config.windows.preview = true. This will always show a preview on the right which will allow to navigate (only) one step back without windows getting rearranged.

Hope this helps.

[drowning-cat]

I still think it's strange to automatically trim the tree with j/k, especially since we can manually trim it with >. But it can only become a problem when we try to perform operations on both the parent and the current directory at the same time (e.g., moving a file).

[echasnovski]

I still think it's strange to automatically trim the tree with j/k ...

It makes complete sense with window.preview = true, which in turn makes it more strange to not follow the logic with window.preview = false. But the main driver here is that I do think that it is confusing to allow "misaligned cursors": when cursor points to one file system entry, but to the right there is still information about another.

[drowning-cat]

Yeah, I think I get it. Creating multiple behaviors depending on the preview option isn’t very intuitive either.
By the way, I actually like the multiple cursor because I can see where I’ll jump :0. Though I can see why it might be a problem, since there might be multiple windows with different cursors.

[drowning-cat]

Thank you the explanations :/