Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No skipping number-colliding workspaces with workspace next/prev #4452

Closed
jolmg opened this issue Jun 28, 2021 · 3 comments · Fixed by #4578 · May be fixed by #4451 or #5157
Closed

No skipping number-colliding workspaces with workspace next/prev #4452

jolmg opened this issue Jun 28, 2021 · 3 comments · Fixed by #4578 · May be fixed by #4451 or #5157
Labels
4.19 bug reproducible A bug that has been reviewed and confirmed by a project contributor

Comments

@jolmg
Copy link

jolmg commented Jun 28, 2021

I'm submitting a…

[ ] Bug
[x] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

workspace next and prev skip workspaces that have the same number as current.

For example, having workspace 1, 2:foo, 2:bar, and 3, with 2:foo focused and doing workspace next takes us to workspace 3, skipping 2:bar. Being on workspace 2:bar and doing workspace prev takes us to 1, skipping 2:foo.

Desired Behavior

To not skip them.

Impact

When typically using more than 10 workspaces, this helps to organize them by using the numbers to categorize workspaces and group them. The digit keys can be used to quickly get to an area of workspaces and then select the correct workspace with workspace next/prev keybindings. This is similar to how one would quickly navigate a video on YouTube.

Skipping the number-colliding workspaces doesn't seem useful, so this might actually be a bug report.

[ ] This feature requires new configuration and/or commands

Environment

Output of i3 --moreversion 2>&-:

i3 version:
Binary i3 version:  4.19.2 (2021-02-27) © 2009 Michael Stapelberg and contributors
Running i3 version: 4.19.2 (2021-02-27) (pid 1413)
Loaded i3 config: /home/jol/.config/i3/config (Last modified: Mon 28 Jun 2021 02:00:47 AM PDT, 922 seconds ago)

The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3 
- Linux Distribution & Version: Archlinux last updated a couple of hours ago.
- Are you using a compositor (e.g., xcompmgr or compton): No.
@i3bot
Copy link

i3bot commented Jun 28, 2021

Please note that new features which require additional configuration will usually not be considered. We are happy with the feature set of i3 and want to focus in fixing bugs instead. We do accept feature requests, however, and will evaluate whether the added benefit (clearly) outweighs the complexity it adds to i3.

Keep in mind that i3 provides a powerful way to interact with it through its IPC interface: https://i3wm.org/docs/ipc.html.

@Airblader
Copy link
Member

I think I'd view this as a bug rather than a feature request. It seems only sensible that the command cycles workspaces in the order i3bar shows them.

@jolmg
Copy link
Author

jolmg commented Jun 28, 2021

@Airblader Yeah. I think I made a mistake in viewing this as a new feature rather than a bugfix.

@orestisfl orestisfl added the reproducible A bug that has been reviewed and confirmed by a project contributor label Oct 10, 2021
orestisfl pushed a commit that referenced this issue Feb 6, 2024
…4578)

eg if you have workspaces: { 1, 2:a, 2:b, 3 } and are on workspace 1,
then 'workspace next' should traverse 1 -> 2:a -> 2:b -> 3 -> 1 instead
of 1 -> 2:a -> 3 -> 1.

Fixes #4452
desmana pushed a commit to desmana/i3 that referenced this issue Apr 3, 2024
…3#4578)

eg if you have workspaces: { 1, 2:a, 2:b, 3 } and are on workspace 1,
then 'workspace next' should traverse 1 -> 2:a -> 2:b -> 3 -> 1 instead
of 1 -> 2:a -> 3 -> 1.

Fixes i3#4452
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.19 bug reproducible A bug that has been reviewed and confirmed by a project contributor
Projects
None yet
4 participants