[ISSUE] Package request: spotifywm

[ISSUE] Package request: spotifywm

[pyramidhead52]

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

New issue by pyramidhead52 on void-packages repository

https://github.com/void-linux/void-packages/issues/29479

Description:
[spotifywm](https://github.com/dasJ/spotifywm): Set Spotify's WM_NAME before opening the window.

Spotify does not respect window manager rules. Any window manager that try to apply specific rules like starting it on a determined workspace or maximizing it on startup, has no effect, as Spotify doesn't set the WM_CLASS property before creating the window.

This one should fix the problem.

Re: Package request: spotifywm

[FollieHiyuki]

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

New comment by FollieHiyuki on void-packages repository

https://github.com/void-linux/void-packages/issues/29479#issuecomment-799841130

Comment:
Hmm it is just 1 source file, and is simple enough that it doesn't need any updates since 2016. Here you go:
```sh
$ wget https://github.com/dasJ/spotifywm/raw/master/spotifywm.cpp
$ g++ -O3 -shared -fPIC -static-libgcc -lX11 -Wall -Wextra -DSONAME="spotifywm.so" -o spotifywm.so spotifywm.cpp
```
Packaging this just adds burden to maintain in my opinion.

Re: Package request: spotifywm

[pyramidhead52]

[-- Attachment #1: Type: text/plain, Size: 365 bytes --]

New comment by pyramidhead52 on void-packages repository

https://github.com/void-linux/void-packages/issues/29479#issuecomment-800915235

Comment:
I got this error:

```
spotifywm.cpp:9:10: fatal error: X11/Xlib.h: No such file or directory
    9 | #include <X11/Xlib.h>
      |          ^~~~~~~~~~~~
compilation terminated.
```
"base-devel" is installed.

Re: Package request: spotifywm

[FollieHiyuki]

[-- Attachment #1: Type: text/plain, Size: 181 bytes --]

New comment by FollieHiyuki on void-packages repository

https://github.com/void-linux/void-packages/issues/29479#issuecomment-801039955

Comment:
You need `libX11-devel` installed

Re: Package request: spotifywm

[pyramidhead52]

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

New comment by pyramidhead52 on void-packages repository

https://github.com/void-linux/void-packages/issues/29479#issuecomment-801059927

Comment:
Thank you, it worked.

Sorry, I am bit noob about this. Just to be clear, I changed my Spotify keybinding command from `spotify` to `LD_PRELOAD=$HOME/Downloads/spotifywm/spotifywm.so spotify`.

That is the correct way, right?

Re: Package request: spotifywm

[FollieHiyuki]

[-- Attachment #1: Type: text/plain, Size: 247 bytes --]

New comment by FollieHiyuki on void-packages repository

https://github.com/void-linux/void-packages/issues/29479#issuecomment-801068436

Comment:
I guess it is.
You can check whether `spotify` is launched with a proper WM_CLASS by using `xprop`

Re: Package request: spotifywm

[pyramidhead52]

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

New comment by pyramidhead52 on void-packages repository

https://github.com/void-linux/void-packages/issues/29479#issuecomment-801078795

Comment:
Thank you, it works just fine.

Re: [ISSUE] [CLOSED] Package request: spotifywm

[pyramidhead52]

[-- Attachment #1: Type: text/plain, Size: 525 bytes --]

Closed issue by pyramidhead52 on void-packages repository

https://github.com/void-linux/void-packages/issues/29479

Description:
[spotifywm](https://github.com/dasJ/spotifywm): Set Spotify's WM_NAME before opening the window.

Spotify does not respect window manager rules. Any window manager that try to apply specific rules like starting it on a determined workspace or maximizing it on startup, has no effect, as Spotify doesn't set the WM_CLASS property before creating the window.

This one should fix the problem.

Re: Package request: spotifywm

[pyramidhead52]

[-- Attachment #1: Type: text/plain, Size: 323 bytes --]

New comment by pyramidhead52 on void-packages repository

https://github.com/void-linux/void-packages/issues/29479#issuecomment-808752663

Comment:
I've asked if this patch could be incorporated to Spotify package directly and one of the Spotify's maintainers, @ericonr suggested to reopen the issue. So, I'm reopening it.