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

Sway defaults to workspace 10 on nth monitors #6041

Open
philipwilk opened this issue Nov 5, 2024 · 5 comments
Open

Sway defaults to workspace 10 on nth monitors #6041

philipwilk opened this issue Nov 5, 2024 · 5 comments

Comments

@philipwilk
Copy link
Contributor

The default workspace in the hm config is 10 - but this can be solved by setting defaultWorkspace to 1. However, this does not fix the default workspace for nth monitors also being 10 - ex, plug in laptop to an external monitor and that monitor defaults to workspace 10 instead of 2 or 3 (whatever your next unused one is)

Originally posted by @philipwilk in #4636 (comment)

@philipwilk
Copy link
Contributor Author

Copy link

stale bot commented Feb 4, 2025

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

  • If this is resolved, please consider closing it so that the maintainers know not to focus on this.
  • If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

  • If you are also experiencing this issue, please add details of your situation to help with the debugging process.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

@stale stale bot added the status: stale label Feb 4, 2025
@philipwilk
Copy link
Contributor Author

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.
If you are the original author of the issue

If you are not the original author of the issue

Memorandum on closing issues

I am going to explode you

@KoviRobi
Copy link

If you want, you could help with #6546 -- I have done the i3 side of things, but haven't yet touched sway

@philipwilk
Copy link
Contributor Author

Will have a look later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants