Bug on i3/sway workspace module. #30

Closed
opened 11 months ago by cruzjp · 4 comments
cruzjp commented 11 months ago

I'm running sway v1.5 on Gentoo with yambar 1.6.0-15-g3603ca9 built from source.

About the issue, when switching to workspace 10 with windows openned in other workspaces, the workspace 10 stay after the 1 and before the rest workspaces.

My module config:

  • i3:
    sort: ascending
    anchors:
    - string: &i3_common {margin: 5, on-click: "swaymsg --quiet workspace {name}"}
    - string: &default {<<: *i3_common, text: "{name}"}
    - string: &main {<<: *i3_common, text: , font: *awesome}
    - string: &surfing {<<: *i3_common, text: , font: *awesome_brands}
    - string: &misc {<<: *i3_common, text: , font: *awesome}
    - string: &mail {<<: *i3_common, text: , font: *awesome}
    - string: &music {<<: *i3_common, text: , font: *awesome}
    - focused: &focused
    foreground: ff5555ff
    - invisible: &invisible {foreground: ffffff55}
    - urgent: &urgent
    foreground: 000000ff
    deco: {stack: [background: {color: bc2b3fff}, <<: *std_underline]}
I'm running sway v1.5 on Gentoo with yambar 1.6.0-15-g3603ca9 built from source. About the issue, when switching to workspace 10 with windows openned in other workspaces, the workspace 10 stay after the 1 and before the rest workspaces. My module config: - i3: sort: ascending anchors: - string: &i3_common {margin: 5, on-click: "swaymsg --quiet workspace {name}"} - string: &default {<<: *i3_common, text: "{name}"} - string: &main {<<: *i3_common, text: , font: *awesome} - string: &surfing {<<: *i3_common, text: , font: *awesome_brands} - string: &misc {<<: *i3_common, text: , font: *awesome} - string: &mail {<<: *i3_common, text: , font: *awesome} - string: &music {<<: *i3_common, text: , font: *awesome} - focused: &focused foreground: ff5555ff - invisible: &invisible {foreground: ffffff55} - urgent: &urgent foreground: 000000ff deco: {stack: [background: {color: bc2b3fff}, <<: *std_underline]}
Owner

It is currently doing a simple lexicographical sort on the names (since workspace names can be anything, not just numbers), meaning "10" comes after "1"...

But that's obviously not what you'd expect. I think we can improve upon this by special-casing numbered workspaces.

It is currently doing a simple lexicographical sort on the names (since workspace names can be anything, not just numbers), meaning "10" comes after "1"... But that's obviously not what you'd expect. I think we can improve upon this by special-casing numbered workspaces.
dnkl added the
bug
label 11 months ago
Poster

Thanks for the answer.

Thanks for the answer.
cruzjp closed this issue 11 months ago
Owner

No need to close, I have an idea I would like to test.

No need to close, I have an idea I would like to test.
dnkl reopened this issue 11 months ago
Poster

No need to close, I have an idea I would like to test.

Sorry lol.

> No need to close, I have an idea I would like to test. Sorry lol.
dnkl closed this issue 11 months ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.