As always, thanks for w3m; I use it all the time.
Here are a few suggestions for improving w3m's mailcap-related behavior:
When a program listed in the mailcap is invoked, stdin, stdout, and
stderr still refer to the tty. This can mislead the program into trying
to use the tty. But w3m is also still using the tty, so they will fight
each other. The easiest solution is for w3m to close file descriptors
0, 1, and 2 just before calling exec().
When the first resource displayed (the one named on the w3m command
line) requires the use of mailcap, w3m invokes the program, then says
"Press any key to quit w3m", waits for the user to press Return, then
kills the other process and exits. I don't understand why w3m kills
the other process. If it didn't, then it wouldn't need to wait for the
user to press a key; it could invoke the program and immediately exit.
Notice that when w3m is displaying an HTML page, and a link is followed
that invokes another program, w3m can then be quit and the other process
is not killed.
~/.mailcap and /etc/mailcap are hard-coded in w3m. It would be nice
for this search path to be configurable. For example, I tell netscape
to ignore /etc/mailcap because it contains a lot of junk that I don't
trust.
AMC
This archive was generated by hypermail 2b29 : Fri Aug 25 2000 - 16:31:50 CDT