search

fvwmorg / fvwm3

FVWM version 3 -- the successor to fvwm2
Other
488 stars 75 forks source link

FvwmCommand: use FVWMMFL_SOCKET when it's present #1035

Open akovalenko opened 3 weeks ago

akovalenko commented 3 weeks ago

Follow-up to da4387bd FvwmMFL: introduce FVWMML_SOCKET_PATH for namespacing. It breaks FvwmCommand for me because instead of taking FVWMMFL_SOCKET from the environment, FvwmCommand guesses it from FVWMMFL_SOCKET_PATH (incorrectly, DISPLAY=:1.0 while socket being :1.sock)

When running FvwmCommand from a specific fvwm instance, FVWMMFL_SOCKET is available, so let FvwmCommand use it. In the "outer" environment where only FVWMML_SOCKET_PATH is available, let it resort to guessing socket by $DISPLAY. Fixes #1034.

ThomasAdam commented 1 week ago

Damn... I missed that you'd done this, @akovalenko -- sorry.

Is this PR still required?