Re: [PATCH 2/2] doc: Improve documentation about MI thread output

[Simon Marchi <simon.marchi@ericsson.com>]

On 17-04-12 04:35 PM, Eli Zaretskii wrote:
> IME, defensive programming aside, knowing that some field could or
> could not appear is not always enough, sometimes you also need to
> understand the semantics and the significance of whether it does or
> doesn't, because you might need to interpret that in some way, e.g. to
> present some meaningful message to a human user.

I agree that a clarification would be helpful to understand to make sense
of the description.  I just don't want it to be interpreted as a formal
specification of when the field appears.  That's why I'm not comfortable
with a claim such as "the field will always be present when X and Y".

What do you think of?

@item current-thread-id
The global id of the currently selected thread.  This field is omitted if there
is no selected thread (for example, when the selected inferior is not running,
and therefore has no threads) or if a @var{thread-id} argument was passed to
the command.

> That said, I'm not going to argue.  It's up to you.

Thanks,

Simon