Re: IceWM-user Digest, Vol 39, Issue 1
Anthony Campbell <[email protected]>
| Newsgroups | gmane.comp.window-managers.icewm.user |
|---|---|
| Message-ID | <[email protected]> |
On 10 Mar 2010, [email protected] wrote: > > > Date: Sun, 28 Feb 2010 14:43:32 -0500 > From: Frank McCormick <[email protected]> > Subject: Re: Menu entries for browsers stopped working > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=US-ASCII > > On Sun, 28 Feb 2010 19:05:24 +0000 > Anthony Campbell <[email protected]> wrote: > > > > I have been using icewm for a long time with menu entries of the > > > form: > > > > > > prog Iceweasel - iceweasel > > > > > > This always worked perfectly. Now it doesn't; nothing happens at > > > all, no error messages, nothing. I tried putting in the full path > > > without effect. > > > > > > > Thanks to all for replies. > > > > In reply to Dave: it's all the browsers I have that produce this: > > iceweasel, firefox, iceape, lynx. Icewm is version 1.2.30-1 from > > Debian Sid. > > > > > That version of Icewm is pretty old. Sure you got it from Sid ? This is > what is listed for Sid now . > > Sorry, yes, it is 1.3.6-1 > > > Message: 7 > Date: Mon, 8 Mar 2010 23:38:42 -0500 > From: "Walter Dnes" <[email protected]> > Subject: Re: IceWM-user Digest, Vol 38, Issue 1 > To: ICEWM Users List <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > "/usr/bin/which" is a posix utility that can find the first occurence > of an executable file (script or compiled program) in your path; e.g. > > [d531][waltdnes][~] which firefox > /usr/bin/firefox > > I will make a logical deduction here. On the machine which had > problems, your PATH variable has $HOME/bin (or some version thereof) > *BEFORE* /usr/bin. This is probably what caused the problem. Take a > look at your bash init file where PATH is set. I recommend putting your > own stuff at the end. If you *ABSOLUTELY MUST* override the order, > don't use $HOME/bin, because that puts *EVERY* local script/compiled > program in there ahead of $HOME/bin. Instead... > - create a directory $HOME/priority > - put your scripts that you want over-riding standard programs in there > - put $HOME/priority at the front of your PATH > > -- > Walter Dnes <[email protected]> No, $HOME/bin is at the end of the path. I think the mistake was to write the "which" script in the first place (can't remember why I did). Possibly it created a loop. Anthony -- Anthony Campbell - [email protected] Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk - sample my ebooks at http://www.smashwords.com/profile/view/acampbell ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev