[X] I checked for similar issues beforehand, but could not find any. I could not add my proposal to any existing issue.
[X] I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.
Feature description
Editing ~/.local/share/applications/*.desktop for launch parameters, on every upgrade, is a real PITA.
Proposed solution
Modify the existing "Move to ~/Applications?" dialog to also ask for Desktop launch parameters.
Manpage documentation explaining AppImageLauncher just sets the parameters in the .Desktop file during that first time integration only. it doesn't manage anything after that. It's up to the user to edit ~/.local/share/applications/*.desktop accordingly.
IOW, we do not want to setup management of the state of an appimage install or any of that. We do not need another dialog for "settings" for each and every parameter settings. We need just enough to setup during the first time install, part of that, "dang it, I should have clicked that Move option." Which can now include a first time, "ok, i know exactly the parameters this appimage needs on every upgrade, let me paste that now."
Alternative solutions you considered
Ansible. I have used Ansible to manage desktop parameters before. Don't do that.
Currently I do it manually. Could write a script to grep the line, and copy it over I guess for the lazy... But, I know my parameters when I am launching! :)
Additional context
I've been using AppImageLauncher since it's 1.0. Thank you!! All other solutions, which somehow sneaks into my distros, never got it right. Thank you!
Pre-submit checks
Feature description
Editing
~/.local/share/applications/*.desktopfor launch parameters, on every upgrade, is a real PITA.Proposed solution
~/.local/share/applications/*.desktopaccordingly.IOW, we do not want to setup management of the state of an appimage install or any of that. We do not need another dialog for "settings" for each and every parameter settings. We need just enough to setup during the first time install, part of that, "dang it, I should have clicked that Move option." Which can now include a first time, "ok, i know exactly the parameters this appimage needs on every upgrade, let me paste that now."
Alternative solutions you considered
Ansible. I have used Ansible to manage desktop parameters before. Don't do that.
Currently I do it manually. Could write a script to grep the line, and copy it over I guess for the lazy... But, I know my parameters when I am launching! :)
Additional context
I've been using AppImageLauncher since it's 1.0. Thank you!! All other solutions, which somehow sneaks into my distros, never got it right. Thank you!