-
Notifications
You must be signed in to change notification settings - Fork 3k
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
macOS badge dock icon #4472
Comments
I'm not sure what you mean by "badge"? |
A small red circle with number of unseen events - something like this: https://imgur.com/a/tIDZejA. |
Btw. I suppose it needs from alacritty to be integrated with this whole 'notification system' included in modern macOS versions - for different apps it's possible to set what notifications to see in System Preferences -> Notifications. |
I personally don't see much of a point in doing this, since there's no way for Alacritty to really understand if a bell is a new request for action or just an extension to an existing request. Realistically more than binary urgency determination doesn't make much sense from a terminal perspective. But to outright deny it I'd have to look into how this works on macOS. |
I use bells as form of notification - for example after running the command which is supposed to take a long time, I can add So for me it's a killer feature and a blocker for switching from iTerm - but I understand there are not much people like me around ;-) So, fingers crossed it's possible to add in a easy way. |
The icon should bounce after '\a' on macOS if bell is enabled. I don't see how a static notification is any different from jumping doc icon. |
It does bounce - but it's not enough for me. I often have other full screen apps opened on other desktops/workspaces, so when I get back to desktop/workspace where my terminal is it's nice to know that something happened and needs my attention. Actually I haven't noticed this bouncing (mostly because I was working in other full screen window, as described, almost the whole day today), so thanks for this hint. If @chrisduerr decides this issue is a WontFix, I can live with bouncing, I suppose. Let me ask bonus question here (to avoid opening new issue with just this silly one): is it possible to keep the app open (macOS style 'open', so to have process still running) after closing last window, or it closes the process right after shell inside is closed? I have 'muscle memory' after years on iTerm, so after closing the last window I'm pressing cmd+q anyway, so if Alacritty process won't be there, I will be accidentally closing other apps by this ;-) |
No. Not yet at least. See #607. |
I'd rather disable dock bouncing on bel but didn't find any option for this in config. |
Is it possible to badge macOS dock icon as a reaction for 'bell'?
(Im using Big Sur 11.0.1 and stable alacrity 0.5.0, if it matters).
The text was updated successfully, but these errors were encountered: