Just an aside ... I've found GET(ARG.) to be unreliable. I used it in an application where it consistently returned args from the *previous* command instead of the current one under the following circumstances:
- previous command is something like SORT KR.BP = "KDB]" - current command is something like TBASIC KR.BP KDB (O - TBASIC is a locally catalogued program I was on UV 9.4 or 9.6 on HP-UX at the time. I finally said the heck with it and parsed @SENTENCE directly. -Keith ----Original Message---- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacques G. Sent: Tuesday, December 06, 2005 6:44 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] -D command line switch? >> Well, today I wanted to use -D as an argument but >> discovered that somehow my >> screen output was suppressed. Anyway, after a bunch of fooling >> around, I discovered that -D, D, -P and P on the command line will >> suppress output to the screen, and send it to the default printer >> instead! Also, GET(ARG.) does >> not see the argument either. > > These are standard switches. I usually use them with > (D or (P though. If you really want to use -D and > -P, it might work if you parse SENTENCE() or @SENTENCE > to get your command line arguments instead of using > GET(ARG.) Or use a different letter. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
