On Sat, Jan 10, 2015 at 07:25:54PM +0100, lee wrote > Andrew Savchenko <[email protected]> writes: > > > 1) Configure your handlers in seamonkey. > > How?
I've got Seamonkey 2.31. Go to Edit ==> Preferences ==> Category;Browser ==> Helper Aplications Assuming you've already got "Content Type" "PDF file" in the list, click on the icon beside "emacsclient" in the "Action" column. This opens a dropdown menu. Click on "Use other..." and navigate to /usr/bin/mupdf in the file menu. If you're really brave, you can try editing the mimeTypes.rdf file in the browser profile directly. Remember to shut down your browser, and back up the file first. I originally got into this because of a particularly obnoxious behaviour by Firefox. Seamonkey shares most Firefox code, so I assume it follows suit. The obnoxious behaviour is that it dereferences symlinks. Years ago Abiword would actually install a binary like /usr/bin/abiword-1.2.3.4 and /usr/bin/abiword was a symlink to this file. Let's say you selected abiword as the helper application to launch when you get Word files as URLs. Firefox would dereference the symlink to /usr/bin/abiword-1.2.3.4, and store that app name as the app to launch for Word files. A version bump to /usr/bin/abiword-1.2.3.5 and Firefox would whine about /usr/bin/abiword-1.2.3.4 not being found. I edited mimeTypes.rdf, changing all "abiword-1.2.3.4" to "abiword", and things worked properly. This was even more crucial for apps like "sox" which have symlinks with different names like "play" that take different parameters and act differently depending on the name you invoke them by. -- Walter Dnes <[email protected]> I don't run "desktop environments"; I run useful applications
