HP3000-L Archives

August 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Joseph Norris <[log in to unmask]>
Reply To:
Joseph Norris <[log in to unmask]>
Date:
Thu, 5 Aug 1999 14:59:14 -0700
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (35 lines)
Why not get into the Posix shell and use grep. I use it all of the time
and it works jus fine.

#Joseph Norris (Perl - what else is there?/HP3000/Linux/CGI/Msql)
print @c=map chr $_+100,(6,17,15,16,-68,-3,10,11,16,4,1,14,-68,12,1,14,8,
-68,4,-3,-1,7,1,14,-68,-26,11,15,1,12,4,-68,-22,11,14,14,5,15,-90);


On Thu, 5 Aug 1999, Glenn Cole wrote:

Giridhar writes:

> Is there any command in MPEX that can search the given string
> ..................in "USE" program of the code. ?
> I am aware that this can be done in QE with $use option. I need similar
> MPEX command.

MPEX does not have this feature built in, BUT...

If the reason you want it in MPEX is just so you can search a fileset,
then you can just call Qedit from MPEX!  The output from this is a bit
of a pain to parse, but it works.

For example:
        % qedit @.job, list $use "customer-m" (up)

See     %help qedit
for more info.

(Note:  If "%qedit" fails, it may be because a UDC command of this name
        exists.  I normally get around this by copying qedit.cmd22.vesoft
        to qeditv in a group somewhere in my path, then using %qeditv .)

--Glenn

ATOM RSS1 RSS2