fix(hyprland): fix Slack and Telegram keybindings - #1293
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
You do not have enough credits to review this pull request. Please purchase more credits to continue. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughModified Hyprland keybindings in the configuration file: changed the Telegram launcher from ALT+SHIFT+T to $mod+SHIFT+T with updated executable label, and simplified the Slack keybinding from conditional focus-or-launch logic to a direct exec command. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Mesa DescriptionTL;DRFixed Hyprland keybindings for Slack and Telegram to ensure correct application launching behavior. What changed?
Description generated by Mesa. Update settings |
There was a problem hiding this comment.
Code Review
This pull request updates the application launch hotkeys in the Hyprland configuration, specifically changing the Telegram binding and simplifying the Slack binding by removing the window focus check. Feedback suggests using gtk-launch for both Telegram and Slack to ensure consistency with other bindings and improve robustness by utilizing desktop files.
| # ============================================================================= | ||
| bind = $mod, T, exec, ghostty | ||
| bind = ALT SHIFT, T, exec, telegram-desktop | ||
| bind = $mod SHIFT, T, exec, Telegram |
There was a problem hiding this comment.
For consistency with how other applications like 1Password (line 233) and Signal (line 234) are launched, consider using gtk-launch. This is generally more robust as it uses the application's .desktop file instead of relying on an executable in the PATH.
The binary name Telegram is also unusual; the executable is typically telegram-desktop. Using gtk-launch with the correct desktop file name (e.g., telegramdesktop) would resolve this ambiguity.
bind = $mod SHIFT, T, exec, gtk-launch telegramdesktop
| bind = $mod SHIFT, T, exec, Telegram | ||
| bind = $mod, G, exec, hyprctl clients -j | grep -q '"class": "google-chrome"' && hyprctl dispatch focuswindow class:google-chrome || google-chrome-stable | ||
| bind = $mod, S, exec, hyprctl clients -j | grep -q '"class": "Slack"' && hyprctl dispatch focuswindow class:Slack || slack | ||
| bind = $mod, S, exec, slack |
There was a problem hiding this comment.
Pull request overview
Updates Hyprland application launch keybindings to adjust how Slack and Telegram are launched from the window manager config.
Changes:
- Change Telegram binding to use
$mod SHIFT+Tand update the executed command. - Simplify Slack binding to always execute Slack rather than focus-or-launch.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # ============================================================================= | ||
| bind = $mod, T, exec, ghostty | ||
| bind = ALT SHIFT, T, exec, telegram-desktop | ||
| bind = $mod SHIFT, T, exec, Telegram |
There was a problem hiding this comment.
Telegram is likely not the executable provided by this repo’s installed package set. home-manager/packages/default.nix includes telegram-desktop, and this file previously used telegram-desktop; switching to Telegram may make the keybinding a no-op on fresh setups. Consider using the actual installed binary (telegram-desktop) or a stable desktop entry via gtk-launch if that’s the intended target.
| bind = $mod SHIFT, T, exec, Telegram | |
| bind = $mod SHIFT, T, exec, telegram-desktop |
| bind = $mod SHIFT, T, exec, Telegram | ||
| bind = $mod, G, exec, hyprctl clients -j | grep -q '"class": "google-chrome"' && hyprctl dispatch focuswindow class:google-chrome || google-chrome-stable | ||
| bind = $mod, S, exec, hyprctl clients -j | grep -q '"class": "Slack"' && hyprctl dispatch focuswindow class:Slack || slack | ||
| bind = $mod, S, exec, slack |
There was a problem hiding this comment.
PR description says Super+S should “always open a new Slack window”, but this binding now just runs slack without any flag/command to force a new window. If Slack reuses the existing instance (common for Electron apps), this won’t meet the stated behavior; consider invoking Slack with an explicit new-window option or an alternative command that guarantees a new window.
| bind = $mod SHIFT, T, exec, Telegram | ||
| bind = $mod, G, exec, hyprctl clients -j | grep -q '"class": "google-chrome"' && hyprctl dispatch focuswindow class:google-chrome || google-chrome-stable | ||
| bind = $mod, S, exec, hyprctl clients -j | grep -q '"class": "Slack"' && hyprctl dispatch focuswindow class:Slack || slack | ||
| bind = $mod, S, exec, slack |
There was a problem hiding this comment.
This change makes Super+S no longer a focus-or-launch binding, but earlier in this file there’s a comment explicitly recommending “Super+G/S/D focus-or-launch bindings” (around lines 183–185). Update that comment to reflect the new intended behavior for Super+S to avoid future confusion.
Summary
telegram-desktoptoTelegramTest plan
🤖 Generated with Claude Code
Summary by cubic
Fix Hyprland keybindings so Slack and Telegram launch reliably.
slackdirectly, always opening a new window.$mod(not ALT) and callsTelegram(correct binary).Written for commit 563bb9a. Summary will update on new commits.