While in certain situations it might be uncomfortable, but I use Chrome
and didn't really encounter any problems.
But I agree that it would be easier to integrate the default browser as
a variable, that could be called on by applications, instead of calling
on a specific one.
However, I suspect it's a more complex problem than that. There are a
number of applications that can or should be treated this way (e-mail
clients, for example), therefore I believe it's more of an upstream
decision, and with the number of desktop environments I don't know how
realistically we can expect implementation.
Cheers,
Din
On 05/07/2010 05:20 AM, T o n g wrote:
Hi,
Having upgraded iceweasel, I am no longer able to call firefox or mozilla
from command line any more. I don't mind firefox is called iceweasel or
whatever in Debian, but entirely stopping me from starting firefox is
something I don't feel comfortable.
Please comment.
PS:
$ apt-cache policy iceweasel
iceweasel:
Installed: 3.5.9-2
Candidate: 3.5.9-2
Version table:
3.5.9-3 0
50 http://debian.mirror.rafal.ca unstable/main Packages
*** 3.5.9-2 0
300 http://debian.mirror.rafal.ca testing/main Packages
100 /var/lib/dpkg/status
$ update-alternatives --display firefox
update-alternatives: error: no alternatives for firefox.
$ update-alternatives --display mozilla
update-alternatives: error: no alternatives for mozilla.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4be39ca2.9050...@gmail.com
