icewm

The settings for those options are in the preferences file.

On Mon, Mar 22, 2010 at 4:37 AM, Enguerran Vanquelef
<enguerran.vanquelef@...> wrote:
> Dear IceWM users,
>
> I have discover IceWM recently and have configured some options for
> exemple : my start
> menu.
>
> I have created an ~/.icewm directory, and have touched some files :
> menu, preferences,
> prefoverride, startup etc.
>
> I have edited the ~/.icewm/menu file as I want and have then "my""
> program shortcuts in
> the start menu.
>
> However, 4 sub-menus of my start menu are present when I click on the
> start button but
> are not present in my ~/.icewm/menu file. These sub-menus are at the
> bottom of the start
> menu : windows, help, settings, and leave.
>
> I would like to know how configuring these 4 sub-menus, and how
> removing them from my
> start menu.. Could-you help me ?
>
> Thanks in advance, regards,
>
> Enguerran Vanquelef
> UMR CNRS 6219, Faculté de Pharmacie d'Amiens
> Enguerran Vanquelef
> UMR CNRS 6219, Faculté de Pharmacie d'Amiens - France
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
> _______________________________________________
> IceWM-user mailing list
> IceWM-user@...
> https://lists.sourceforge.net/lists/listinfo/icewm-user
>

Thank you for your answer.

I was convinced that this kind of option must be setted in  
~/.icewm/menu file. After reading  
http://www.icewm.org/manual/icewm-10.html#ss10.1, I found the two  
options ShowThemesMenu & ShowHelp and modified them. I need again help  
for the last sub-menu (Déconnexion in french, ie leave in english I  
suppose, see below).

When I leave IceWM to turn off my laptop, I cannot shutdown directly.  
IceWM exits and I must shutdown my computer using the session manager  
shutdown menu.

Can you explain me how configuring the leave sub-menu ? (I'm not sure  
about this name, in french, it is "déconnexion" i.e. "deconnecting" in  
english but I think this mean the "Leave" button on other window  
managers).

I have noted that I can hit CTRL-ALT-SUPPR to open an option window  
where I can restart IceWM, shutdown and other things, but "shutdown"  
is not accessible (maybe editing /etc/sudoers will help me - I have  
not try yet.)

Thanks in advance,

Enguerran Vanquelef
UMR CNRS 6219, Faculté de Pharmacie d'Amiens - France


Quoting Matt <lacrima97@...>:

> The settings for those options are in the preferences file.
>
> On Mon, Mar 22, 2010 at 4:37 AM, Enguerran Vanquelef
> <enguerran.vanquelef@...> wrote:
>> Dear IceWM users,
>>
>> I have discover IceWM recently and have configured some options for
>> exemple : my start
>> menu.
>>
>> I have created an ~/.icewm directory, and have touched some files :
>> menu, preferences,
>> prefoverride, startup etc.
>>
>> I have edited the ~/.icewm/menu file as I want and have then "my""
>> program shortcuts in
>> the start menu.
>>
>> However, 4 sub-menus of my start menu are present when I click on the
>> start button but
>> are not present in my ~/.icewm/menu file. These sub-menus are at the
>> bottom of the start
>> menu : windows, help, settings, and leave.
>>
>> I would like to know how configuring these 4 sub-menus, and how
>> removing them from my
>> start menu.. Could-you help me ?
>>
>> Thanks in advance, regards,
>>
>> Enguerran Vanquelef
>> UMR CNRS 6219, Faculté de Pharmacie d'Amiens
>> Enguerran Vanquelef
>> UMR CNRS 6219, Faculté de Pharmacie d'Amiens - France
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; 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
>> _______________________________________________
>> IceWM-user mailing list
>> IceWM-user@...
>> https://lists.sourceforge.net/lists/listinfo/icewm-user
>>
>
>

On Mon, 22 Mar 2010 21:32:00 +0100
Enguerran Vanquelef <enguerran.vanquelef@...>
wrote:

