Close open windows gracefully and save them as a session. And you can restore them when necessary manually or automatically at startup. Most importantly, it supports both X11 and Wayland! Main features: - Restore the previous session at startup. disabled by default. - Save running apps and windows automatically when necessary, this will be used to restore the previous session at startup. - Close running apps and windows automatically before Log Out, Restart, Power Off. disabled by default. - Close running windows gracefully - Close apps with multiple windows gracefully via ydotool so you don't lose sessions of this app (See also: How to make Close by rules work) - Save running apps and windows manually - Restore a selected session at startup (See also: #9). disabled by default. - Restore a saved session manually - Restore window state, including Always on Top, Always on Visible Workspace and maximization - Restore window workspace, size and position - Restore 2 column window tiling - Stash all supported window states so that those states will be restored after gnome shell restarts via Alt+F2 -> r or killall -3 gnome-shell. - Move windows to their own workspace according to a saved session - Support multi-monitor - Remove saved session to trash - Search saved session by the session name fuzzily For more information, please visit https://github.com/nlpsuge/gnome-shell-extension-another-window-session-manager/blob/feature-close-save-session-while-logout/README.md. Please report issues on Github.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 49 | Active |
| 48 | Active |
| 47 | Active |
| 46 | Active |
| 45 | Rejected |
| 44 | Rejected |
| 43 | Rejected |
| 42 | Rejected |
| 41 | Active |
| 40 | Active |
| 39 | Active |
| 38 | Active |
| 37 | Active |
| 36 | Active |
| 35 | Active |
| 34 | Active |
| 33 | Inactive |
| 32 | Rejected |
| 31 | Active |
| 30 | Active |
| 29 | Active |
| 28 | Active |
| 27 | Active |
| 26 | Active |
| 25 | Active |
| 24 | Active |
| 23 | Active |
| 22 | Active |
| 21 | Active |
| 20 | Active |
| 19 | Active |
| 18 | Active |
| 17 | Rejected |
| 16 | Active |
| 15 | Active |
| 14 | Rejected |
| 13 | Active |
| 12 | Rejected |
| 11 | Active |
| 10 | Active |
| 9 | Active |
| 8 | Inactive |
| 7 | Active |
| 6 | Active |
| 5 | Rejected |
| 4 | Active |
| 3 | Rejected |
| 2 | Rejected |
| 1 | Active |
(line 38 utils/string.js) Why `anki` in command?
Hi, The method _testFill() is used for testing. In this test method, I fill anki to ${appName}. And _testFill() is commented (line 32 utils/string).
Maybe should I comment or remove all code from line 30 to line 43? _testFill() method can be used by other js, but it really makes no sense, it just a testing method. anki is just a string, it can't be launched during loading the string.js and using String.prototype.fill(), it should be safe.
Sure, I'll remove it in the next version. :)
Thanks!
Another Window Session Manager