timeout options passed on cmdline in sway config not respected
- Dominant language
- C
- Stars
- 3.3k
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
Hello `mako` devs and users,
Thanks a lot for maintaining this project. It is quite nice.
On to the point of this issue: I've encountered a bit of a mind boggling problem while using the `--default-timeout` and/or `--ignore-timeout` options while executing `mako` within sway's configuration:
`exec --no-startup-id mako --default-timeout=1000 --ignore-timeout=1`
Doing this inside of sway's config does not seem to respect the values I provide. However, if I configure it to do so in `~/.config/mako/config`, everything works as expected.
If I execute `mako` within a shell after starting sway, the options do take effect.
To clarify: The notifications just stay up there forever, as would be done without the options being configured.
Just leaving this here in case it helps. I'm really not sure why using the exact same shell options within sway's config would no-op those options.
Contributor guide
Assessment
This issue has not been assessed yet.