How to avoid subsequent AppImage package mounting?

[Szyk Cech]

Hi
I have text editor in AppImage. It works fine. But open new file is
slow. It is due to new mount entire AppImage when I want open new file
from file manager. It is due to used scheme: first app on the desktop
opens local socket and listen on it for files to open. When I want open
new file from file manager I start my editor and write to local socket
file name and close app immediately - this involve mount AppImage.
I think it is pointles mount the AppImage every time I start my editor
as it is mounted read only (right?).

So:
How to avoid/prevent from mounting my editor AppImage every time I open
new file?

thanks and best regards
Szyk Cech

[Mike Wells]

Hello! As far as I'm aware, there's really no easy way to prevent this.
AppImage at its core works on mounting an image at application start,
and unmounting it when the program exits. I might be wrong, though!

Having said that, it might certainly be possible to unpackage the
AppImage and extract the binaries, and create a native package that
works with your distro, or you could just run the binaries manually.
What text editor is it? There might even be a package available somewhere.

Hope that helps! :)

Post by Szyk Cech
Hi
I have text editor in AppImage. It works fine. But open new file is
slow. It is due to new mount entire AppImage when I want open new file
from file manager. It is due to used scheme: first app on the desktop
opens local socket and listen on it for files to open. When I want open
new file from file manager I start my editor and write to local socket
file name and close app immediately - this involve mount AppImage.
I think it is pointles mount the AppImage every time I start my editor
as it is mounted read only (right?).
How to avoid/prevent from mounting my editor AppImage every time I open
new file?
thanks and best regards
Szyk Cech