Before opening a feature request
What is the user problem or growth opportunity you want to see solved?
In order to properly integrate with systemd-run or wrappers, some values from Desktop Entry need to be available in execution context.
How do you know that this problem exists today? Why is this important?
Currently there is only {cmd} pattern available to customize -run-command, no way to get anything from or about the Entry.
Who will benefit from it?
People running systemd-managed graphical sessions.
Rofi version (rofi -v)
Version: 2.0.0
Configuration
Additional information
There is a corresponding PR for fuzzel where solution is settled on providing agnostic environment variables, aiming to become interoperable convention:
- DESKTOP_ENTRY_ID
- DESKTOP_ENTRY_PATH
- DESKTOP_ENTRY_NAME
- DESKTOP_ENTRY_GENERICNAME
- DESKTOP_ENTRY_COMMENT
- DESKTOP_ENTRY_NAME_L (Localized)
- DESKTOP_ENTRY_GENERICNAME_L (Localized)
- DESKTOP_ENTRY_COMMENT_L (Localized)
- DESKTOP_ENTRY_ICON
And if launching an action, also:
- DESKTOP_ENTRY_ACTION (Action identifier)
- DESKTOP_ENTRY_ACTION_NAME
- DESKTOP_ENTRY_ACTION_NAME_L (Localized)
- DESKTOP_ENTRY_ACTION_ICON
Before opening a feature request
What is the user problem or growth opportunity you want to see solved?
In order to properly integrate with systemd-run or wrappers, some values from Desktop Entry need to be available in execution context.
How do you know that this problem exists today? Why is this important?
Currently there is only
{cmd}pattern available to customize-run-command, no way to get anything from or about the Entry.Who will benefit from it?
People running systemd-managed graphical sessions.
Rofi version (rofi -v)
Version: 2.0.0
Configuration
Additional information
There is a corresponding PR for fuzzel where solution is settled on providing agnostic environment variables, aiming to become interoperable convention:
And if launching an action, also: