Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!umix!nancy!eecae!fmsrl7!mibte!gamma!ulysses!terminus!rolls!mtuxo!mtgzz!avr
From: avr@mtgzz.UUCP (XMRP50000[jcm]-a.v.reed)
Newsgroups: comp.unix.wizards
Subject: Re: Ksh use (was Re: Should ``csh'' be part of ...)
Summary: job control in ksh
Message-ID: <4109@mtgzz.UUCP>
Date: 19 May 88 17:30:08 GMT
References: <2599@usceast.UUCP> <2601@usceast.UUCP> <4095@mtgzz.UUCP> <11747@duke.cs.duke.edu>
Organization: AT&T, Middletown NJ
Lines: 23

In article <11747@duke.cs.duke.edu>, ndd@duke.cs.duke.edu (Ned Danieley) writes:
< As long as we're talking about ksh, is there any way to do job
< control without typing fg (and bg)? In csh
< 
< %2
< 
< brings the second stopped job into the foreground; as I understand it,
< in ksh I have to do
< 
< fg %2
< 
< A minor nit, but when you have 7 or 8 years invested in one shell,
< the change-over has to be very smooth, or it won't be made.

Just put the following in the ksh $ENV file of every user who wants it:

function argfg	{ fg %$1
		}
for jobnum in 0 1 2 3 4 5 6 7 8 9 # as many as you allow per user
	do alias -x %$jobnum="argfg $jobnum"; done

I do believe that's smooth enough....
					Adam Reed (mtgzz!avr)