Re: debian sensible browser help
On Wed, Jul 27, 2011 at 06:12:10PM -0600, Bob Proulx wrote: Robert Holtzman wrote: Bob Proulx wrote: It definitely is not on mine. Not on Lenny, Squeeze, nor Sid. I just double checked by doing the tests. Variable settings in .bashrc are not available to GNOME. I have this in my .bashrc and they work with no problem: NNTPSERVER='news.sonic.net' export NNTPSERVER BROWSER=firefox/firefox export BROWSER If you are launching something from a shell command line then they would have those settings. But unless something is configured as other than default I don't know how they would appear in the X and GNOME environment. But very likely you already fixed it long ago. :-) A long time ago I learned something: no matter how much you know about linux, every once in a while it rears back and slaps you upside the head to remind you that you still have a looong way to go. I just got reminded again. I deleted the FF line from .bashrc. Works fine because FF is the default in Preferences. What was throwing me was that the NNTP server line *was* required. Then it dawned on me that I was calling my news reader (slrn) from the command line. Your sentence quoted above is the key. Here is the way I looked for environment variables that GNOME knows about. I created this following simple script. #!/bin/sh exec /var/tmp/env.trace.out 21 echo hello env echo goodbye exit 0 I put that in my ~/bin/env.dumper file and chmod a+x on it. Then I right clicked on the GNOME menu bar and clicked Add to panel... then selected Custom Application Launcher and then +Add and then filled the path to the script in for the command field. With that in place I could test the different environments. Running it from the command line would of course show all of my shell variables including those that were set from the .bashrc file. But running it from GNOME itself through the launcher would not. Creating the test script seems a little less crass than adding similar env dump modifications to /usr/bin/sensible-browser itself. But doing so there would of course eliminate the extraneous script. I would move it out of the way and copy it back and then edit the copy. Then after all of the debug was done I could simply move the original back into place and it would completely clean up my debug hacking. That's great. I have to try that when I have time to do some experimenting. So let's say you have GNOME preferences configured so that the web browser will be sensible-browser. In that case it won't get the BROWSER variable setting in .bashrc and then won't launch the desired browser. If that's true (and I'm not saying it isn't) how to explain the browser and nntp lines in my .bashrc working. I still have a hunch I'm misunderstanding something. I am sure it would all make sense if we knew everything that was happening. Instead for GNOME it appears in /etc/X11/Xsession.d/55gnome-session_gnomerc that you need to put settings into ~/.gnomerc instead. I mention this because Paul said he was running GNOME. Users running other session managers would be better served to use ~/.xsession. Haven't set up either one of these. Probably won't as long as the .bashrc is working. I tend to agree that if it isn't broken then don't fix it. But knowing what is really going on would be comforting. And would probably help in the future when it does break. I think you nailed it pretty good. -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: debian sensible browser help
On Tue, Jul 26, 2011 at 08:07:02PM -0600, Bob Proulx wrote: Robert Holtzman wrote: Bob Proulx wrote: AFAIK it is still true that unless you have taken special measures (e.g. ~/.xsession) then the .bashrc environment will not be present to the GNOME desktop. It sure seems to be present out of the box on mine (Lenny and Squeeze). In addition to the browser export setting, I source my .bash_aliases file from it. It definitely is not on mine. Not on Lenny, Squeeze, nor Sid. I just double checked by doing the tests. Variable settings in .bashrc are not available to GNOME. I have this in my .bashrc and they work with no problem: NNTPSERVER='news.sonic.net' export NNTPSERVER BROWSER=firefox/firefox export BROWSER Therefore while setting BROWSER in .bashrc will work for invocations of sensible-browser from the command line it won't have any effect for when GNOME is launched. Gnome has to be launched manually? Not my experience. On my distros it launches at boot. What distros are you basing your statement on? Or am I completely misunderstanding your post? I didn't say anything about launching GNOME manually. Not sure where you read that from. Although you certainly can do so through xinit or startx and many do use those to start up X manually. I misread your post. Sorry. What I said was that setting shell variables in .bashrc won't normally have any presence to applications launched by GNOME. GNOME is normally started by gdm, as you so noted. That doesn't come through either .bash_profile or .bashrc and so variables set there won't be in effect. So let's say you have GNOME preferences configured so that the web browser will be sensible-browser. In that case it won't get the BROWSER variable setting in .bashrc and then won't launch the desired browser. If that's true (and I'm not saying it isn't) how to explain the browser and nntp lines in my .bashrc working. I still have a hunch I'm misunderstanding something. Instead for GNOME it appears in /etc/X11/Xsession.d/55gnome-session_gnomerc that you need to put settings into ~/.gnomerc instead. I mention this because Paul said he was running GNOME. Users running other session managers would be better served to use ~/.xsession. Haven't set up either one of these. Probably won't as long as the .bashrc is working. -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: debian sensible browser help
Robert Holtzman wrote: Bob Proulx wrote: It definitely is not on mine. Not on Lenny, Squeeze, nor Sid. I just double checked by doing the tests. Variable settings in .bashrc are not available to GNOME. I have this in my .bashrc and they work with no problem: NNTPSERVER='news.sonic.net' export NNTPSERVER BROWSER=firefox/firefox export BROWSER If you are launching something from a shell command line then they would have those settings. But unless something is configured as other than default I don't know how they would appear in the X and GNOME environment. But very likely you already fixed it long ago. :-) Here is the way I looked for environment variables that GNOME knows about. I created this following simple script. #!/bin/sh exec /var/tmp/env.trace.out 21 echo hello env echo goodbye exit 0 I put that in my ~/bin/env.dumper file and chmod a+x on it. Then I right clicked on the GNOME menu bar and clicked Add to panel... then selected Custom Application Launcher and then +Add and then filled the path to the script in for the command field. With that in place I could test the different environments. Running it from the command line would of course show all of my shell variables including those that were set from the .bashrc file. But running it from GNOME itself through the launcher would not. Creating the test script seems a little less crass than adding similar env dump modifications to /usr/bin/sensible-browser itself. But doing so there would of course eliminate the extraneous script. I would move it out of the way and copy it back and then edit the copy. Then after all of the debug was done I could simply move the original back into place and it would completely clean up my debug hacking. So let's say you have GNOME preferences configured so that the web browser will be sensible-browser. In that case it won't get the BROWSER variable setting in .bashrc and then won't launch the desired browser. If that's true (and I'm not saying it isn't) how to explain the browser and nntp lines in my .bashrc working. I still have a hunch I'm misunderstanding something. I am sure it would all make sense if we knew everything that was happening. Instead for GNOME it appears in /etc/X11/Xsession.d/55gnome-session_gnomerc that you need to put settings into ~/.gnomerc instead. I mention this because Paul said he was running GNOME. Users running other session managers would be better served to use ~/.xsession. Haven't set up either one of these. Probably won't as long as the .bashrc is working. I tend to agree that if it isn't broken then don't fix it. But knowing what is really going on would be comforting. And would probably help in the future when it does break. Bob signature.asc Description: Digital signature
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 -- 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/loom.20110726t145501...@post.gmane.org
Re: debian sensible browser help
Steve Kleene wrote: 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). This is expected due to the fine grained control exposed in bash. In the bash man page you will find: ~/.bash_profile The personal initialization file, executed for login shells ~/.bashrc The individual per-interactive-shell startup file A very typical thing to do in the ~/.bash_profile is to source the $HOME/.bashrc file with a snippet similar to the following: if [ -f $HOME/.bashrc ]; then . $HOME/.bashrc fi Or this following in ~/.profile which needs to be shell portable: if [ -n $BASH_VERSION ]; then # include .bashrc if it exists if [ -f $HOME/.bashrc ]; then . $HOME/.bashrc fi fi Bob P.S. I am also using fvwm, right now in fact. signature.asc Description: Digital signature
Re: debian sensible browser help
On Tue, Jul 26, 2011 at 02:39:24AM +, Steve Kleene wrote: 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 . 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. That's strange because when I put BROWSER=/usr/bin/firefox export BROWSER in my .bashrc it over rode the sensible-browser entry in /etc/mailcap (I don't use a ~/.mailcap file). -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: debian sensible browser help
On Mon, Jul 25, 2011 at 10:29:43PM -0600, Bob Proulx wrote: Steve Kleene wrote: On Mon, Jul 25, 2011 at 11:53:28PM +, I wrote: From my command line, I tried BROWSER=/usr/bin/iceweasel export BROWSER but found that reading an html e-mail then brought up both iceweasel and sensible-browser. I had no entry for html in ~/.mailcap, and /etc/mailcap listed sensible-browser. I did this all with metamail, which is kind of archaic. 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 . 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. AFAIK it is still true that unless you have taken special measures (e.g. ~/.xsession) then the .bashrc environment will not be present to the GNOME desktop. It sure seems to be present out of the box on mine (Lenny and Squeeze). In addition to the browser export setting, I source my .bash_aliases file from it. Therefore while setting BROWSER in .bashrc will work for invocations of sensible-browser from the command line it won't have any effect for when GNOME is launched. Gnome has to be launched manually? Not my experience. On my distros it launches at boot. What distros are you basing your statement on? Or am I completely misunderstanding your post? Instead for GNOME it appears in /etc/X11/Xsession.d/55gnome-session_gnomerc that you need to put settings into ~/.gnomerc instead. I mention this because Paul said he was running GNOME. Users running other session managers would be better served to use ~/.xsession. Probably best to have the .gnomerc simply dot source (with '.' not 'source', Xsession is a /bin/sh script not a /bin/bash script) the .bashrc file so that you get the same environment both places. -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: debian sensible browser help
Robert Holtzman wrote: Bob Proulx wrote: AFAIK it is still true that unless you have taken special measures (e.g. ~/.xsession) then the .bashrc environment will not be present to the GNOME desktop. It sure seems to be present out of the box on mine (Lenny and Squeeze). In addition to the browser export setting, I source my .bash_aliases file from it. It definitely is not on mine. Not on Lenny, Squeeze, nor Sid. I just double checked by doing the tests. Variable settings in .bashrc are not available to GNOME. Therefore while setting BROWSER in .bashrc will work for invocations of sensible-browser from the command line it won't have any effect for when GNOME is launched. Gnome has to be launched manually? Not my experience. On my distros it launches at boot. What distros are you basing your statement on? Or am I completely misunderstanding your post? I didn't say anything about launching GNOME manually. Not sure where you read that from. Although you certainly can do so through xinit or startx and many do use those to start up X manually. What I said was that setting shell variables in .bashrc won't normally have any presence to applications launched by GNOME. GNOME is normally started by gdm, as you so noted. That doesn't come through either .bash_profile or .bashrc and so variables set there won't be in effect. So let's say you have GNOME preferences configured so that the web browser will be sensible-browser. In that case it won't get the BROWSER variable setting in .bashrc and then won't launch the desired browser. Instead for GNOME it appears in /etc/X11/Xsession.d/55gnome-session_gnomerc that you need to put settings into ~/.gnomerc instead. I mention this because Paul said he was running GNOME. Users running other session managers would be better served to use ~/.xsession. Probably best to have the .gnomerc simply dot source (with '.' not 'source', Xsession is a /bin/sh script not a /bin/bash script) the .bashrc file so that you get the same environment both places. I think it is actually better to do the variable setting through ~/.xsession. It certainly isn't an obvious solution though. In any case it has been discussed to death on the mailing list previously so I will avoid it again here. The 55gnome-session_gnomerc seems to want those in a ~/.gnomerc file. Bob signature.asc Description: Digital signature
Re: debian sensible browser help
On 2011-07-25 02:24:59 GMT, Paul E Condon wrote: How do I make debian offer google-chrome to gnome? I have checked all the places I know of. Where is sensible browser defined? You might check in /etc/mailcap for lines that begin with text/html. I prefer to have iceweasel called instead of sensible-browser, so I move the line with sensible-browser to the end of mailcap. I often have to repeat this procedure after an upgrade. If your mailcap has a text/html line for google-chrome, you might move that above other text/html lines. -- 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/loom.20110725t160434-...@post.gmane.org
Re: debian sensible browser help
On Sun, 24 Jul 2011 20:24:59 -0600, Paul E Condon wrote: I am running squeeze w/ gnome desktop. I am attempting to use google-chrome as my browser, but I also use Mutt as my MUA. Under some situations, maybe always, but it is confusing, when I am presented with an email containing HTML, I am but into Iceweasel rather than google-chrome. I had thought the update-alternatives could fix this, but there is not a sensible browser name in u-a. Googling brings up only hits from several years ago, and only complaints, not solutions. (...) Have you configured google-chrome as your default preferred browser? That's a GNOME setting (start/system/preferences...). Greetings, -- Camaleón -- 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/pan.2011.07.25.14.58...@gmail.com
Re: debian sensible browser help
On Mon, Jul 25, 2011 at 02:05:18PM +, Steve Kleene wrote: On 2011-07-25 02:24:59 GMT, Paul E Condon wrote: How do I make debian offer google-chrome to gnome? I have checked all the places I know of. Where is sensible browser defined? You might check in /etc/mailcap for lines that begin with text/html. I prefer to have iceweasel called instead of sensible-browser, so I move the line with sensible-browser to the end of mailcap. I often have to repeat this procedure after an upgrade. If your mailcap has a text/html line for google-chrome, you might move that above other text/html lines. I believe ~/.mailcap overrides /etc/mailcap, so rather than editing /etc/mailcap and having to keep it up-to-date, you might find it easier to simply copy the line to ~/.mailcap. -- Paul Saunders signature.asc Description: Digital signature
Re: debian sensible browser help
How do I make debian offer google-chrome to gnome? I have checked all the places I know of. Where is sensible browser defined? These are defined in the directory /etc/alternatives. For help, see the man page update-alternatives(8). Mark -- 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/20110725141711.3ef06...@torfree.net
Re: debian sensible browser help
On Mon, Jul 25, 2011 at 04:30:57PM +0100, Darac Marjal wrote: On Mon, Jul 25, 2011 at 02:05:18PM +, Steve Kleene wrote: On 2011-07-25 02:24:59 GMT, Paul E Condon wrote: How do I make debian offer google-chrome to gnome? I have checked all the places I know of. Where is sensible browser defined? You might check in /etc/mailcap for lines that begin with text/html. I prefer to have iceweasel called instead of sensible-browser, so I move the line with sensible-browser to the end of mailcap. I often have to repeat this procedure after an upgrade. If your mailcap has a text/html line for google-chrome, you might move that above other text/html lines. I believe ~/.mailcap overrides /etc/mailcap, so rather than editing /etc/mailcap and having to keep it up-to-date, you might find it easier to simply copy the line to ~/.mailcap. Anything wrong with putting the following line in .bashrc? BROWSER=/usr/bin/google-chrome export BROWSER -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: debian sensible browser help
On Mon, Jul 25, 2011 at 02:05:18PM +, I wrote: You might check in /etc/mailcap for lines that begin with text/html. I prefer to have iceweasel called instead of sensible-browser, so I move the line with sensible-browser to the end of mailcap. I often have to repeat this procedure after an upgrade. On 2011-07-25 15:30:57 GMT, Darac Marjal replied: I believe ~/.mailcap overrides /etc/mailcap, so rather than editing /etc/mailcap and having to keep it up-to-date, you might find it easier to simply copy the line to ~/.mailcap. I tested this and you're right. That's an improvement. Thanks. On 2011-07-25 19:14:48 GMT, Robert Holtzman wrote: Anything wrong with putting the following line in .bashrc? BROWSER=/usr/bin/google-chrome export BROWSER From my command line, I tried BROWSER=/usr/bin/iceweasel export BROWSER but found that reading an html e-mail then brought up both iceweasel and sensible-browser. I had no entry for html in ~/.mailcap, and /etc/mailcap listed sensible-browser. I did this all with metamail, which is kind of archaic. -- 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/loom.20110726t015255-...@post.gmane.org
Re: debian sensible browser help
On Mon, Jul 25, 2011 at 11:53:28PM +, Steve Kleene wrote: On 2011-07-25 19:14:48 GMT, Robert Holtzman wrote: Anything wrong with putting the following line in .bashrc? BROWSER=/usr/bin/google-chrome export BROWSER From my command line, I tried BROWSER=/usr/bin/iceweasel export BROWSER but found that reading an html e-mail then brought up both iceweasel and sensible-browser. I had no entry for html in ~/.mailcap, and /etc/mailcap listed sensible-browser. I did this all with metamail, which is kind of archaic. Try putting that line in .bashrc, log out and back in. Don't forget the . -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: debian sensible browser help SOLVED
On 20110725_140518, Steve Kleene wrote: On 2011-07-25 02:24:59 GMT, Paul E Condon wrote: How do I make debian offer google-chrome to gnome? I have checked all the places I know of. Where is sensible browser defined? You might check in /etc/mailcap for lines that begin with text/html. I prefer to have iceweasel called instead of sensible-browser, so I move the line with sensible-browser to the end of mailcap. I often have to repeat this procedure after an upgrade. If your mailcap has a text/html line for google-chrome, you might move that above other text/html lines. Thanks. sensible-browser is designated in /etc/mailcap. Specifying google-crome in ~/.mailcap overrides the /etc/mailcap entry. Sensible-browser is a script that introduces a layer of indirection of which I was unaware. Now I know. How long I will remember is problematic. -- Paul E Condon pecon...@mesanetworks.net -- 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/20110726005515.gb16...@cmpq.lan.gnu
Re: debian sensible browser help
On Mon, Jul 25, 2011 at 11:53:28PM +, I wrote: From my command line, I tried BROWSER=/usr/bin/iceweasel export BROWSER but found that reading an html e-mail then brought up both iceweasel and sensible-browser. I had no entry for html in ~/.mailcap, and /etc/mailcap listed sensible-browser. I did this all with metamail, which is kind of archaic. 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 . 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. Thanks. -- 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/loom.20110726t043856-...@post.gmane.org
Re: debian sensible browser help
Steve Kleene wrote: On Mon, Jul 25, 2011 at 11:53:28PM +, I wrote: From my command line, I tried BROWSER=/usr/bin/iceweasel export BROWSER but found that reading an html e-mail then brought up both iceweasel and sensible-browser. I had no entry for html in ~/.mailcap, and /etc/mailcap listed sensible-browser. I did this all with metamail, which is kind of archaic. 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 . 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. AFAIK it is still true that unless you have taken special measures (e.g. ~/.xsession) then the .bashrc environment will not be present to the GNOME desktop. Therefore while setting BROWSER in .bashrc will work for invocations of sensible-browser from the command line it won't have any effect for when GNOME is launched. Instead for GNOME it appears in /etc/X11/Xsession.d/55gnome-session_gnomerc that you need to put settings into ~/.gnomerc instead. I mention this because Paul said he was running GNOME. Users running other session managers would be better served to use ~/.xsession. Probably best to have the .gnomerc simply dot source (with '.' not 'source', Xsession is a /bin/sh script not a /bin/bash script) the .bashrc file so that you get the same environment both places. Bob signature.asc Description: Digital signature
debian sensible browser help
I am running squeeze w/ gnome desktop. I am attempting to use google-chrome as my browser, but I also use Mutt as my MUA. Under some situations, maybe always, but it is confusing, when I am presented with an email containing HTML, I am but into Iceweasel rather than google-chrome. I had thought the update-alternatives could fix this, but there is not a sensible browser name in u-a. Googling brings up only hits from several years ago, and only complaints, not solutions. How do I make debian offer google-chrome to gnome? I have checked all the places I know of. Where is sensible browser defined? I'd like to keep iceweasel installed so that I can use it when I choose to, but I never want it to be automatic -- at least until, and if, I choose to reject google-chrome. Suggestions? TIA -- Paul E Condon pecon...@mesanetworks.net -- 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/20110725022459.ga15...@cmpq.lan.gnu
Re: debian sensible browser help
On Sun, Jul 24, 2011 at 10:24 PM, Paul E Condon pecon...@mesanetworks.net wrote: I am running squeeze w/ gnome desktop. I am attempting to use google-chrome as my browser, but I also use Mutt as my MUA. Under some situations, maybe always, but it is confusing, when I am presented with an email containing HTML, I am but into Iceweasel rather than google-chrome. I had thought the update-alternatives could fix this, but there is not a sensible browser name in u-a. Googling brings up only hits from several years ago, and only complaints, not solutions. How do I make debian offer google-chrome to gnome? I have checked all the places I know of. Where is sensible browser defined? I'd like to keep iceweasel installed so that I can use it when I choose to, but I never want it to be automatic -- at least until, and if, I choose to reject google-chrome. Suggestions? TIA -- Paul E Condon pecon...@mesanetworks.net Hi Paul, Re-creating the following symbolic link pointing to the application you prefer should be sufficient: ~$ file /etc/alternatives/gnome-www-browser /etc/alternatives/gnome-www-browser: symbolic link to `/usr/bin/epiphany-browser' Regards, Burhan -- 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/CABSER8XnhfdVq5TDGcd=5humoa69f-qufjtzx-fqbppoajd...@mail.gmail.com
