bufferline mouse action

[hunterliao29]

#5274

[gibbz00]

Maybe not the best to present two features in the PR but I'm guilty of it myself 😅

Anyhow, could the buffer-nth operations be incorporated into the default buffer-next and bugger-prev? Whereby 1 is the default unless a number is specified before the motion. Similar to how one can do 2w.

[hunterliao29]

Anyhow, could the buffer-nth operations be incorporated into the default buffer-next and bugger-prev? Whereby 1 is the default unless a number is specified before the motion. Similar to how one can do 2w.

I'm not sure if I understanding this correctly. Is this about 1 based index, where :buffer-nth 1 should go to the first buffer?

[gibbz00]

No, meaning that if I do 3 buffer_next i jump to the next buffer 3 times.

Naturally, 1buffer_next is then same as buffer_next.

[hunterliao29]

What should be the behavior of multiple buffer-nth 0s?

[gibbz00]

0buffer_next nothing?

[hunterliao29]

:buffer-nth 0 will switch to the first open buffer, :buffer-nth 2 will switch to the second if there is one and so on. It does not consider their current position like buffer_next. I am not sure if there is a use case for repeating it.

[AddictArts]

I'd like to see this feature happen, but seems to be stuck here. @hunterliao29 I think you might be missing what @gibbz00 is really asking. I think from reading, helix has a buffer_next code path; therefore, your buffer_nth is really duplicating in a sense what it does. The desire looks like just improving the existing buffer_next instead of adding yet another way to move between buffers. Maybe I have that wrong, but looking at code it does seem like one buffer motion code path could do both?

Apologies if I am way wrong or even slightly wrong, which happens.

[pascalkuthe]

Closing this as its quite stale.The bufferline and mouse support are also not a priority. Thank you for contributing!