-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Verify sway commands match i3 commands #2336
Comments
There are at least some commands that don't support the same boolean representations, for example focus_wrapping. sway only allows yes, no and force. i3 allows anything. |
We should probably use something similar to eval_boolstr ourselves. |
Made a start. Most seems to be there, mainly issues of documentation.
|
Thanks for putting that list together, much appreciated! I went through and crossed out some things that don't make sense for sway to implement.
Can you elaborate on these? Are these just differences with i3 rather than things sway is missing (save for better
These aren't present on master, was this list prepared against 0.15? |
I accidentally started on the 0.15 docs and when I switched to the 1.0 docs I forgot to check ones that were removed. The ones that I put "can be command" means that in i3, they're only supposed to be used in the config file but in sway they can also be executed at runtime. I don't know if you want to change it. Otherwise, it works as well as in i3. I also noticed a few markdown escapes I missed, I'll fix that. |
Gotcha, thanks |
Actually, if primary outputs aren't being supported you can mark them off. |
Good call, updated. |
i3-gaps:
|
I noticed that "tiling" and "floating" criteria do not work. |
Thanks @martinsb, @RyanDwyer fixed that in #2755. |
All done! Special thanks to @ianyfan for their hard work on shoring this up. |
Hooray! Thank you so much @SirCmpwn and all contributors for making this happen. This project is so exciting, as is |
New stuff in i3 4.16:
|
Can you open a new ticket for those things? |
A new ticket for each or a single for all? |
Up to you. |
disclaimer: never used i3 and really new to this all. |
Should I open a new bug? |
Yes. And send a patch |
That's total horseshit. |
What about |
|
You're right, appearently this is what the i3 guide says. |
You can just replace it with
No, there is no way to read an environment variable's value into a sway variable |
You can use command substitution in |
Couldn't find a more relevant issue for this:
Is that a bug, an intentional divergence, or an oversight? Also, @RedSoxFan, i3's In interpreting my 450 line i3 config file, those are the only two stumbles sway had. |
I think this is an oversight since they don't really have any relation to modes since they are not scoped. I'll submit a PR to allow it -- Submitted as #3940
I have no problem submitting a PR to add this for i3 compatibility and just documenting that the fallback is always used and the command only exists for compatibility with i3 configs. @ddevault @emersion any objections? |
I'd rather not implement |
Why is |
Find a list of i3 commands and make sure we have all of them in sway (at least all the ones we want to have). Double check that each sway implementation supports the same arguments as the i3 equivalents.
Criteria:
Commands:
[--no-startup-id]primary|<output> (sway: no primary)primary|<output> (sway: no primary; allows "window")shmlogshmlog <size_in_bytes>shmlog on|off|togglerestartbar hidden_state hide|show|toggle [<bar_id>]bar mode dock|hide|invisible|toggle [<bar_id>]Configuration:
set_from_resource $<name> <resource_name> <fallback>[--no-startup-id]<command>ipc-socket <path> (default: /tmp/i3-%u.XXXXXX/ipc-socket.%p)force_xinerama yes|no (default: no)primary|<output>tray_output none|primary|<output>Sway-exclusive:
clipboard <content>seamless_mouseThe text was updated successfully, but these errors were encountered: