Open Lew-Rockwell-Fan opened 2 years ago
@Lew-Rockwell-Fan Thanks for the idea. I'm curious to learn more about your use case - why would you wrap it in a script? Are there other viewers better suited for this purpose, possibly feh
as an example?
"why would you wrap it in a script?" In my case, to facilitate a custom context menu that needs a way to know the /path/filename of the image shown. But really, there are all sorts of potential reasons. Maybe, for example, somebody would want to change the screen brightness or pause video players or change what an OSD is showing while viewing images, and reverse the changes on exit. Or invoke it with different options without having to type them in.
"other viewers better suited for this purpose, possibly feh" Overall, no. Feh is great & my second choice. If it weren't for one limitation, I'd prefer it to Viewnior, but it won't show a gif. There are things to be said in favor of many viewers - honorable mention to Nomacs - but they all have limitations. Most are resource hogs. Viewnior's only flaw is that there is no direct way to control the context menu & no simple way to get around that by informing either a wrapper or an independent external program (either of which can provide an alternate menu) of the /path/filename of the image shown (or not shown in the case of defective files).
It would real handy if Viewnior would echo the full /path/filename to stdout every time it loads, or, in the case of corrupt images, tries to load, an image. People who don't wrap Viewnior in a script wouldn't even see the difference but it sure would help those of us who want to tinker with it. Something like: loaded: /path/to/image.jpg corrupt: /path/to/bad-image.png