We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Any
The extension Unload event is sent to extensions when Ulauncher is closed, but not when you manually close them.
It is located in Client.py which is called when the socket closes. It should be triggered in the stop method instead.
Ulauncher/ulauncher/api/client/Client.py
Line 61 in a41e515
Ulauncher/ulauncher/modes/extensions/ExtensionRuntime.py
Lines 58 to 70 in a41e515
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Environment
Any
Bug description
The extension Unload event is sent to extensions when Ulauncher is closed, but not when you manually close them.
It is located in Client.py which is called when the socket closes. It should be triggered in the stop method instead.
Ulauncher/ulauncher/api/client/Client.py
Line 61 in a41e515
Ulauncher/ulauncher/modes/extensions/ExtensionRuntime.py
Lines 58 to 70 in a41e515
Log output
No response
Communication guidelines
Ulauncher v6
The text was updated successfully, but these errors were encountered: