The Terminal property in a .desktop file specifies, whether an application will start it's own GUI or needs to be run from inside a terminal emulator, so a desktop file with Terminal=true should have its command run inside a terminal emulator, for example alacritty -e $COMMAND. handlr misinterprets this, hiding a command's output if it's set to false and never launching a terminal emulator.
The result of this is that output will be needlessly hidden for most applications, and some applications, such as htop.desktop will fail to correctly launch, as their TUI will be hidden when launched from a UI that doesn't show handlr's output.
EDIT: There seems to be no clear specification on what terminal emulator to use. GNOME's stack just tries some known ones. Maybe handlr can find a more elegant solution.
The
Terminalproperty in a.desktopfile specifies, whether an application will start it's own GUI or needs to be run from inside a terminal emulator, so a desktop file withTerminal=trueshould have its command run inside a terminal emulator, for examplealacritty -e $COMMAND. handlr misinterprets this, hiding a command's output if it's set tofalseand never launching a terminal emulator.The result of this is that output will be needlessly hidden for most applications, and some applications, such as
htop.desktopwill fail to correctly launch, as their TUI will be hidden when launched from a UI that doesn't show handlr's output.EDIT: There seems to be no clear specification on what terminal emulator to use. GNOME's stack just tries some known ones. Maybe handlr can find a more elegant solution.