AppImageLauncher
AppImageLauncher copied to clipboard
Ignore directory
Is your feature request related to a problem? Please describe. AppImage distributed via Lutris or Itch.io display the integration dialog every time they are run
Describe the solution you'd like
A directory could be set to be ignored, essentially the same as running export APPIMAGELAUNCHER_DISABLE=true
Describe alternatives you've considered There is no solution other than uninstalling appimagelauncher or clicking 'run once' every time
this would be great, i've been having issues with steamtinkerlaunch, which uses an appimage of yad, and doesn't properly exit after installing appimagelauncher. being able to block a specific directory from using appimagelauncher or more would be really helpful.
steamtinkerlaunch optionally offers to use a 3rd party yad appimage for people who use a distro without yad and can't compile it themselves. Instead of flaming here you could have opened an issue on the project page, @mindcombatant
i guess i should clarify, it was not my intention to flame here, sorry if it came off that way. however, as this issue only started after installing appimagelauncher, i believe it to be an issue with this project, not steamtinkerlaunch or yad, as they worked perfectiy fine before installing appimagelauncher.
Thanks for the reply, @mindcombatant. I might have been a bit thin-skinned, so sorry for the noise.
Anyway, a bug-report would have been nice, as support for the external appimage
might have to be dropped now.
I personally don't use it and have no idea if others do. Sorry for off-topic
here, @jpenguin and devs, this is my last post here.
I use Joplin, installing it with its installer (which download an appimage to ~/.joplin). It would be nice to select some folders to be ignored when running a file from them.
PureRef is also being incorrectly identified as an AppImage. It has the executable in the /usr/bin/PureRef
. Ignore list would indeed help.
Encountered same for Joplin so created a workaround using the suggest env var in the desktop file ~/.local/share/applications/appimagekit-joplin.desktop
:
- Exec=/home/user/.joplin/Joplin.AppImage %u
+ Exec=env APPIMAGELAUNCHER_DISABLE=true /home/user/.joplin/Joplin.AppImage %u
The changes will be overwritten on next install script update however if we set the file to immutable it will bork the install script, though installation is completed.
Encountered same for Joplin so created a workaround using the suggest env var in the desktop file
~/.local/share/applications/appimagekit-joplin.desktop
:- Exec=/home/user/.joplin/Joplin.AppImage %u + Exec=env APPIMAGELAUNCHER_DISABLE=true /home/user/.joplin/Joplin.AppImage %u
The changes will be overwritten on next install script update however if we set the file to immutable it will bork the install script, though installation is completed.
Thanks @cas-- this workaround works well for me
While this workaround seems good, I would still like for this to be an officially-supported feature, as well.