-
Notifications
You must be signed in to change notification settings - Fork 17
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
[FEAT] [Scratchpads] Improved error handling and recovery #125
Comments
Can you provide a relatively simple setup which is a "worst case" in terms of scratchpad management when the window is closed ? (this is typically supported and isn't failing... so that must be with a specific config/unsupported app). |
@kuba-gaj |
I think it's mostly electron and pwa apps. But sometimes it feels random. I can replicate it easily with slack app:
It is tracked by
|
I am not sure I want to add complexity for the PWA apps, I think it's already a bit borderline... |
Is your feature request related to a problem? Please describe.
Sometimes when a scratchpad app crashes or I close it by mistake it causes pyprland to stop working, not only for that app but also for other scratchpads.
Describe the solution you'd like
It would be great if it could handle errors like that more gracefully and provide options to recover. Maybe a
notify-send
system notification with some actions likestop tracking
relaunch
(that would run exec again and update process_id)The text was updated successfully, but these errors were encountered: