Aengus Lawlor wrote:
> Is there a way to get Analog to dumpt the lines it doesn't recognize
> into a file, so that I can analyze them to figure out what the problem
> might be?
Well, analog will output all the bad lines to STDERR. And, (as I learned
earlier today) this can be logged to a file on Windows NT, Borne or Korn
shell by using
analog 2> analog.log
Of course, this will include all of the rest of analog's warnings and
errors, and each line will be prepended by a C:, but they'll be there. You
could also write a scrip to process this log if you needed just those
lines (for instance, only read lines beginning with C:, or something).
HTH
--
Jeremy Wadsack
OutQuest Magazine
a Wadsack-Allen publication
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------