HDTenEightyP/NetNews huggingface dataset:
From: tfj@hillkomm.dk (Torben Fjerdingstad)
Newsgroups: comp.unix.shell
Subject: zapuser script questions
Keywords: How do I remove last argument from a variable?
Date: 16 Dec 92 08:30:42 GMT
Organization: Hilleroed Kommune


I want to make at script to kill all processes attached to at specific
users terminal.

I also want to be sure that the users running applications get a fair
deal.

Therefore i tried `ps -e|grep <tty> | sort -n -r' to get the child
processes first in the kill queue.

That did not work well.  Some parents die before their childen.
I often got messages from kill: xxxxx: no such process and user
applications left stuff hanging around.

THEN I got an idea: How about tsort? That damned thing I fought with,
trying to build a curses library for Minix. 

My questions are below the script:

#!/bin/sh
# Assuming these field from a `ps -fe' (sys5r3.2):
# ps:  UID   PID  PPID  C   STIME TTY TIME COMMAND
# awk:  $1    $2    $3             $6
if [ $# -ne 1 ]
then
	echo "usage: $0 <tty>"
	exit 1
fi
TTY="$1"

SORTED_PROCS=`ps -fe|\
awk '$6 == tty { printf("%s %s\n",$2,$3)}' tty="$TTY" - | tsort`
# (thanks to the c.u.q faq list)

echo $SORTED_PROCS
echo "I guess you see pid 1 (init) as the last one."

# Now the hard skipping of last arg.
NUMPROCS=`echo $SORTED_PROCS | wc -w`

KILL_LIST=`for arg in $SORTED_PROCS
   do
      NUMPROCS=\`expr $NUMPROCS - 1\`
      if [ $NUMPROCS != "0" ]
         then
         echo $arg
      fi
   done`

echo killing $KILL_LIST
# enable after test:
#for proc in $KILL_LIST
#do
#   kill -1 $proc || kill -15 $proc || kill -9 $proc
#done
# END

Questions:
==========
The KILL_LIST loop is ugly. It's only purpose is to skip the last argument
of $SORTED_PROCS. How do I do that simple? Can it be done without external
commands?

What does tsort actually do? Does it really work here?

Any comments?

Please email, and I will summarize.


-- 
Torben
tfj@hillkomm.dk
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.shell
Subject: rsh terminates while loop
Date: 14 Dec 92 20:21:47 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY


  A friend just brought this one in, and I've simplified it down to
something you can type in and ponder. He wants to call a shell script
with a filename, and read two variables per line from the file, and
execute a command on a remote machine using rsh, including the two
values read off a line.

  It appears that the rsh does /something/ which wipes out the stdin of
the while loop. What I would like to understand is what's happening (I
already have an ugly but functional workaround).

$ cat y.tmp
qx1 -a
qx2 -a
danqx -l
$ cat x.tmp
#!/bin/sh
while read host flags
do
 result=`rsh $host uname $flags`
 echo "$host: $result"
done
$ ./x.tmp < y.tmp
qx1: qx1
$

Note that after reading a single line from the file the while loop ends.
Any command other than rsh does not cause this, and if you use ksh you
get an illegal IOCTL fault (under SunOS).

This fails under SunOS and HP-UX, but works with SCO ODT at a minimum,
supposedly fails on virtually anything with a form of rsh (aka rcmd,
remsh, etc) based on BSD code. I *think* it's a bug in rsh in the
redirecting of the i/o to sockets and pulling it back, but I don't
swear to it. 

If anyone has some words of wisdom on this I'd love to hear them, it
really should be valid as posted. I'll try to get a chance to test on a
few other machines in the next few days.

--
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
Newsgroups: comp.unix.shell
From: guenther@stolaf.edu (Philip A Guenther)
Subject: Re: Reading a line from a file in Bourne
Organization: Academic Computing Center, St. Olaf College
Distribution: usa
Date: 11 Dec 92 14:06:49

In article <SHUTTON.92Dec11112920@fokker.union.indiana.edu> shutton@fokker.union.indiana.edu (Scott K. Hutton) writes:
   This is something that has eluded me  for a good while, but now I have
   to find out.  How can  you read lines (yes, entire lines) sequentially
   in from a file and store them in a variable.  For example:

     for ITEM in `cat $FILENAME`
       do echo a full line: $ITEM
     done

   If you're given a file that contains:

     Line one
     Line two

   This script would output

     a full line: Line
     a full line: one
     a full line: Line
     a full line: two

   Any easy answers?

How about:

while read i; do
	echo A line: $i
done <$FILENAME

Philip Guenther
--
guenther@stolaf.edu (Philip Guenther)       | The ACC might agree with me,
Student Sys Prog, Academic Computing Center | but with that bunch, (and me)
St Olaf College, Northfield, MN 55057-1001  | you never know... :-) :-| :-(
"Life makes sense?  LIFE MAKES SENSE!!?  Where do people get these ideas?"-me
From: leisner@wrc.xerox.com ( Marty Leisner)
Newsgroups: comp.unix.shell
Subject: Opening up remote xterm windows?
Date: 20 Dec 92 21:52:37 GMT
Reply-To: leisner@eso.mc.xerox.com
Organization: Xerox
X-Newsreader: TIN [version 1.1 PL8]

I want a good way to open up remote xterm windows...

I'm using bash and have this a function:
rxterm () 
{ 
    rsh $1 ./dologin "xterm -title $1 -display `hostname`:0 -e bash "  &
}

In .dologin, I have:
#! /bin/csh

source ~/.login
$* &


to read my .login file (and set up my environment and path -- I don't use this
in csh...).


I then invoke the command (in this case, xterm...)

I'm also running bash on the remote system in an xterm window...

The problem is, I get:

rxterm annapurna
[1] 5444
leisner@hydrus$ 
[1]+  Stopped (tty input)     rsh $1 ./dologin "xterm -title $1 -display `hostname`:0 -e bash "


I tried redirecting stdout/stderr to /dev/null, but no luck...

The rsh is a job, which I can kill after it executes...

What I want is a system which backgrounds, and lets the rsh terminate cleanly...

Or is there a better way of doing what I'm trying to do?

--
marty
leisner.henr801c@xerox.com  leisner@eso.mc.xerox.com
Member of the League for Programming Freedom
Newsgroups: comp.unix.shell
From: etxmesa@eos.ericsson.se (Michael Salmon)
Subject: Re: Question concerning Xterm control sequences 
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB
Date: Tue, 15 Dec 1992 08:45:39 GMT

In article <Bz9HFK.HGu@fuhainf.fernuni-hagen.de>, ralf.weber@fernuni-hagen.de (Ralf Weber) writes:
|> Hello world,
|> 
|> is there anybody who can give me information on how i can get
|> the Xterm control sequences ?

The X11 R5 distribution contain a file called ctlseqs.ms that contains
all of xterms control sequences. This file needs to be formatted using
{n,t}roff and then printed.

-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm
Newsgroups: comp.unix.shell
From: dman@netcom.com (Dallman Ross)
Subject: Need quick-'n'-dirty syntax lesson in csh
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
X-Newsreader: TIN [version 1.1 PL8]
Date: Sun, 20 Dec 1992 23:06:14 GMT


I'm writing a tiny csh script, and I need to know how the syntax is
formed in an "if"-statement for:

	if <there is no argument3 ...>

I have the "then"- and "else"-parts down fine, just need the "if"
syntax.  I grepped through man csh with no real luck.

--
 __D_a l_l m a_n  _ R o_s s _ |dman@netcom.com  /or/  |"You sound like a man|
 l  \\ l\\   /l  /\\  l\\   l |dross@well.sf.ca.us    |with a rubber nose." |
 l   >)l \\ /ll /  \\ l \\  l |vox/fax: 1.510.645.1883| -- One-Lung Bill    |
 l  // l  \X ll/--- \\l  \\ l |350 Perkins St., #108  |     Remmer (deceased)
_l//______________________\\l_|Oakland,_CA__94610-3422|_____________________|_
Newsgroups: comp.unix.shell
From: dcb@kopachuk.uucp (David Breneman)
Subject: Re: Exiting KSH with ^D
Keywords: shell, ksh, kornshell, HP-UX
Organization: Tacoma Screw Products, Inc.
Date: Thu, 17 Dec 1992 22:33:04 GMT

In article <1992Dec9.184249.24657@cbfsb.cb.att.com> jpittas@cbnewsf.cb.att.com (john.pittas) writes:
>Lots of people have followed up on this saying that you need
>to set 'viraw' in order to exit ksh with control-d.  However,
>on both Sun machines and AT&T 3B2's I can exit ksh with ^D
>without a subsequent <return> and WITHOUT having viraw set.
>So, the original question is still valid: why is this behavior
>different with HP's ksh?
>

