We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I store AppImages in a folder /home/lamy/opt/AppImage with separate subfolders for each appimage. For example:
/home/lamy/opt/AppImage
/home/lamy/opt/AppImage $ tree . ├── AppImageUpdate │ ├── appimageupdatetool-x86_64.AppImage │ ├── appimageupdatetool-x86_64.AppImage.zs-old │ └── Latest -> ./appimageupdatetool-x86_64.AppImage ├── ffsend │ ├── ffsend-v0.2.76-linux-x64-static │ └── Latest -> ./ffsend-v0.2.76-linux-x64-static ├── FrappeBooks │ ├── Frappe-Books-0.14.1.AppImage │ └── Latest -> ./Frappe-Books-0.14.1.AppImage └── LosslessCut ├── Latest -> ./LosslessCut-linux-x86_64.AppImage └── LosslessCut-linux-x86_64.AppImage
Is it possible that while init, if I specify the path /home/lamy/opt/AppImage, it can look for appimages recursively (zap list)?
init
The text was updated successfully, but these errors were encountered:
okay, but updating it could be harder, because zap creates some metadata when installing. If its just for listing appimages, it is doable.
zap
Sorry, something went wrong.
No branches or pull requests
I store AppImages in a folder
/home/lamy/opt/AppImage
with separate subfolders for each appimage. For example:Is it possible that while
init
, if I specify the path/home/lamy/opt/AppImage
, it can look for appimages recursively (zap list)?The text was updated successfully, but these errors were encountered: