This website requires JavaScript.

polyphony/volute

Code Issues 5 Pull requests Projects Releases Packages Activity Actions

Keybinds for quickly moving between buffers #4

New issue

Open

opened 2026年07月14日 18:31:14 +02:00 by lumi · 0 comments

lumi commented

2026年07月14日 18:31:14 +02:00

Owner

Copy link

What I would like to do is implement some way to quickly jump between buffers, using keybinds such as alt+N where N is a number, and I would like to use the tab bar to display which keybind goes to which buffer.

The reordering of buffers in the tab bar could be handled using a pop-up with a keybind? Alternatively, it could be done with alt+shift+N. (where again N is a number) Kind of resembling control groups in an RTS.

We could also have the option of reordering these automatically based on some criteria, like most recently accessed.

What I would like to do is implement some way to quickly jump between buffers, using keybinds such as alt+N where N is a number, and I would like to use the tab bar to display which keybind goes to which buffer. The reordering of buffers in the tab bar could be handled using a pop-up with a keybind? Alternatively, it could be done with alt+shift+N. (where again N is a number) Kind of resembling control groups in an RTS. We could also have the option of reordering these automatically based on some criteria, like most recently accessed.

Sign in to join this conversation.

No Branch/Tag specified

main

master

dependabot/cargo/sha2-0.11.0

gh-pages

spellbook-2

filesentry

syntax-gd-gr

ropey-2

config_refactor_v2

spellbook

foreground-rulers

25.07.x

diagnostic-severity-glyphs

ropey2

inlay-hints-on-event-system

batteries

helix_syntax

register-history

append-changes-ensure-cursor-automatically

allowlist

config_refactor

get-lang-config-by-injection-layer

md-compositor-key-remapping-idea

fix-yaml-indents-debug

help-command

gui

termwiz

set-title

Labels

Clear labels

Highest priority issue

High priority issue

D (Medium-High)

Medium to high priority issue

Medium priority issue

Low priority issue

Lowest priority issue

Something is not as expected. For specifications or guidelines, an under-/overspecification is also considered a bug.

Regular maintainance tasks, version bumps, lint fixes

Documentation changes

This issue is a collection of other, related issues.

New functionality

Improve existing functionality

A specific work item. Can be part of an epic

Change related to CI or testing

👁️Reviewed

This issue or pull request already exists

👁️Reviewed

👁️Reviewed

This issue has been reviewed and a resolution is desired

👁️Reviewed

This issue won't be fixed

📋️Kind/Security

This is security issue

Archived

Somebody has started to work on this but abandoned work

Something is blocking this issue or pull request

Archived

This label is intended to be used when an outside collaborator is pursuing the completion of this issue, since they cannot be directly assigned to the task.

Feedback is required to reproduce issue or to continue work

Measure of time-to-implement and cognitive complexity of the task. "Hard" tasks usually take >15h to complete. Extremely unlikely to be suitable for first-time-contributors.

Measure of time-to-implement and cognitive complexity of the task. "Hard" tasks usually take 3h-15h to complete. Very likely not suitable for first-time-contributors.

Measure of time-to-implement and cognitive complexity of the task. "Medium" tasks usually take 30min-3h to complete. Likely not suitable for first-time-contributors.

Measure of time-to-implement and cognitive complexity of the task. "Easy" tasks usually take 15-30min to complete. Likely suitable for first-time-contributors.

Measure of time-to-implement and cognitive complexity of the task. "Trivial" tasks usually take 1-15min to complete. Very likely suitable for first-time-contributors.

Breaking change that won't be backward compatible

Good First Issue

This issue is a good task to take on if you are new to the project or the repository and looking to contribute.

No labels

D (Medium-High)

👁️Reviewed

👁️Reviewed

👁️Reviewed

👁️Reviewed

📋️Kind/Security

Good First Issue

Clear milestone

No items

No milestone

Clear projects

No items

No project

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

polyphony/volute#4

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?