I don't have the answer, but I can tell you that HP isn't the only
offender.  Our AT&T 7020 (Pyramid MIS-02) does the same thing.  If
you want to log out you have to enter <CTRL> D  <RETURN>
If you just enter <CTRL> D  somebody can come along and press
<DELETE> and bring the terminal back up as you.  This is in the Sys V
universe.  Useful security feature. :-)  I now find myself using
<CTRL> D  <RETURN> even on the 3B2s just out of habit.

-- 
David Breneman     Sys Admin, Tacoma Screw Products, Inc. |  ____  ____  ____
dcb@tacoma.uucp           |   SCREWIE the TSP CLOWN sez-  |   /   /___  /___/ 
 ..!uunet!tacoma!dcb      | "Zinc & cadmium plating stops |  /   ____/ / 
CompuServe: <DEAD>        |  rust & acts as a lubricant!" |
Xref: sparky comp.unix.shell:5075 comp.unix.questions:14700
From: uwe@mpi-sb.mpg.de (Uwe Waldmann)
Newsgroups: comp.unix.shell,comp.unix.questions
Subject: Re: Substituting using sed, skipping quoted strings
Date: 15 Dec 92 14:29:07 GMT
Reply-To: uwe@mpi-sb.mpg.de
Followup-To: comp.unix.shell
Organization: Max-Planck-Institut fuer Informatik

In article <1992Dec14.042422.22897@candle.uucp>, root@candle.uucp
(Bruce Momjian) writes:
> Here is a sample file:
> 
> 	acaX csacacXcascsc  
> 	"cscaXcacsXcs"  csaXc "X" caX
> 	Xaca Xcaca  ca "caXcas"  ccaX cacs
> 
> I want to use sed to replace X with another character, but only if the X
> does not appear within quotes.  The quoted strings do not extend across
> new-lines.

That's easy:

