Re: [PATCH, doc RFA] New feature: extension language post-initializers

[Eli Zaretskii <eliz at gnu dot org>]

> Date: Sun, 09 Aug 2015 18:50:31 +0000
> From: Doug Evans <dje@google.com>
> 
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -3,6 +3,11 @@
> 
>   *** Changes since GDB 7.10
> 
> +* Python Scripting
> +
> +  ** Python code can now be run after -ix/-iex processing and before any
> +     program is loaded by appending functions to gdb.post_initializers.
> +
>   * Support for tracepoints on aarch64-linux was added in GDBserver.

OK.

> +@node Startup Post-Initialization
> +@subsubsection Startup Post-Initialization
> +@cindex running python at the end of GDB startup
                                        ^^^
@value{GDBN}

> +@value{GDBN} provides a way to run Python code at the end of startup,
> +after @code{-iex}, @code{-ix}, and @code{-cd} option processing,
> +and before it loads any specified program.
> +Such initialization may depend on various startup options thus we want
> +to defer it until after all such options are processed.

"thus we want" sounds strange in this context.  How about the
following alternative:

  Such initialization may depend on various startup options, so
  @value{GDBN} invokes them after all such options are processed.

The documentation parts are OK with those fixed.

Thanks.