× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



RSE probably doesn't have a pattern for "grep -l" but you could try "grep 
-n" - in that case you should be able to jump to not only the file but the 
line of text within the file in the editor.

____________________________________
David McKnight 
Phone:   905-413-3902 , T/L:  969-3902
Internet: dmcknigh@xxxxxxxxxx
Mail:       D1/619/8200/TOR
____________________________________




Chris <didjit86@xxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
20/03/2006 09:06 AM
Please respond to
Websphere Development Studio Client for iSeries 


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Shell File Grep Open Problem






I got all the PTF's install on our system so I can use the shell from 
WDSCI.
I love that I can launch editors directly from listed files. But, I ran 
into
this problem.

If I grep for contents of a file. IE. "grep -l "mytext" MyFiles*"  I will
get a listing of MyFiles* that contain mytext. However, I cannot launch an
editor from the displayed list of files from grep. But if I cut/paste one 
of
the files and do "ls MyFile*".  I can then launch an editor on the 
displayed
files (which are the same as the grep results). Seems bulky, I should be
able to launch an editor directly from the Grep results. Is this a bug or
just the way its supposed to work? Using WDSCI Lite.

Tx

Chris

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.