Re: RFC: add ability to "source" Python code

[Joel Brobecker <brobecker@adacore.com>]

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

> >     gdb/doc/ChangeLog:
> >     
> >             Tom Tromey  <tromey@redhat.com>
> >             * gdb.texinfo (File Options): Document -x on .py files.
> >             (Command Files): Document handling of Python scripts.
> 
> Okay for this part, except that:

Ooops, sorry - I was confused as to the status of the documentation.
Somehow, I managed to understand that your approval of the change
included the approval of the documentation update. I apologize.

I checked in this patch, to fix the issue you spotted.

2010-01-19  Joel Brobecker  <brobecker@adacore.com>

        * gdb.texinfo (Command Files): Fix typo.

-- 
Joel

[-- Attachment #2: gdb.texinfo.diff --]
[-- Type: text/x-diff, Size: 745 bytes --]

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.660
diff -u -p -r1.660 gdb.texinfo
--- gdb.texinfo	18 Jan 2010 06:28:47 -0000	1.660
+++ gdb.texinfo	19 Jan 2010 10:27:39 -0000
@@ -19164,7 +19164,7 @@ each command as it is executed.  The opt
 
 If @var{filename} ends in @samp{.py}, then @value{GDBN} evaluates the
 contents of the file as Python code.  If Python support is not compiled
-in to @value{GDBN}, then the file is assumed to contain @value{GDBN}
+into @value{GDBN}, then the file is assumed to contain @value{GDBN}
 commands, regardless of its extension.
 
 Commands that would ask for confirmation if used interactively proceed