> Thank you for your answer.
> 
> I was convinced that this kind of option must be setted in  
> ~/.icewm/menu file. After reading  
> http://www.icewm.org/manual/icewm-10.html#ss10.1, I found the two  
> options ShowThemesMenu & ShowHelp and modified them. I need again
> help for the last sub-menu (Déconnexion in french, ie leave in
> english I suppose, see below).
> 
> When I leave IceWM to turn off my laptop, I cannot shutdown
> directly. IceWM exits and I must shutdown my computer using the
> session manager shutdown menu.
> 
> Can you explain me how configuring the leave sub-menu ? (I'm not
> sure about this name, in french, it is "déconnexion" i.e.
> "deconnecting" in english but I think this mean the "Leave" button
> on other window managers).

These are in your preferences file.

#  Command to start logout
# LogoutCommand=""

#  Command to cancel logout
# LogoutCancelCommand=""

#  Command to shutdown the system
ShutdownCommand="sudo halt"

#  Command to reboot the system
RebootCommand="sudo reboot"


The last 2 are what you are looking for I think.
-- 
Frank McCormick<beacon@...>

Quoting Frank McCormick <beacon@...>:

> These are in your preferences file.
>
> #  Command to start logout
> # LogoutCommand=""
>
> #  Command to cancel logout
> # LogoutCancelCommand=""
>
> #  Command to shutdown the system
> ShutdownCommand="sudo halt"
>
> #  Command to reboot the system
> RebootCommand="sudo reboot"
>
>
> The last 2 are what you are looking for I think.
> --
> Frank McCormick<beacon@...>

Great !

Thank you very much. How do you know this ? I searched on the IceWM  
website (http://www.icewm.org/manual/icewm-10.html) but  have not  
found (maybe I'm blind ?!?).

CTRL+ALT+SUPPR allow me to reboot or halt my system. What about  
implementation of these two options in the menu ? I know I can add an  
entry in my ~/.icewm/menu file as I done for programs, but do you know  
how hidding the "deconnect" or "leave" sub-menu ?

Thanks again,


Enguerran Vanquelef
UMR CNRS 6219, Faculté de Pharmacie d'Amiens - France

On Tue, 23 Mar 2010 09:27:11 +0100
Enguerran Vanquelef <enguerran.vanquelef@...>
wrote:

> Quoting Frank McCormick <beacon@...>:
> 
> > These are in your preferences file.
> >
> > #  Command to start logout
> > # LogoutCommand=""
> >
> > #  Command to cancel logout
> > # LogoutCancelCommand=""
> >
> > #  Command to shutdown the system
> > ShutdownCommand="sudo halt"
> >
> > #  Command to reboot the system
> > RebootCommand="sudo reboot"
> >
> >
> > The last 2 are what you are looking for I think.
> > --
> > Frank McCormick<beacon@...>
> 
> Great !
> 
> Thank you very much. How do you know this ? I searched on the
> IceWM website (http://www.icewm.org/manual/icewm-10.html) but  have
> not found (maybe I'm blind ?!?).

   Everything I know about IceWm is learned by going through the
preferences file and trying various options to see what effect
they had.


> 
> CTRL+ALT+SUPPR allow me to reboot or halt my system. What about  
> implementation of these two options in the menu ? I know I can add
> an entry in my ~/.icewm/menu file as I done for programs, but do
> you know how hiding the "deconnect" or "leave" sub-menu ?

   Maybe some of these may help:


#  Show programs submenu
ShowProgramsMenu = 1 # 0/1

#  Show settings submenu
ShowSettingsMenu=1 # 0/1

#  Show focus mode submenu
ShowFocusModeMenu=1 # 0/1

#  Show themes submenu
ShowThemesMenu = 1 # 0/1

#  Show logout submenu
ShowLogoutMenu = 1 # 0/1        <<<<<<<<<<<<<<<<<

#  Show the help menu item
ShowHelp = 1 # 0/1

#  Show logout submenu
ShowLogoutSubMenu = 1 # 0/1     <<<<<<<<<<<<<<<<<

#  Show the about menu item
ShowAbout = 1 # 0/1

#  Show the run menu item
ShowRun = 1 # 0/1

#  Show the window menu item
# ShowWindowList=1 # 0/1

#  Allow to switch a window to fullscreen
# AllowFullscreen=1 # 0/1

#  Enable address bar functionality in taskbar
EnableAddressBar=1 # 0/1

#  Show address bar in task bar
ShowAddressBar=1 # 0/1

#  Overrides automatic multiple byte detection
# MultiByte=1 # 0/1

#  Confirm logout
# ConfirmLogout=1 # 0/1  <<<<<<<<<<<<<<<<<<<<<<<<


  
-- 
Frank<beacon@...>

Thank you,

Now all is as I want.

regards,

Enguerran Vanquelef
UMR CNRS 6219, Faculté de Pharmacie d'Amiens - France


Quoting Frank McCormick <beacon@...>:

> On Tue, 23 Mar 2010 09:27:11 +0100
> Enguerran Vanquelef <enguerran.vanquelef@...>
> wrote:
>
>> Quoting Frank McCormick <beacon@...>:
>>
>> > These are in your preferences file.
>> >
>> > #  Command to start logout
>> > # LogoutCommand=""
>> >
>> > #  Command to cancel logout
>> > # LogoutCancelCommand=""
>> >
>> > #  Command to shutdown the system
>> > ShutdownCommand="sudo halt"
>> >
>> > #  Command to reboot the system
>> > RebootCommand="sudo reboot"
>> >
>> >
>> > The last 2 are what you are looking for I think.
>> > --
>> > Frank McCormick<beacon@...>
>>
>> Great !
>>
>> Thank you very much. How do you know this ? I searched on the
>> IceWM website (http://www.icewm.org/manual/icewm-10.html) but  have
>> not found (maybe I'm blind ?!?).
>
>    Everything I know about IceWm is learned by going through the
> preferences file and trying various options to see what effect
> they had.
>
>
>>
>> CTRL+ALT+SUPPR allow me to reboot or halt my system. What about
>> implementation of these two options in the menu ? I know I can add
>> an entry in my ~/.icewm/menu file as I done for programs, but do
>> you know how hiding the "deconnect" or "leave" sub-menu ?
>
>    Maybe some of these may help:
>
>
> #  Show programs submenu
> ShowProgramsMenu = 1 # 0/1
>
> #  Show settings submenu
> ShowSettingsMenu=1 # 0/1
>
> #  Show focus mode submenu
> ShowFocusModeMenu=1 # 0/1
>
> #  Show themes submenu
> ShowThemesMenu = 1 # 0/1
>
> #  Show logout submenu
> ShowLogoutMenu = 1 # 0/1        <<<<<<<<<<<<<<<<<
>
> #  Show the help menu item
> ShowHelp = 1 # 0/1
>
> #  Show logout submenu
> ShowLogoutSubMenu = 1 # 0/1     <<<<<<<<<<<<<<<<<
>
> #  Show the about menu item
> ShowAbout = 1 # 0/1
>
> #  Show the run menu item
> ShowRun = 1 # 0/1
>
> #  Show the window menu item
> # ShowWindowList=1 # 0/1
>
> #  Allow to switch a window to fullscreen
> # AllowFullscreen=1 # 0/1
>
> #  Enable address bar functionality in taskbar
> EnableAddressBar=1 # 0/1
>
> #  Show address bar in task bar
> ShowAddressBar=1 # 0/1
>
> #  Overrides automatic multiple byte detection
> # MultiByte=1 # 0/1
>
> #  Confirm logout
> # ConfirmLogout=1 # 0/1  <<<<<<<<<<<<<<<<<<<<<<<<
>
>
>
> --
> Frank<beacon@...>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
> _______________________________________________
> IceWM-user mailing list
> IceWM-user@...
> https://lists.sourceforge.net/lists/listinfo/icewm-user
>
>

--- On Mon, 3/22/10, jaro <jaromrax@...> wrote:
 
> I want evolution, skype and some other progs. have on
> startup (done), and
> appearing in the workspace #2.
> I have winoptions file starting like:
> 
> Skype.Workspace: 2
> skype.Workspace: 2

Run 'xprop' to make sure you're using the corrent window name/class.

I use lowercase 'workspace' which works OK

>From src/themable.h

"User load on the CPU monitor"),
"System load on the CPU monitor"),
"Interrupts on the CPU monitor"),
"IO Wait on the CPU monitor"),
"Soft Interrupts on the CPU monitor"),
"Nice load on the CPU monitor"),
"Idle (non) load on the CPU monitor, leave empty to force transparency"),

