Tony Mechelynck wrote:
> echo string1 > file
> echo string2 >> file
> echo string3 >> file
> etc.
>
> ought to work, _except_ when the string is (ignoring case) ON OFF or
> empty (in which case you will set, clear or display the echo on/off
> setting instead of writing / appending to the file). People were using
> it in batch files in Dos from time immemorial, with shells which didn't
> know about inline documents.
You are apparently reading documentation. Does it also say something
about having > and < characters in the string? That may be the cause of
the problem:
@echo ^<?xml version="1.0" encoding="UTF-8" standalone="yes"?^> >$@
@echo ^<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0"^> >>$@
The ^ character is apparently used to escape the special meaning of >
and <.
--
ARTHUR: I did say sorry about the `old woman,' but from the behind you
looked--
DENNIS: What I object to is you automatically treat me like an inferior!
ARTHUR: Well, I AM king...
The Quest for the Holy Grail (Monty Python)
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
