Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!EMPTYS.CC.UMICH.EDU!mts
From: mts@EMPTYS.CC.UMICH.EDU (Michael T. Stolarchuk)
Newsgroups: comp.windows.x
Subject: menuwm and shell
Message-ID: <8705080031.AA12483@emptys.cc.umich.edu>
Date: Thu, 7-May-87 20:31:53 EDT
Article-I.D.: emptys.8705080031.AA12483
Posted: Thu May  7 20:31:53 1987
Date-Received: Sat, 9-May-87 21:17:08 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 47


The current version of menuwm I have exec's a shell
depending on the SHELL environment variable.  This is
a good idea.  But I usually use the csh, and don't
want my SHELL=/bin/sh for menuwm...  the obivous solution
is a shell script...

	#/bin/sh
	# don't forget to set it (SHELL doesn't care)
	SHELL=/bin/sh
	menuwm ...

But for those who don't like to cover up programs with
additional scripts, and want more control over menuwm...
How about another variable in .menuwmrc... shell

... Like this
resizefont=9x15
shell=/bin/sh
...

(ps: maybe I did something else wrong.  when I used menuwm
with SHELL=/bin/csh, I ran menuwm in the background.  In doing
so, every command issued by menuwm was run by /bin/csh.  But
csh wanted to display the proc number of the background proc,
and needed the 'terminal' in the foreground... menuwm would
block until 'fg' was done to allow the background /bin/csh
to pring the process number. that's how my [this] mess started)

(pps: menuwm is nice)

*** uwm.h
260a261
> extern char Shell[];		/* Shell name */
*** global.c
112a113
> char Shell[NAME_LEN];		/* Shell to use */
168a170
>     { "shell",		IsString,	0,0,Shell,0 },
*** Menu.c
101c101,104
< 		shell = (cptr = getenv("SHELL")) ? cptr : "/bin/csh" ;
---
> 		if (Shell[0] == 0)
> 			shell = (cptr = getenv("SHELL")) ? cptr : "/bin/csh" ;
> 		else
> 			shell = Shell;