Re: [doc, committed] invoke.texi markup fixes

2015-01-25 Thread Gerald Pfeifer
On Monday 2015-01-05 19:37, Sandra Loosemore wrote: (I'm actually surprised that anybody even bothered to look at the patch If the doc maintainers would prefer me to post these kinds of copy-editing changes for review rather than just commit them, please let me know.) I am fine, in fact hap

Re: [doc, committed] invoke.texi markup fixes

2015-01-05 Thread Sandra Loosemore
On 01/05/2015 03:57 PM, Joseph Myers wrote: On Mon, 5 Jan 2015, Sandra Loosemore wrote: @file is used for file names. For standard headers, the use of @code{} (inttypes.h and limits.h, in this patch) is deliberate, reflecting that the C standard does not require headers to correspond to files

Re: [doc, committed] invoke.texi markup fixes

2015-01-05 Thread Joseph Myers
On Mon, 5 Jan 2015, Sandra Loosemore wrote: > @file is used for file names. For standard headers, the use of @code{} (inttypes.h and limits.h, in this patch) is deliberate, reflecting that the C standard does not require headers to correspond to files and that the use of files to implement tho

[doc, committed] invoke.texi markup fixes

2015-01-05 Thread Sandra Loosemore
This is another one of my boring tech-writer-ish patches to the GCC user documentation. I noticed that there were numerous places in invoke.texi using @code markup instead of the more specific @option, @file, or @command markup, or in contexts where most other places in the manual use @samp.