On Wed, 2001-12-19 at 21:12, Joe Pluta wrote: > > From: Martin Rowe > > > > Odd - it worked for me (tm) > > Do you consider creating a file with an asterisk in the name as "working"? > I'm honestly curious. I'm not a Unix savant, so I don't know whether that's > "good" behavior or "bad" behavior. In any case, I'm using bash 1.14, > fileutils 4.0, and it says "no match". Hi Joe By worked, I meant that the command created an empty file, rather than fail. Whether that's good behaviour or not I couldn't say ;-) Being able to escape (precede with a backslash \ ) troublesome characters like * and ? does help though (haven't tried this in QShell yet). As far as bad names on the IFS go, I managed to end up with a file with a leading x'22' (that's right - highlight in EBCDIC) which even WRKLNK wouldn't remove. I think it ignored the leading 'space' as it saw it and said the file didn't exist. Windows couldn't touch (no pun intended) it either. In the end I had to write a program to do the RMVLNK, so it could include the x'22'. Regards, Martin -- firstname.lastname@example.org email@example.com http://www.dbg400.net /"\ DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ / Source free test environment tools and others (file/spool/misc) X [this space for hire] ASCII Ribbon Campaign against HTML mail & news / \
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.