I hope this helps.  Since the colors are theme specified, those can't
really be matched to a particular piece of the monitor without looking
in the theme.

::: Matthew

On Wed, Mar 10, 2010 at 3:35 PM, David J Iannucci
<vprjzhfrezy@...> wrote:
> One of the things I love most about IceWM is the cpu/disk and network
> monitors in the taskbar (there's a serious problem with subject-verb
> number agreement in that sentence, but I'm gonna let it go :-) They are
> simple, beautiful and very informative.  I haven't yet found better ones
> in any WM or desktop framework.
>
> Over the years I've managed to guess the meaning of the colors used in
> the cpu/disk monitor _roughly_, but I'm still not exactly sure what
> color means what (the network one is pretty obvious). Does anyone have
> an authoritative answer for this?  I'm pretty sure I've never seen it in
> the docs on the web site, and  I'd really like to know.
>
> Thanks,
> Dave
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
> _______________________________________________
> IceWM-user mailing list
> IceWM-user@...
> https://lists.sourceforge.net/lists/listinfo/icewm-user
>

Thanks a lot!  However if I search through the files making up my theme
(blueHeart - another reason I can't leave IceWM :-), I can't find any
reference to the color identifiers named in themable.h, and it appears
my theme uses the default colors, which I was able to find in the source
code (if anyone wants to know what they are, follow up and I'll post).

I would have sworn that disk activity was reported by this monitor, but
it appears not to be so.  IIRC, the colors that I was associating with
disk activity are "user load" and "system load".  Maybe these things
encompass disk activity? (me, sheepishly ignorant -> :-})

I did wanna ask one more thing, which is the thing that really spurred
me to finally post this: lately my machine will suddenly start showing a
high level of interrupts (the third item on your list below).  I have no
idea what causes this, and it goes on and on until I reboot the machine.
I know this is (probably) not IceWM related, but if anyone has a clue
what could be causing this, I'd be grateful for the advice :-)

Dave


On Wed, 10 Mar 2010 16:02 -0600, "Matt" <lacrima97@...> wrote:
> From src/themable.h
> 
> "User load on the CPU monitor"),
> "System load on the CPU monitor"),
> "Interrupts on the CPU monitor"),
> "IO Wait on the CPU monitor"),
> "Soft Interrupts on the CPU monitor"),
> "Nice load on the CPU monitor"),
> "Idle (non) load on the CPU monitor, leave empty to force
>         transparency"),
>
> I hope this helps.  Since the colors are theme specified, those can't
> really be matched to a particular piece of the monitor without looking
> in the theme.
>
> ::: Matthew
>
> On Wed, Mar 10, 2010 at 3:35 PM, David J Iannucci
> <vprjzhfrezy@...> wrote:
> > One of the things I love most about IceWM is the cpu/disk and
> > network monitors in the taskbar (there's a serious problem with subject-
> > verb number agreement in that sentence, but I'm gonna let it go :-)
> > They are simple, beautiful and very informative.  I haven't yet
> > found better ones in any WM or desktop framework.
> >
> > Over the years I've managed to guess the meaning of the colors
> > used in the cpu/disk monitor _roughly_, but I'm still not exactly
> > sure what color means what (the network one is pretty obvious).
> > Does anyone have an authoritative answer for this?  I'm pretty
> > sure I've never seen it in the docs on the web site, and  I'd
> > really like to know.
> >
> > Thanks,
> > Dave

Hmm, some wifi problem would be my first guess, purely a guess of course.

On Thu, Mar 11, 2010 at 7:20 PM, David Iannucci
<vprjzhfrezy@...> wrote:
> Thanks a lot!  However if I search through the files making up my theme
> (blueHeart - another reason I can't leave IceWM :-), I can't find any
> reference to the color identifiers named in themable.h, and it appears
> my theme uses the default colors, which I was able to find in the source
> code (if anyone wants to know what they are, follow up and I'll post).
>
> I would have sworn that disk activity was reported by this monitor, but
> it appears not to be so.  IIRC, the colors that I was associating with
> disk activity are "user load" and "system load".  Maybe these things
> encompass disk activity? (me, sheepishly ignorant -> :-})
>
> I did wanna ask one more thing, which is the thing that really spurred
> me to finally post this: lately my machine will suddenly start showing a
> high level of interrupts (the third item on your list below).  I have no
> idea what causes this, and it goes on and on until I reboot the machine.
> I know this is (probably) not IceWM related, but if anyone has a clue
> what could be causing this, I'd be grateful for the advice :-)
>
> Dave
>
>
> On Wed, 10 Mar 2010 16:02 -0600, "Matt" <lacrima97@...> wrote:
>> From src/themable.h
>>
>> "User load on the CPU monitor"),
>> "System load on the CPU monitor"),
>> "Interrupts on the CPU monitor"),
>> "IO Wait on the CPU monitor"),
>> "Soft Interrupts on the CPU monitor"),
>> "Nice load on the CPU monitor"),
>> "Idle (non) load on the CPU monitor, leave empty to force
>>         transparency"),
>>
>> I hope this helps.  Since the colors are theme specified, those can't
>> really be matched to a particular piece of the monitor without looking
>> in the theme.
>>
>> ::: Matthew
>>
>> On Wed, Mar 10, 2010 at 3:35 PM, David J Iannucci
>> <vprjzhfrezy@...> wrote:
>> > One of the things I love most about IceWM is the cpu/disk and
>> > network monitors in the taskbar (there's a serious problem with subject-
>> > verb number agreement in that sentence, but I'm gonna let it go :-)
>> > They are simple, beautiful and very informative.  I haven't yet
>> > found better ones in any WM or desktop framework.
>> >
>> > Over the years I've managed to guess the meaning of the colors
>> > used in the cpu/disk monitor _roughly_, but I'm still not exactly
>> > sure what color means what (the network one is pretty obvious).
>> > Does anyone have an authoritative answer for this?  I'm pretty
>> > sure I've never seen it in the docs on the web site, and  I'd
>> > really like to know.
>> >
>> > Thanks,
>> > Dave
>

Upgrade your Xorg related packages using the version currently
available in updates-testing repository (0:1.7.5.901-4.fc12).
In that version Fedora folks reverted one of their *hm* patches ;-)

Here's the entry from their changelog:
* Tue Mar 09 2010 Peter Hutterer <peter.hutterer@...> 1.7.5.901-3
- Revert to previous version of xserver-1.7.5-owner-events.patch. The one in
  git breaks fluxbox.

Running
  yum --enablerepo=updates-testing update xorg-\*
should do the trick.

cheers
--
altblue

Hi Marius (and friends):

Talk about a "HOME RUN" response to my question Marius! Your
reply was PERFECT: First you described what happened; then you
provided the precise command to correct the situation;
which I then cut-and-pasted (after taking a snapshot of my
O/S to be safe =:)).

Below we can see the packages that were clearly updated
(or backed out depending on how you view it). It all works
perfectly now. Thank you so much!

=========================================================
root@...# yum --enablerepo=updates-testing update xorg-\*
    
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating       : xorg-x11-server-common-1.7.5.901-4.fc12.x86_64                                       1/10 
  Updating       : xorg-x11-server-Xvfb-1.7.5.901-4.fc12.x86_64                                         2/10 
  Updating       : xorg-x11-server-Xephyr-1.7.5.901-4.fc12.x86_64                                       3/10 
  Updating       : xorg-x11-server-Xnest-1.7.5.901-4.fc12.x86_64                                        4/10 
  Updating       : xorg-x11-server-Xorg-1.7.5.901-4.fc12.x86_64                                         5/10

  Cleanup        : xorg-x11-server-Xvfb-1.7.5.901-1.fc12.x86_64                                         6/10 
  Cleanup        : xorg-x11-server-Xephyr-1.7.5.901-1.fc12.x86_64                                       7/10 
  Cleanup        : xorg-x11-server-Xnest-1.7.5.901-1.fc12.x86_64                                        8/10 
  Cleanup        : xorg-x11-server-Xorg-1.7.5.901-1.fc12.x86_64                                         9/10 
  Cleanup        : xorg-x11-server-common-1.7.5.901-1.fc12.x86_64                                      10/10 

Complete!

========================================================


________________________________
From: Marius Feraru <altblue@...>
To: Noel Milton Vega <nmvega@...>
Cc: icewm-user@...
Sent: Thu, March 11, 2010 6:12:39 PM
Subject: Re: Icewm (v1.2.37-7.fc12.x86_64) taskbar/toolbar clicks makes mouse  input unsreponsive ...

Upgrade your Xorg related packages using the version currently
available in updates-testing repository (0:1.7.5.901-4.fc12).
In that version Fedora folks reverted one of their *hm* patches ;-)

Here's the entry from their changelog:
* Tue Mar 09 2010 Peter Hutterer <peter.hutterer@...> 1.7.5.901-3
- Revert to previous version of xserver-1.7.5-owner-events.patch. The one in
  git breaks fluxbox.

Running
  yum --enablerepo=updates-testing update xorg-\*
should do the trick.

cheers
--
altblue

On 28 Feb 2010, icewm-user-request@... wrote:
> Message: 5
> Date: Fri, 26 Feb 2010 17:00:20 +0000
> From: Anthony Campbell <ac@...>
> Subject: Menu entries for browsers stopped working
> To: icewm-user@...
> Message-ID: <20100226170020.GA4351@...>
> Content-Type: text/plain; charset=us-ascii
> 
> 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.
> 
> I can run iceweasel from a terminal without problems. 
> The issue is on my HP laptop; on my desktop there is no problem.
> 
> I am not sure that this is an icewm problem but I have no idea how to go
> about identifying its source. Any suggestions for what to try?
> 
> Anthony

Thanks to everyone who replied to this thread. I found the problem in
the end: I had a file in $HOME/bin called "which", containing the one
line "type -path". Deleting this made things work normally. I don't know
why it had this effect, especially since I have the same file on a
different machine where it doesn't produce this effect. Anyway, it's
fine now.

Anthony


-- 
Anthony Campbell - ac@... 
Microsoft-free zone - Using Debian GNU/Linux 
http://www.acampbell.org.uk - sample my ebooks at
http://www.smashwords.com/profile/view/acampbell

On Mon, Mar 08, 2010 at 02:58:19PM +0000, Anthony Campbell wrote

> Thanks to everyone who replied to this thread. I found the problem in
> the end: I had a file in $HOME/bin called "which", containing the one
> line "type -path". Deleting this made things work normally. I don't know
> why it had this effect, especially since I have the same file on a
> different machine where it doesn't produce this effect. Anyway, it's
> fine now.

  "/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 <waltdnes@...>