Re: [PATCH v2 16/16] Document pseudo-terminal and interrupting changes

[Pedro Alves <pedro@palves.net>]

On 2021-06-16 1:15 p.m., Eli Zaretskii wrote:
>>>> +@value{GDBN} on MS-Windows supports @kbd{C-@key{BREAK}} as an
>>>> +alternative interrupt key sequence.  @xref{interrupt debuggee on
>>>> +MS-Windows}.
>>> I'm not sure I understand the significance of this note: after all, a
>>> Windows program can install a Ctrl-BREAK handler exactly like it does
>>> with Ctrl-C.  Is this only about SetConsoleMode?
>> I was creating a new "Interrupting" node in the manual, so I thought it
>> was a good place to put cross references to other places in the manual
>> that talk about interruption.  That's all this is.  Just like the
>> reference to the remote debug section.
> My point was more general: why are we taking such a great care
> publishing the Ctrl-BREAK support?  What's the big deal?
> 

The text that I was xrefing reads:

 @cindex Ctrl-BREAK, MS-Windows
 @cindex interrupt debuggee on MS-Windows
 @anchor{interrupt debuggee on MS-Windows}
 MS-Windows programs that call @code{SetConsoleMode} to switch off the
 special meaning of the @samp{Ctrl-C} keystroke cannot be interrupted
 by typing @kbd{C-c}.  For this reason, @value{GDBN} on MS-Windows
 supports @kbd{C-@key{BREAK}} as an alternative interrupt key
 sequence, which can be used to interrupt the debuggee even if it
 ignores @kbd{C-c}.

And the sentence I wrote was just my attempt to summarize this information
so that the xref made any sense.  How would you go about this?  

- Say something different in the xref?  What?

- Remove the xref completely?  

- Move the whole text to the new Interrupt section (removing it from its original place)?

Thanks,
Pedro Alves