seemless workspace navigation

[inadicis]

when trying to go up/down but reached the last pane in the current workspace, switch to the next workspace in this direction.

I have (vibe) coded this in my fork, tell me if interested i'll create the PR

[paulbkim-dev]

You're welcome to submit your PR, just make sure you actually have read your code.

[imagirom]

Before finding this issue and seeing @inadics fork, I built the same thing with some extra functionality: Jumping to the previous/next tab on left/right on the leftmost/rightmost pane.

@inadicis you raised this first, so I don't want to jump the queue. Do you want to open a PR yourself, otherwise I would go ahead.

@paulbkim-dev before I open a PR, two things I'd like to agree on first:

1. Opt-in. It sits behind HERDR_NAV_SPILL=1, off by default - Silently landing in another workspace is a bigger surprise than a key that does nothing. Let me know if you would prefer if it were on by default.
2. Scope. I also did left/right → previous/next tab, since that's the other half of the i3 behaviour it's modelled on. I find it super convenient, do you want the functionality?

[inadicis]

@imagirom feel free to go for it! I can work on it first on the weekend anyway, i would then review your logic if you want.

[paulbkim-dev]

Before finding this issue and seeing @inadics fork, I built the same thing with some extra functionality: Jumping to the previous/next tab on left/right on the leftmost/rightmost pane.

@inadicis you raised this first, so I don't want to jump the queue. Do you want to open a PR yourself, otherwise I would go ahead.

@paulbkim-dev before I open a PR, two things I'd like to agree on first:

1. Opt-in. It sits behind HERDR_NAV_SPILL=1, off by default - Silently landing in another workspace is a bigger surprise than a key that does nothing. Let me know if you would prefer if it were on by default.
2. Scope. I also did left/right → previous/next tab, since that's the other half of the i3 behaviour it's modelled on. I find it super convenient, do you want the functionality?

Opt-in seems to be a good path as this is kind of beyond the scope of "vim" navigation, but nothing stops us from defining what "vin" in our project is supposed to mean! As for #2, blanked out for a moment that's a wonderful idea too. Go for it!