From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii To: Don Howard Cc: gdb-patches@sources.redhat.com Subject: Re: Doc update Date: Wed, 31 Oct 2001 04:00:00 -0000 Message-id: References: X-SW-Source: 2001-10/msg00386.html On Tue, 30 Oct 2001, Don Howard wrote: > 2001-10-30 Don Howard > > * gdb.texinfo: Added documentation for the behavior of gdb with > input redirected from a file. Thanks! This is approved, with the following comments: > +@value{GDBN} also accepts command input from stdin. In this mode, > +normal output goes to stdout and error output goes to stderr. Errors in > +a command file supplied on stdin do not terminate execution of the > +command file -- execution continues with the next command. The words "stdin", "stdout", and "stderr" should have a @code markup, since they are C symbols. In fact, it might be better to replace them with "standard input" etc., since GDB is used for debugging languages other than C, so a user might not know what `stdin' is. > +@example > +gdb < cmds > log 2>&1 > +@end example > + > +(The syntax above will vary depending on the shell used) This example A period is missing inside the parens. > +will execute commands from the file @var{cmds}. All output and errors > +would be directed to @var{log}. In this case, `cmds' and `log' are not metasyntactic variables, they are simple file names. So they should have the @file markup. Oh, and in the ChangeLog entry, please tell in what node was the change done, as if the node were a function (i.e. inside parens).