#: 17097 S12/OS9/68000 (OSK)
    18-Nov-92  05:31:51
Sb: #17082-More Desktop Stuff
Fm: Mark Griffith 76070,41
To: Mike Haaland 72300,1433 (X)

Mike,

 > Depends how well you, Steve and I like it.  I'm not sure how to make shell
 > scripts run if I keep it in.  I guess you could Open a shell script, yuk!

I like it, but if it means I can't click on a shell script to run it, then I'd
rather not have it in there.  My original idea was to have Desktop check the
execute attribute on the file and run it if it was set, otherwise pull it into
the editor.  If this is not possible, then I'd rather have it set to run the
file by default.  An alternative would be to allow the user to 'Open' the file
into the editor.

 > It now uses the SHELL env var for all shell access, including forking basic
 > i-code.  Does smersh and sh both understand basic i-code needs RunB and
 > automatically for it that way?

Is this set in the version I have (last one you uploaded)?  No, smersh doesn't
understand BASIC i-code, and I'm sure sh and csh don't either. Could you make
two environment variables, say SHELLRUN and SHELLINTER and let the user pick
what they want?  For the BASIC i-code problem, again, you should be able to
look at the module header of the file and see it is an i-code file and then run
BASIC directly.

I know this makes more work for you, but I really believe you need to make this
as user setable as possible.  The more little touches you add like this, the
more positive response you will get from your users.

On another note, if you want me to do your docs, you should be sending me
something soon so I can get started.