public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tamar Christina <tnfchris@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-2011] docs: replace backslashchar [PR 110329].
Date: Wed, 21 Jun 2023 09:35:03 +0000 (GMT)	[thread overview]
Message-ID: <20230621093503.3FB8F3858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:b8b19729e65c79d5b9399591d19e8724b52347f9

commit r14-2011-gb8b19729e65c79d5b9399591d19e8724b52347f9
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Wed Jun 21 10:34:54 2023 +0100

    docs: replace backslashchar [PR 110329].
    
    It seems like @blackslashchar{} is a relatively new addition
    to texinfo.  Other parts of the docs use @samp{\} so use it
    here too so older distros work.
    
    gcc/ChangeLog:
    
            PR other/110329
            * doc/md.texi: Replace backslashchar.

Diff:
---
 gcc/doc/md.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index 052375b1a31..9648fdc846a 100644
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -837,7 +837,7 @@ blocks on the line.
 @item
 Within an @samp{@{@@} block, any iterators that do not get expanded will result
 in an error.  If for some reason it is required to have @code{<} or @code{>} in
-the output then these must be escaped using @backslashchar{}.
+the output then these must be escaped using @samp{\}.
 
 @item
 It is possible to use the @samp{attrs} list to specify some attributes and to

                 reply	other threads:[~2023-06-21  9:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230621093503.3FB8F3858D28@sourceware.org \
    --to=tnfchris@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).