-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
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
Allow more control over cleaner #626
Comments
@build2stone To be honest, I don't use image previewing myself and I'm not aware if there is a way to do this currently or not. Maybe we could export |
Exporting $f sounds great |
I have reverted |
@build2stone @lucas-mior I have now pushed a commit to export files (i.e. if [ "$1" != "$f" ]; then
case "$(file -Lb --mime-type -- "$f")" in
image/*) exit;;
esac
fi The first check |
Thanks for the fix! |
I'd find it useful if the cleaner script was not run when the next file requires a preview (ie has no preview cached).
This would allow selectively running it from within the preview script.
Example: A directory full of images, previewed using the ueberzug scripts from the wiki
Right now, the cleaner script is always run, causing the previews to flicker when switching from image to image.
My suggestion would enable skipping the cleaner when the next file is also an image.
(In this case ueberzug smoothly replaces the preview)
draw_img.sh
could look like this:Of course, this will sometimes uselessly clear images, but that shouldn't be much of a problem.
Alternatively, is there some way to tell whether a file will trigger the preview script?
Maybe a variable with a list of files with cached previews?
The text was updated successfully, but these errors were encountered: