Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!uwm.edu!lll-winken!sun-barr!newstop!sun!amdcad!ashirvad!indra
From: indra@ashirvad.amd.com (Indra Singhal)
Newsgroups: comp.mail.elm
Subject: Re: OpenWindows 2.0 shelltool & elm quirks.
Message-ID: <1990Aug17.022111.21856@amd.com>
Date: 17 Aug 90 02:21:11 GMT
References: <1990Aug15.210147.11131@amd.com>
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices; Sunnyvale, CA
Lines: 26

In article <1990Aug15.210147.11131@amd.com> indra@ashirvad.amd.com I write:
>I never had the following problem when I used SunView. Now when I set up
>a OpenWindows Menu Item to fireup elm in a shelltool, I get
>unpredictable results. The various things that happened are:
>	o	The initial elm menu display was mangled, seemed like
>		elm was unable to determine the size of the window.
>	o	The menu was blank... header line had the # of messages
>		displayed and a Command: sat at the bottom of an empty
>		screen.
>
>Has any one been playing with OpenWindows 2.0 and elm? I am running on
>an SPARCstation SLC with SunOS 4.1;

After a bunch of experimentation, I was able to have OpenWindows 2.0
shelltool handle elm OK by using the -I option:

	shelltool -Wh 50 -Ww 80 -I "exec elm"

to get a 80x50 window and I guess since the exec elm is invoked in a
different fashion than a command tacked at the end of the statement:
	shelltool -Wh 50 -Ww 80 elm
it behaves perfectly.
--
iNDRA | indra@amd.com (Indra Singhal) (408) 749-5445
      | {ames decwrl apple pyramid sun uunet}!amdcad!indra
      | MS 167; Box 3453; 901, Thompson Pl., Sunnyvale, CA 94088