README: add a mention about '$PATH' issues (#11)

This commit is contained in:
Skia 2023-03-02 12:49:01 +01:00
parent faf309ce81
commit 2541b0aa2c

View file

@ -19,6 +19,13 @@ Otherwise, you may grab a [pre-built
binary](https://gitlab.com/hyask/swaysome/-/jobs/artifacts/master/raw/target/release/swaysome?job=build:cargo) from the binary](https://gitlab.com/hyask/swaysome/-/jobs/artifacts/master/raw/target/release/swaysome?job=build:cargo) from the
CI and put it in your `$PATH`. CI and put it in your `$PATH`.
**WARNING**: please double-check that your `swaysome` binary is in `sway`'s `$PATH`. Depending on your setup, the
`$PATH` you have in your shell may not be the same as `sway`'s, and if `swaysome` can't be called by `sway`, the
symptoms will only look like non-functional shortcuts.
If you're in this situation, a quick workaround is to call `swaysome` with its full absolute path from `sway`'s config
to check that everything works before fixing your `$PATH` issue.
## Usage ## Usage
Then create the file (and the directory if needed) `~/.config/sway/config.d/swaysome.conf` and paste this inside: Then create the file (and the directory if needed) `~/.config/sway/config.d/swaysome.conf` and paste this inside: