According to Eric Crump: > Thanks Gilles! Apparently those pesky extra spaces after several of the > backslashes were the cause of the problem. I woulda never thought of that! I think you'd be hard-pressed to find any Unix-based tool in which a space after a backslash didn't prevent that backslash from being used as a continuation character. E.g., in the shell, echo xxx\<newline> yyy would echo "xxx yyy", but echo xxx\<space><newline> would echo "xxx ". In general, the backslash changes the meaning of the character immediately following it. If the newline character does not immediately follow the backslash, then you haven't changed its meaning, and in the context of a configuration file, a newline marks the end of an attribute definition. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 ------------------------------------ To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
