Timeline for i3wm : start applications on specific workspaces when i3 starts
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 9, 2020 at 15:45 | history | suggested | Lubo | CC BY-SA 4.0 | Added "copy&paste" ready command to apply settings after change |
| Apr 9, 2020 at 14:55 | review | Suggested edits | |||
| S Apr 9, 2020 at 15:45 | |||||
| Mar 28, 2019 at 9:35 | comment | added | kittenparry | @LuísdeSousa some programs don't work with it like Spotify. For them you might write something similar to this for_window [class="Spotify"] move to workspace $ws10 where $ws10 is your workspace variable. | |
| Mar 28, 2019 at 9:33 | comment | added | Luís de Sousa | @kittenparry. Thank you for the suggestion, but still using the string from the xprop command the windows are not assigned to the desired workspace. | |
| Mar 27, 2019 at 3:34 | comment | added | kittenparry | @LuísdeSousa you xprop | grep CLASS in terminal, your mouse pointer changes into a crosshair, you click on the program you want to get the class of and use the second variable that comes up in your terminal. Example result for Chrome: WM_CLASS(STRING) = "google-chrome", "Google-chrome" | |
| Mar 25, 2019 at 7:29 | comment | added | Luís de Sousa | This works for some applications, but not for others. I suspect it could be related with the string used in the class argument. Is there any way to know exactly to which class is an application associated? | |
| May 9, 2017 at 8:12 | review | Low quality posts | |||
| May 9, 2017 at 8:57 | |||||
| May 9, 2017 at 7:44 | history | edited | phk | CC BY-SA 3.0 | formatting |
| May 9, 2017 at 7:25 | review | Late answers | |||
| May 9, 2017 at 7:44 | |||||
| May 9, 2017 at 7:14 | history | edited | head-shot | CC BY-SA 3.0 | deleted 53 characters in body |
| May 9, 2017 at 7:07 | review | First posts | |||
| May 9, 2017 at 8:09 | |||||
| May 9, 2017 at 7:07 | history | answered | head-shot | CC BY-SA 3.0 |