TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Mike Haaland 72300,1433 (X)
from: Mark Griffith 76070,41
date: 1992-10-16 16:24:39
subject: #16704-#Desktop hacks

#: 16709 S12/OS9/68000 (OSK)
    16-Oct-92  16:24:39
Sb: #16704-#Desktop hacks
Fm: Mark Griffith 76070,41
To: Mike Haaland 72300,1433 (X)

Mike,

What you might want to do is make up a separate icon for a shell script and put
that up when you see a text file that has the execution bit set. Of course,
this may make things more dofficult.  I don't know how you are doing it now,
I'd guess you look for any file with the execution bit set and make that a
program and then anything else is a text file.

I've been playing with Open Look version 3 on one of the Sun workstations at
work.  It has a different icon for each file.  It must read each and every file
to do this thought since it can tell the difference between a "C" source code
file and a header file, as well as a postscript file and a normal text file. 
Pretty slick!  Each icon type then gets a different set of parameters for
forking and printing.  I don't think this will be easy to do for OSK, if at
all, but it sure would be nice!

To answer your question, like Steve said, if it has the execution bit set, and
the first few bytes in the file are not a module header, then make it a shell
script, other wise it is a text file.  If you double click on a text file, run
the editor given in the EDITOR environ variable, or run thhe script if it is
not a text file.

Mark

There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.