Bug#186209: tetex-bin: xdvi anything.tex launches web browser on file:anything.tex
[From Atsuhito Kohda, Tue, 01 Apr 2003 17:43:25 +0900 (JST)]
> [...]
> I can't reproduce this bug.
> [...]
You must have an opened mozilla already, it prints the message on stderr but
also opens the browser :
<cappe@udon> ps uxf | grep mozilla
cappe 29762 0.0 0.1 1588 556 pts/0 S 11:22 0:00 | \_ grep
mozilla
<cappe@udon> xdvi anything.tex
Can't open `/tsi/udon/cappe/anything.tex.dvi': No such file or directory
<cappe@udon> ps uxf | grep mozilla
cappe 29781 0.0 0.1 1588 556 pts/0 S 11:22 0:00 | \_ grep
mozilla
cappe 29766 11.7 3.8 34032 19624 pts/0 S 11:22 0:01
/usr/lib/mozilla/mozilla-bin file:anything.tex
cappe 29775 0.0 3.8 34032 19624 pts/0 S 11:22 0:00 \_
/usr/lib/mozilla/mozilla-bin file:anything.tex
cappe 29776 0.0 3.8 34032 19624 pts/0 S 11:22 0:00 \_
/usr/lib/mozilla/mozilla-bin file:anything.tex
cappe 29777 0.0 3.8 34032 19624 pts/0 S 11:22 0:00 \_
/usr/lib/mozilla/mozilla-bin file:anything.tex
cappe 29778 0.0 3.8 34032 19624 pts/0 S 11:22 0:00 \_
/usr/lib/mozilla/mozilla-bin file:anything.tex
cappe 29779 0.3 3.8 34032 19624 pts/0 S 11:22 0:00 \_
/usr/lib/mozilla/mozilla-bin file:anything.tex
<cappe@udon> dpkg -l tetex-bin
ii tetex-bin 1.0.7+20011202-7.1 teTeX binary files
<cappe@udon> dpkg -l mozilla* | grep ^ii
ii mozilla-browse 1.0.1-2 Mozilla Web Browser - core and browser
ii mozilla-psm 1.0.1-2 Mozilla Web Browser - Personal Security Mana
Note that I have since then been contacted by Stefan Ulrich (developper?) who
seemed to be aware of the problem (see my answer
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186209). He wrote:
[Stefan Ulrich, Tue, 25 Mar 2003]
> That's a braindeadness in xdvi's MIME handling that will be fixed
> in the upcoming 22.7x. (I don't think it can be backported to
> 22.4x, since the changes are rather fundamental - e.g. 22.7x
> doesn't use libwww any more).
>
> However I'm still unsure whether to preserve the `send-to-browser'
> default for links to local files (not at startup, you'd need to
> explicitly click on them) for which no valid MIME type (mime.types)
> or application (mailcap) is found. (`Local files' being files with
> no URL scheme, just an ordinary path, or the `file://' URL scheme).
> [...]
Reply to: