On Tue, 2004-06-15 at 01:06, Ken Wallis wrote: > Karl Pearson wrote: > > > Try putting two \\ so the escape will be used as it was meant > > to be, to > > keep special characters from being treated like special characters. > > > > I.e. \* \? \\ etc. > > The difficulty is in doing this. Once the shell has the value with the '\' > in it, it becomes very hard to manipulate it. > > You might get away with doing a 'tr' or a 'sed' in between the 'find ... > -print' and the 'while read', but you'd have to be very clever with the > escaping of your escapes in the sed script or the tr strings. >
One other option on Unix is the difference between " and ' quotes. To force an absolute, use 'TRAN.EXT-14320S1??\4-DF' rather than "...". Unix allows special characters and variables to be 'checked' withint double quotes, but uses strict string representation within single quotes. Karl > Cheers, > > Ken > > > LeRoi Keiller wrote: > > >> Cutdown example of what I'm trying to do (ksh): > >> > >> $ ls TRAN* > >> TRAN.EXT-14320S1??\4-DF > >> TRAN.EXT-14320S1??\5-DF > >> (note the '\' in the file names) > >> $ find TRAN* -print | while read file > >> do > >> ls -l $file" > >> done > >> TRAN.EXT-14320S1??4-DF not found ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
