Expected behavior of the wanted feature
For the purpose of testing my session management implementation with a real application, I want to add session management support to mpv. The interface would be as follows:
~$ mpv --help
Basic options:
--session=name the name of the wayland session to create or restore
This would default to the empty string. mpv would then compute hash($XDG_CURRENT_DESKTOP, session_name) and look up the resulting string as a file name under ~/.state/data/mpv/sessions/. If found, it would use the contents as the wayland session id.
If a new session is created, mpv saves the new session id in that file.
The session would contain a single window, the mpv window, which the compositor would then restore fullscreen/on the workspace/on the output where it was the last time the session was used.
What do you think?
Alternative behavior of the wanted feature
No response
Log File
No response
Sample Files
No response
Expected behavior of the wanted feature
For the purpose of testing my session management implementation with a real application, I want to add session management support to mpv. The interface would be as follows:
~$ mpv --help Basic options: --session=name the name of the wayland session to create or restoreThis would default to the empty string. mpv would then compute
hash($XDG_CURRENT_DESKTOP, session_name)and look up the resulting string as a file name under~/.state/data/mpv/sessions/. If found, it would use the contents as the wayland session id.If a new session is created, mpv saves the new session id in that file.
The session would contain a single window, the mpv window, which the compositor would then restore fullscreen/on the workspace/on the output where it was the last time the session was used.
What do you think?
Alternative behavior of the wanted feature
No response
Log File
No response
Sample Files
No response