Ronald, >Larry F. Allen-Tonar wrote: >> In the one-liner dialog window, try typing in: >> >> perl -w -e 'print "It truly works.\\n";' >> The 'idea' of one-liners is to be able to type in the same obnoxiously-quoted >> and back-slash-doubled PERL one-line command needed for a UNIX shell >> and have it executed similarly by MacPerl. >But in a Unix shell I would have typed: > >perl -w -e 'print "It truly works.\n";' > >without the extra backslash before the 'n'. Why do you say that the >backslashes need to be doubled?? If it's not a bug in MacPerl, it's at >least rather counter-intuitive. (The above line doesn't give any output at >all when run from the OneLiner dialog.) Without doubling the backslash, AppleScript silently fails to properly parse the line, as far as I can tell. The need to double-up backslashes is obnoxious. Probably this should be considered a defect. The problem is in a MacPerl script which is distributed and modifiable ( ...:MacPerl Scripts:One Liner/1 ) ... anybody who is so inclined might figure out how to properly handle backslashes so they are correctly presented to AppleScript (within and not within a single-quoted and/or double-quoted argument). (Sorry, this is not on my list of things to do.) -- Regards, Larry F. Allen-Tonar (larryat@cts.com) +1 760/746-6464 (voice) Principal Designer +1 760/746-0766 (FAX, P.O. Box 463072 upon request) Escondido, CA 92046-3072 ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch