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

Workspace order in bar does not maintain numerical order #59

Open
kgilmer opened this issue Jul 3, 2019 · 3 comments

Comments

2 participants
@kgilmer
Copy link
Member

commented Jul 3, 2019

It seems that at times workspaces are shown on i3bar out of numerical order.

STR

  1. create and add windows to workspace 1 and 2
  2. create workspace 17
  3. create workspace 5

Expected behavior: workspace 5 appears between 3 and 17 in bar
Actual behavior: workspace 5 appears after 17 in bar

@kgilmer kgilmer self-assigned this Jul 3, 2019

@kgilmer kgilmer added the bug label Jul 3, 2019

@kgilmer kgilmer changed the title Workspace order in bar intermittently random Workspace order in bar does not maintain numerical order Jul 3, 2019

@kgilmer

This comment has been minimized.

Copy link
Member Author

commented Jul 4, 2019

Fix pushed to regolith-stable.

@kgilmer kgilmer closed this Jul 4, 2019

@plagasul

This comment has been minimized.

Copy link

commented Jul 16, 2019

I am up to date and still getting this problem when workspaces automatically dissappear because they are empty. For example:

  • I open 3 workspaces
  • 1 and 2 are removed automatically because no windows are in them, only 3 remains in the bar
  • I press super+1 creating workspace number 1, which is placed second in the bar, after number 3
@kgilmer

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2019

Hi @plagasul , I am guessing that you have older i3 config files. When package updates occur, they will not overwrite your existing i3 file. If you haven't made any changes to them that you care to keep, can you remove all files in ~/.config/i3-regolith/ and log back into your session? If you have made changes, maybe just rename them, log back in, verify your issue is fixed and then merge your updates back in?

@kgilmer kgilmer reopened this Jul 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.