-
Notifications
You must be signed in to change notification settings - Fork 46
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
[BUG] -window-command ignored #114
Comments
Two main blockers for the functionality:
|
@alebastr Thanks for the fast reply. Is there any way to execute a custom script for a window at the moment? Maybe the unique node id ( |
Unfortunately, that info is not available to the module. The implementation does not use Sway specific IPC. Window title and app_id is all we have, although I'm hesitant to allow using these for scripting and introduce even more divergence with XCB |
Returning the PID might be a viable option (maybe along with a new "pattern", like I came across this for Hyprland, which supports acting on windows by PID; not sure if Sway and others do the same. |
Rofi version (rofi -v or git commit in case of build issue)
Version: 1.7.5+wayland2
Configuration
https://gist.github.com/ckudera/3296974509961570aa7d13ab58688ec7
Theme
https://gist.github.com/ckudera/e5e528840451a8e7d015ab1db4b66d3b
Timing report
No response
Launch command
rofi -show window -kb-accept-alt x -window-command "notify-send {window}"
Step to reproduce
Execute the Launch Command and press x on any window entry. No special config or theme file are necessary.
Expected behavior
On any window entry, x should lead to a notification (
notify-send {window}
should be executed).Actual behavior
The
-window-command
is ignored and the selected window gets focused (default behaviour as it would be when the Return key is pressed).Additional information
With
rofi -show window -kb-accept-alt x -window-command "notify-send {window}" --help
I get the following output:Therefore, both commandline options are set as they should be.
Using wayland display server protocol
I've checked if the issue exists in the latest stable release
The text was updated successfully, but these errors were encountered: