-
Notifications
You must be signed in to change notification settings - Fork 19
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
Questions about uwsm app
#53
Comments
Command line or Desktop Entry: the main difference is resulting unit's metadata. If Desktop Entry is given, its Name and Comment are used, plus arguments are parsed according to the spec if the entry has fields for them. Is using path to entries a NixOS thing? ID is usually enough. |
No, it's just that anyrun already has the path, but not the ID (basename).
If this is the case, then I'll make another uwsm-specific application plugin rather than try to modify the current one. |
Ah, ok, in this case the path is preferable, no need to search the entry if file is already known. |
Thanks for the clarifications! |
I've been in the process of integrating uwsm into my desktop experience since the discussion in Hyprland. So far I've done the first part, aka starting Hyprland via uwsm. The second part would entail launching apps through
uwsm app
.I currently use anyrun as my runner. It does not have a
--launch-prefix
option like fuzzel does, but I've been integrating it myself. I've hit a roadblock in deciding whether to pass Exec or the Desktop Entry path touwsm app --
(or thelaunch_prefix
, to be precise). Is there any benefit to using one over the other?The next question would be how to handle starting terminal applications from anyrun:
sh -c ${terminal} -e ${launch_prefix} ${entry.exec}
(or${entry.path}
, if that's more appropriate)sh -c ${launch_prefix} ${terminal} -e ${entry.exec}
The text was updated successfully, but these errors were encountered: