as mentioned in #253, version numbers can be confusing if you don't know
or realize you're running SwayFX instead of standard sway.
to fix this issue, I've updated the way we display versions, replacing
"sway version X" to "swayfx version X", suffixed by the sway upstream
version which swayfx is based upon.
while not immediately displaying we come from swayfx in
swaymsg/swaynag/swaybar, we do display we're based off a specific
upstream sway version.
note: this requires updating meson.build (currently meson.build:181)
each time we rebase into a new sway version.
as mentioned in #253, version numbers can be confusing if you don't know or realize you're running SwayFX instead of standard sway.
to fix this issue, I've updated the way we display versions, replacing "sway version X" to "swayfx version X", suffixed by the sway upstream version which swayfx is based upon.
while not immediately displaying we come from swayfx in swaymsg/swaynag/swaybar, we do display we're based off a specific upstream sway version.
note: this requires updating
meson.build(currentlymeson.build:181) each time we rebase into a new sway version.Closes: Issue #253