Open probonopd opened 6 years ago
@probonopd how can we efficiently extract that bit of information to make it available to AppImageUpdate? I guess one has to mount the AppImage and extract the .desktop
file. Is there an easier way?
It should be possible to extract the relevant code from appimaged
I guess.
We really need to refactor that code as well, and provide a "libappimage", I guess.
Quite possibly.
I guess I'll extract the code to shared.c
for now, then I just need to consume that file.
Rethinking this, I don't think the approach of opening an AppImage in a terminal is a good idea per se. The problem is that tools which expect arguments etc. will cause the terminal to collapse immediately, without showing any useful error message or something alike to the user.
How about just opening a terminal in the right directory? Maybe (but that's a big maybe) you could already "pre-type" the command, so a user just has to hit "enter". But we need a shell around the application which will stay open in the background.
Also, the button will have to be renamed to "Launch terminal" etc.
Opening a terminal that already has $PATH
set, and printing a clear message in the opened terminal would probably be the best way to go, but for the short run it would be sufficient for me if the button appeared only for GUI apps, that is, in all cases in which we do not positively find Terminal=true
in the desktop file (which can be either Terminal=false
or no Terminal=
or no desktop file at all, and possibly other situations).
The problem with all these approaches begins with the fact that there is no cross-platform way of opening a terminal. I guess that's again something to add to libDE.
Another argument then for
it would be sufficient for me if the button appeared only for GUI apps
When you update a CLI app (desktop file has
Terminal=true
), then "Run app" should open the app in a terminal.Note that this particular AppImage has
True
instead oftrue
: