The code I suggested in post #4 in this thread can be typed directly into ksh at any primary prompt or put into a file and use ksh to execute that file. No \; is required under any circumstances for the for loop I suggested. You could join the 3 lines into a single line if you put just a ; at the end of the 1st 2 lines; but I MUCH prefer to see the structure any of code I'm running instead of trying to cram it all into a single unreadable line. I did have a typo in the first line:

Code:

for dir in $(find . -type d -name 'file*')

should have been:

Code:

for dir in $(find . -type d -name 'prog*')

but that would cause a different (possibly empty) set of directories to be searched; it shouldn't cause a secondary prompt to be issued.

Unless you added or removed some quotes, there is no reason why the code I suggested would issue a secondary prompt waiting for further input. Please show us EXACTLY (in CODE tags) what you typed into ksh.

For the code you asked about:

Code:

find . -type d -name prog\* -print -exec ls -la {} \; | /usr/xpg4/bin/grep -Ei '/|\.txt|\.PRG'

what are you hoping to match with the first of the three alternatives in the ERE you're passing to grep?