You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
install a plugin and verify it shows correctly in xbar
install a second plugin that cannot be executed. For example, clipboard_bar doesn't work on my Sonoma system as it requires PHP.
Actual behaviour
xbar then shows no icons at all (not even for the first plugin which previously worked), but the process remains running.
To recover, I had to fix (or remove) the offending plugin and kill and restart xbar.
Expected
If one plugin cannot be executed, other plugins should still work. I would suggest that for the best UX, the erroring plugin should also show up as an error icon with the error available in the menu.
Details
When running xbar from the terminal in the broken state, the log includes:
2024/01/05 11:01:31 clipboard_bar.1d.php: ERR: exit status 127: env: php: No such file or directory
clipboard_bar.1d.php:
2024/01/05 11:01:34 internet-status.2s.sh: refreshing: internet-status.2s.sh
2024/01/05 11:01:36 internet-status.2s.sh: refreshing: internet-status.2s.sh
2024/01/05 11:01:36 clipboard_bar.1d.php: cycling: 001-clipboard_bar.1d.php
2024/01/05 11:01:38 internet-status.2s.sh: refreshing: internet-status.2s.sh
System: macOS Sonoma
Version: 2.1.7-beta
The text was updated successfully, but these errors were encountered:
Repro
Actual behaviour
xbar then shows no icons at all (not even for the first plugin which previously worked), but the process remains running.
To recover, I had to fix (or remove) the offending plugin and kill and restart xbar.
Expected
If one plugin cannot be executed, other plugins should still work. I would suggest that for the best UX, the erroring plugin should also show up as an error icon with the error available in the menu.
Details
When running xbar from the terminal in the broken state, the log includes:
System: macOS Sonoma
Version: 2.1.7-beta
The text was updated successfully, but these errors were encountered: