In fvwm2, FvwmCommandS was required to set up a comms socket between itself and fvwm2 so that FvwmCommand could send messages to fvwm2.
Under fvwm3, this changed to become a thin wrapper around talking to FvwmMFL which provides similar functionality to FvwmCommandS, and as such, in order to maintain some backwards compatibility with fvwm2, providing such a symlink would mean that the same fvwm config would work under the two versions without requiring modification.
In
fvwm2
,FvwmCommandS
was required to set up a comms socket between itself andfvwm2
so thatFvwmCommand
could send messages tofvwm2
.Under
fvwm3
, this changed to become a thin wrapper around talking toFvwmMFL
which provides similar functionality toFvwmCommandS
, and as such, in order to maintain some backwards compatibility withfvwm2
, providing such a symlink would mean that the same fvwm config would work under the two versions without requiring modification.This was suggested by @danespen (via https://fvwmforums.org/t/fvwmcommand-docs/3052)