-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer prints to stdout #8
Comments
OK I'll revert @pathetic-lynx patch until I understand a little bit more the issue. |
@Biont quick question for you, how do you exit swappy? Do you use the |
Cannot reproduce, output to stdout when killing swappy using sway does not work in either 196f7f4 or 320dae0, killing with @Biont can you investigate more? edit: does not matter whether you use grim to get the screenshot or swappy directly, same behaviour edit2: Ok, we need to make sure that the application takes the same path when killed externally and when exiting from the keyevent with the same precondition. Currently swappy does not save the file when I hit |
So I usually EDIT: And yes, closing the window via my sway keybinding serves as a workaround. Thanks for the hint. |
The bug was introduced by `f3e5d86`. Closes #8
The bug was introduced by `f3e5d86`. Closes #8
The command chain
grim -g "$(slurp)" - | swappy -f - -o -
no longer produces any output for me.I believe this started today, so maybe something in 320dae0 broke it?
Saving pictures regularly seems to be unaffected
The text was updated successfully, but these errors were encountered: