Re: [STUMP] run-or-raise behavior

[Shawn Betts]

Jay Belanger <address@hidden> writes:

> I don't know if this is common, but the main reason I use groups is so
> I can have more than one easily accessible instance of a program
> running.  For example, in group 1 "C-t c" might bring up a terminal in
> one directory, and in group 2 "C-t c" might start a terminal to do
> some compiling.  However, run-or-raise will now change groups if
> necessary to find a particular program.  Is it reasonable to make the
> old behavior (stay in the same group) an option?  The following
> (trivial) patch will add an allgroups keyword to run-or-raise; if
> :allgroups is t (the default), run-or-raise will search all groups
> before starting a program, if nil, it will only stay in the current
> group.

Hi Jay,

I decided to take a slightly different approach and make a global
variable that controls this behavior. There's still a key that you can
use to override the global variable. This way you can use the global
var to control the default behavior.

It's in CVS.

-Shawn