Re: debian sensible browser help
On 2011-07-26 00:43:30 GMT, Robert Holtzman wrote:
> Try putting that line in .bashrc, log out and back in. Don't forget the
> "&&".
On 2011-07-26 02:39:24 GMT, I wrote:
> I just did try that with the "&&", and I still got sensible-browser when I
> used metamail. Maybe that's unexpected, but at least listing iceweasel in
> ~/.mailcap has worked.
I should clarify that I am doing all of this from command lines under a
window manager (fvwm). When I call startx, the first xterm's settings come
from ~/.bash_login. But if I call more xterms from there, any settings in
~/.bashrc override those. This was easily verified by playing with the login
prompt (PS1).
Assume I have no text/html entry in ~/.mailcap and no BROWSER defined in my
settings (as verified by "echo $BROWSER"). If I then call metamail, it calls
sensible-browser, which in turns calls x-www-browser. I don't know where
that is defined; it's not in /etc/mailcap. If I define BROWSER as iceweasel
in ~/.bash_login, and then call metamail from any xterm, then sensible-
browser calls iceweasel. If I only define BROWSER in ~/.bashrc, this doesn't
happen for the first xterm but does from subsequent ones. In any case, there
are six processes:
26091 26012 metamail z
26092 26091 sh -c metamail /tmp/MK962cH
26093 26092 metamail /tmp/MK962cH
26094 26093 sh -c /usr/bin/sensible-browser '/tmp/MNk6vkK'
26095 26094 /bin/sh /usr/bin/sensible-browser /tmp/MNk6vkK
26097 26095 /usr/lib/iceweasel/firefox-bin /tmp/MNk6vkK
The other approach is to have a text/html entry for iceweasel in /etc/mailcap
or ~/.mailcap. I prefer this solution. Sensible-browser isn't called at
all, and there are five processes:
25339 25255 metamail z
25341 25339 sh -c metamail /tmp/Mmml5k6
25342 25341 metamail /tmp/Mmml5k6
25344 25342 sh -c /usr/bin/iceweasel '/tmp/MM6RYsV'
25345 25344 /usr/lib/iceweasel/firefox-bin /tmp/MM6RYsV
Reply to: