This may be because of per-process event handling.
<img width="292" height="284" alt="Image" src="https://github.com/user-attachments/assets/10652588-a2e5-4712-866e-8287102d4a61" />
This may be because of per-process event handling.
it does come from per-process event handling. i remember this happening with the couple of apps that can achieve this situation after i've implemented it.
it does come from per-process event handling. i remember this happening with the couple of apps that can achieve this situation after i've implemented it.
Chances are you may be able to make the shell wait for a bit after an app stops running or just block event processing entirely when an app is running if it doesn't already
Chances are you may be able to make the shell wait for a bit after an app stops running or just block event processing entirely when an app is running if it doesn't already
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
it does come from per-process event handling. i remember this happening with the couple of apps that can achieve this situation after i've implemented it.
Chances are you may be able to make the shell wait for a bit after an app stops running or just block event processing entirely when an app is running if it doesn't already
Or just pull all events when returning to shell and then start listening for them again