Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [mi, doc] mention escape sequences
Date: Thu, 12 Jun 2008 16:37:00 -0000	[thread overview]
Message-ID: <200806120905.08861.vladimir@codesourcery.com> (raw)
In-Reply-To: <u3anjkd01.fsf@gnu.org>

On Wednesday 11 June 2008 23:06:22 Eli Zaretskii wrote:
> > From: Vladimir Prus <vladimir@codesourcery.com>
> > Date: Wed, 11 Jun 2008 18:07:25 +0400
> > 
> > Note that parse_escape function supports more than C language escape
> > sequences, it seems, but given that the function has no comments on
> > those sequences, and given that manual does not say anything about
> > that either, I don't feel like reverse-engineering the code to
> > document the exact rules. "As in C" as sufficient, I think, for MI
> > manual.
> 
> Maybe not all exact rules, but a single example would be good, I
> think.  After all ``escape sequences'' is a heavily overloaded term,
> even with the "C" qualifier, and without an example, the reader might
> be left in doubt.

Okay, which texinfo markup should I wrap "\r" in?

> 
> > Escape sequences are not allowed in @var{non-blank-sequence}.
> 
> How do you mean ``not allowed''?  Perhaps you mean ``not
> interpreted'', i.e. output verbatim?

Right; I'll adjust the text accordingly.

- Volodya


  reply	other threads:[~2008-06-12  5:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 19:06 Vladimir Prus
2008-06-11 22:36 ` Eli Zaretskii
2008-06-12 16:37   ` Vladimir Prus [this message]
2008-06-12 23:24     ` Eli Zaretskii

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=200806120905.08861.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /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