#!/bin/sh
sed -e '
s/^/\
/
: a
s/\(\n[^"]*\)X/\1Y/
t a
/\n.*".*"/ {
s/\n\([^"]*\)"\([^"]*\)"/\1"\2"\
/
t a
}
s/\n//
' ${1+"$@"}

The extension to quoted strings that do extend across newlines is left
to the reader :-)

-- 
Uwe Waldmann, Max-Planck-Institut fuer Informatik
Im Stadtwald, D-W6600 Saarbruecken 1, Germany
Phone: +49 681 302-5431, Fax: +49 681 302-5401, E-Mail: uwe@mpi-sb.mpg.de
Newsgroups: comp.unix.shell,comp.unix.questions,comp.unix.admin
From: glover@credit.erin.utoronto.ca (Mike Glover)
Subject: Re: Need HELP with functions in SH shell programming!       
Organization: University of Toronto, Erindale Campus
Date: Sat, 19 Dec 1992 22:56:21 GMT

In article <1992Dec18.154617.14831@acd4.acd.com> greene@IEDV4.acd.com ( Jonathan Greene ) writes:
>Hi.  I've written a shell script for the SH shell, and would like
>to combine the the 2 places I have the same case statements into 
>into 1, by means of a function.
>
>The manual says a function is defined by:
>  
>name () {list;} where name is the name of the function and
>list is the list of commands you want the function to execute.
>
>When I execute the script, I get the error: '(' Unexpected.
>I also can't figure out the correct way to call the function. 
>

Try this little script and if it doesn't work mail me back (to save bandwidth)

========= 8<  cut here
#!/bin/sh
name() {
    echo hi
}
name

======

This,  when  run should echo hi.  If it works,  then take it from there. :)

ttfn,
	Mike

-- 
_______________________________________________________________________________
 ___                    "Mickey Mouse wears a timex watch."_ ???
 U|     		glover@credit.erin.utoronto.ca  (Mike Glover)
 C|S			University of Toronto Computing Services
From: kkress@phent.UUCP (Kenneth R. Kress)
Newsgroups: comp.unix.shell
Distribution: world
Subject: Re: Substituing using sed, ...
Keywords: sed awk substituting
Organization: That's Entertainment BBS
Date: Tue, 15 Dec 92 22:06:54 EST

Uwe Waldmann writes:
> In article <1992Dec14.042422.22897@candle.uucp>, root@candle.uucp
> (Bruce Momjian) writes:
> > Here is a sample file:
> > 
> > 	acaX csacacXcascsc  
> > 	"cscaXcacsXcs"  csaXc "X" caX
> > 	Xaca Xcaca  ca "caXcas"  ccaX cacs
> > 
> > I want to use sed to replace X with another character, but only if the X
> > does not appear within quotes.  The quoted strings do not extend across
> > new-lines.
> 
> That's easy:
> 
> #!/bin/sh
> sed -e '
> s/^/\
> /
> : a
> s/\(\n[^"]*\)X/\1Y/
> t a
> /\n.*".*"/ {
> s/\n\([^"]*\)"\([^"]*\)"/\1"\2"\
> /
> t a
> }
> s/\n//
> ' ${1+"$@"}
> 
Uwe Waldmann,
	I was unable to test your solution because my version of sed
gave me pattern overflow errors. And I was unable to decipher your
technique. But trying to understand it suggested several other
strategies.
	If Bruce Momjian doesn't mind deconstructing his original file,
one could do:
	tr -s ' ' '\n' datafile		|	# every word to a line
	sed 's/	//' 			|	# remove tabs
	sed '/^[^"]/s/X/Y/g' 			# if line has no quote
						# do the translation
	And this unsatisfactory solution led me to the solution I 
should have thought of first:
awk '
{	# do this for every line
	for (i = 1; i <= NF; i++) {		# loop through words on line
		if ( $i !~ /\"/) {		# not quoted
#			gsub (/X/,"Y",$i )	#   substitute Y for X
			printf ("%s", $i ) 	#   print out word
		} else {			# else
			printf ("%s", $i )	#   print out word
		}
	}					# line is done, so
	printf "\n"				# print newline
}'
	This requires nawk or gawk.
				Ken.
===================================================================
Ken Kress, Glenside, PA * dsinc!phent!kkress 
	Daring ideas are like chessmen moved forward;
	they may be beaten, but they may start a winning game.
					Johann Wolfgang von Goethe
-------------------------------------------------------------------
Newsgroups: comp.unix.shell
From: dattier@ddsw1.mcs.com (DWT)
Subject: ksh autoload quirk
Date: Wed, 16 Dec 1992 20:01:49 GMT
Organization: Contributor Account at ddsw1, Chicago, Illinois  60657

ksh 11/16/88d under Dell SVR4 4.0 here on ddsw1 and the ksh running on a 3B2
on gagme recognize any filename in a directory in $FPATH as an undefined
function whether or not that name has been declared for autoload with
"autoload" or "typeset -fu."

But there is a difference when a file in $FPATH has the same name as an
executable file in $PATH.  If the undefined function has been formally
declared with "autoload" or "typeset -fu," then ksh interprets an appearance
of that name on the command line as a reference to the function.  If the
undefined function has not been declared but is recognized as such solely by
dint of lying in $FPATH, then an appearance of the name on the command line
is taken by ksh parser to mean the executable in $PATH (unless the function
has actually been loaded with the . command or by a call to another function
in the same file to whose name the file is linked).

Is that the correct behavior?  Is a file name in $FPATH that hasn't been
declared for autoload supposed to be recognizable at all as an undefined
function?  I haven't seen anything about that (nor about a difference in
precedence from a declared undefined function) in the ferkakte manual.

David W. Tamkin   Box 59297   Northtown Station, Illinois  60659-0297
dattier@ddsw1.mcs.com    CompuServe: 73720,1570    MCI Mail: 426-1818
Newsgroups: comp.unix.shell
From: guenther@stolaf.edu (Philip A Guenther)
Subject: Re: rsh terminates while loop
Organization: Academic Computing Center, St. Olaf College
	<1992Dec15.054605.6780@cs.wisc.edu>
Date: 15 Dec 92 00:01:10

In article <1992Dec15.054605.6780@cs.wisc.edu> dws@ssec.wisc.edu (DaviD W. Sanderson) writes:
   Redirect the rsh input from /dev/null:
Or just use rsh -n.

Philip
--
guenther@stolaf.edu (Philip Guenther)       | The ACC might agree with me,
Student Sys Prog, Academic Computing Center | but with that bunch, (and me)
St Olaf College, Northfield, MN 55057-1001  | you never know... :-) :-| :-(
"Life makes sense?  LIFE MAKES SENSE!!?  Where do people get these ideas?"-me
Newsgroups: comp.unix.shell
From: anw@maths.nott.ac.uk (Dr A. N. Walker)
Subject: Re: Shell script poser
Reply-To: anw@maths.nott.ac.uk (Dr A. N. Walker)
Organization: Maths Dept., Nott'm Univ., UK.
Date: Mon, 14 Dec 1992 15:00:45 GMT

In article <724029721snx@trmphrst.demon.co.uk>
nikki@trmphrst.demon.co.uk writes:
>Here's a little shell-script problem for all you gurus out there ...
	[wants lines lower-cased and Capitalised]
>Can this be done using STANDARD UNIX COMMANDS ONLY (i.e. awk, tr, sed etc.)

	It's easy enough with "sed":

sed "
	y/ABCDEFGHIJKLMNOPQRSTUVWXYZ/abcdefghijklmnopqrstuvwxyz/
	/^[a-z]/ { h
		   y/abcdefghijklmnopqrstuvwxyz/ABCDEFGHIJKLMNOPQRSTUVWXYZ/
		   G
		   s/\(.\).*\n./\1/
		 }
" < filename

-- 
Andy Walker, Maths Dept., Nott'm Univ., UK.
anw@maths.nott.ac.uk
Newsgroups: comp.unix.shell
From: rick@digibd.digibd.com (Rick Richardson)
Subject: Re: Reading a line from a file in Bourne
Organization: DigiBoard, Incorporated, Eden Prairie,MN
Distribution: usa
Date: Tue, 15 Dec 1992 10:08:17 GMT

dlreed@highlite.uucp (David L. Reed) writes:

>The alternative that has worked best for me is to let while take
>stdin directly from the file:

>#!/bin/sh
>while read LINE
>do
> echo a full line: $LINE
>done < myfile

My favorite way is to use shell I/O redirection.  This method allows
one to set and keep the values of shell variables.  It works in all
versions of Bourne shell from XENIX to SVR3.2 to SVR4.0 to SVR4.2,
except that you have to have the latest SVR4.0 shell.  Early SVR4.0
Bourne shells introduced a bug where this code would hang the 2nd time it
is used.  Without the 'exec' malarky, a lot of Bourne shells will spawn
a subprocess to do the "done < myfile" part shown above.

# Example showing technique
exec 3<&0 0<myfile
count=0
while read LINE
do
	count=`expr count + 1`
done
exec 0<&3 3<&-
echo "$count lines"

--
Rick Richardson		Senior Staff Engineer	Investment advice for 1993-1996:
DigiBoard, Inc.		Email: rick@digibd.com	Go long on Arkansas chicken
6400 Flying Cloud Dr.	Fax:   (612) 943-0803	Go short on everything else
Eden Prarie, MN 55344	Tel:   (612) 943-5383	<standard disclaimer>
Newsgroups: comp.unix.shell
From: ray@Celestial.COM (Ray Jones)
Subject: Re: Reading a line from a file in Bourne
Organization: Celestial Software, Mercer Island, WA
Distribution: usa
Date: Tue, 15 Dec 1992 22:15:42 GMT

In <SHUTTON.92Dec11112920@fokker.union.indiana.edu> shutton@fokker.union.indiana.edu (Scott K. Hutton) writes:

>This is something that has eluded me  for a good while, but now I have
>to find out.  How can  you read lines (yes, entire lines) sequentially
>in from a file and store them in a variable.  For example:

>  for ITEM in `cat $FILENAME`
>    do echo a full line: $ITEM
>  done

>If you're given a file that contains:

>  Line one
>  Line two

>This script would output

>  a full line: Line
>  a full line: one
>  a full line: Line
>  a full line: two

>Any easy answers?
no
Scott,
Here is a code segment that does about what you want.  In this case there is
a file (a tab seperated, variable length field database) with the first line
Fname	Lname	Company	Source	phone
Note the changes of standard in from keyboard to file and back again.

   	exec 4<&0
	 rm -f p.tmp 
	grep -i $1 ${DATA} >p.tmp 
		if test $# -gt 1
		then
		grep -i $2 p.tmp>g.tmp;mv g.tmp p.tmp
		fi
	HEAD=`sed 1q ${DATA}`
	IFS="	"
	exec 3<p.tmp
	exec 0<&3
	read $HEAD 
	LINE=`echo $phone`
	while [ -n "$LINE" ]
	do
	echo "${CLEAR}
   Name:  $Fname $Lname 
Company:  $Company
Comment:  $Source
  Phone:  $phone"
 echo "Is this correct? (d to delete) \c"
	exec 0<&4

Hope this helps.
-- 
INTERNET:  ray@Celestial.COM   Ray A. Jones; Celestial Software
UUCP:   ...!thebes!camco!ray   6641 East Mercer Way
             uunet!camco!ray   Mercer Island, WA 98040; (206) 947-5591
The probability of one or more spelling errors in this missive approaches
From: tony.dunning@almac.co.uk (Tony Dunning)
Newsgroups: comp.unix.shell
Subject: script for changing file
Date: 14 Dec 92 02:21:00 GMT
Reply-To: tony.dunning@almac.co.uk (Tony Dunning)
Organization: Almac BBS Ltd. Scotland. +44 (0)324-665371

TO: newman@cptc1.neep.wisc.edu

DN>For example if the directory contained OUT1 OUT2 OUT3 and TEXT
DN>I could run the script rename OUT run1 and have it return
DN>OUT1run1 OUT2run1 OUT3run1 TEXT.

Try the following

script name eg scr1  , containing the following

find . -name "*$1*" -exec scr1sub {} \;

where scr1sub would read :

mv $1 $1$2

This would find all files in your directory & down from your directory



        Tonyd
---
 . OLX 2.2 . Unable to locate Coffee -- Operator Halted!
                  
Newsgroups: comp.unix.shell
From: shutton@fokker.union.indiana.edu (Scott K. Hutton)
Subject: Re: BASH history question
Organization: /nfs/bronze/usr2/shutton/.organization
Date: Mon, 14 Dec 1992 12:29:14 GMT

Larry Stern writes:

   I have been trying to set my history file size in BASH, with no success.
   I put 'set histfilesize=50' and designated the history file in my profile
   put this doesn't seem to do it.  What is the correct syntax?

export HISTFILESIZE=50
export HISTORY=50	#(or however much you want saved while on-line

Case sensitivity problem.

-S
Newsgroups: comp.unix.shell
From: shutton@fokker.union.indiana.edu (Scott K. Hutton)
Subject: Re: Reading a line from a file in Bourne
Organization: /nfs/bronze/usr2/shutton/.organization
Distribution: usa
Date: Sat, 12 Dec 1992 03:31:07 GMT

I've received a lot of good advice, both through e-mail and followups.
The bottom line (while I did receive lots of  innovative solutions) is
to do something akin to the following:

#!/bin/sh
cat myfile |
while read LINE
do
 echo a full line: $LINE
done

"read"  apparently has a  significant return value--major goof  on  my
part for failing to check this.

-S
Newsgroups: comp.unix.shell,comp.sys.sun.misc
From: jhawk@panix.com (John Hawkinson)
Subject: Zsh doesn't catch HUPs correctly under SunOS 4.1.3?
Date: Fri, 18 Dec 1992 23:04:23 GMT
Organization: PANIX Public Access Unix, NYC

With zsh2.2.0 under SunOS 4.1.3:

if there's a hangup while something has been run from zsh,
then the process that's being run gets killed, but the zsh
process hangs around.
If there's a hangup when the shell is idle, everything's
kosher.

Bug?

Thanks.

--
John Hawkinson
jhawk@panix.com
Newsgroups: comp.unix.shell
From: davew@sol.rtsg.mot.com (Dave Weigand)
Subject: Re: Windowing Korn SHell
Reply-To: davew@jdc.gss.mot.com
Organization: Motorola Digital Cellular
Distribution: usa
Date: Tue, 15 Dec 1992 17:08:03 GMT

In article <1992Dec14.144500.25697@rtsg.mot.com>, yorton@turtle11.rtsg.mot.com (James J. Yorton) writes:
|> In article <1992Dec09.151213.14304@spike.insci.com>, brad@spike.insci.com (Brad Segal) writes:
|> |> Hi,
|> |>   I'm interested in finding out more about the Windowing Korn Shell 
|> |> (WKSH, I think) that provides the ability to write X applications in ksh.
|> |> I know some company in NJ markets it but I'm not sure
|> |> of the name. What platforms are supported? Any info would be greatly
|> |> appreciated. Thanks... please send e-mail.
|> 
|> We got our information on it from the AT&T Toolchest in New Jersey.
|> Their (voice) phone number is (908) 522-6698.
|> 


From what the name Windowing Korn Shell implies you can actually write ksh applications
that conform to the X11 protocol - is this correct.  If so are they making Xlib
calls or using another interface?  


-Dave

--
+-------------------------------------------------------------------------+
| Dave Weigand                       | Internet:  davew@jdc.gss.mot.com   |
| Senior Electrical Engineer         |     or if you must ...             |
| Japan Digital Cellular             | UUCP:      uunet!motcid!weigand    |
| Motorola, Inc.                     | Voice:     (708) 632-2248          |
|-------------------------------------------------------------------------|
| #include  <std_disclaimer>                                              |
|  all opinions are mine alone and not those of my employer!!             |
+-------------------------------------------------------------------------+
Newsgroups: comp.unix.shell