You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now if I want to make a launcher script (which is pretty useful in window managers in general) I click the Add Desktop Entry menu option & then go to ~/.local/share/applications grab the desktop file created there & copy the run command. Alternatively I could manually figure what the name I gave to the bottle is & what the lunched exe is called precisely & formulate the command myself that would kind of like this flatpak run --command=bottles-cli com.usebottles.bottles run -p gameexe -b 'bottlename' -- %u but this is tedious either way.
Describe the solution you'd like
Please consider adding a menu option under Add Desktop Entry to copy the launch command to the clipboard!
Other solutions?
if the clipboard is not good for some reason I would be more than okay with a directly generated .sh run script option as well.
Additional context and references
No response
The text was updated successfully, but these errors were encountered:
Tell us the problem or your need
Right now if I want to make a launcher script (which is pretty useful in window managers in general) I click the
Add Desktop Entry
menu option & then go to~/.local/share/applications
grab the desktop file created there & copy the run command. Alternatively I could manually figure what the name I gave to the bottle is & what the lunched exe is called precisely & formulate the command myself that would kind of like thisflatpak run --command=bottles-cli com.usebottles.bottles run -p gameexe -b 'bottlename' -- %u
but this is tedious either way.Describe the solution you'd like
Please consider adding a menu option under Add Desktop Entry to copy the launch command to the clipboard!
Other solutions?
if the clipboard is not good for some reason I would be more than okay with a directly generated .sh run script option as well.
Additional context and references
No response
The text was updated successfully, but these errors were encountered: