TheAssassin
TheAssassin
What does that have to do with any mac? You don't seem to understand the technical _need_ for a collision avoidance system.
Users won't _need_ to see any of those files anyway, only in exceptional cases...
... but not the core principal of AppImageLauncher.
That's a totally different use case... comparing apples and bags of wheat...
AppImageLauncher != AppImage. You don't like the UX? You don't need to use it, it's purely optional.
@zilti if the vagrant AppImage doesn't "just run" but triggers AppImageLauncher, then it's an issue in the AppImage, actually. Any CLI AppImage (i.e., `Terminal=true` in the desktop file) is ignored...
If you post a link, I'll support you with it!
It's enough to provide some "slightly hidden" message box containing the information. As long as it's available from the UI, it's all fine.
libappimageinfo, your new project, might come in handy for the purpose, once it's ready. I guess we should wait for you to finish the library.
Thanks for this very detailed bug report. This is the first one using the new issue form. Looks like that really helps guide people when creating issues! Your log output...