View Single Post
Old 06-30-2017, 11:16 AM   #6
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by loviedovie View Post
When I try to choose a bash script for open with for pdfs this is what I get.

I am also hoping that this would be fixed for the last 2x version because I personally cant use v3 due to not running in remote session, also there might be others who are still using the 2x versions.
One possible alternative would be to try running in development mode. It would be fairly simple to revert only the commits which affected calibre's binary plugins, while taking advantage of most of the changes in calibre v3 -- or simply cherry-picking this commit on its own.

That might be more convenient than switching between the 3.x and 2.x versions whenever you need to circumvent this bug.
eschwartz is offline   Reply With Quote