From: Eli Zaretskii <eliz@gnu.org>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [python] [patch] set/show extended-prompt
Date: Thu, 11 Aug 2011 18:22:00 -0000 [thread overview]
Message-ID: <83aabfyfjb.fsf@gnu.org> (raw)
In-Reply-To: <m31uwrnat0.fsf@redhat.com>
> From: Phil Muldoon <pmuldoon@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Thu, 11 Aug 2011 17:59:55 +0100
>
> >> +@smallexample
> >> +substitute_prompt (``frame: \f, print arguments: \p@{print frame-arguments@}'')
> >> +@end smallexample
> >
> > The line inside @example should be broken into two, as it is too long.
>
> I'm never sure how to break up function examples like these for the
> documentation (other than making a smaller example).
Just divide it into 2 lines, and if you want to make sure the reader
doesn't perceive the line break as significant, say something like
"this is one long line" in parentheses.
> Any suggestions on where to include the break?
It is not important, other than keeping each line shorter than 64
characters.
> >> +``frame: main, print arguments: scalars''
> >> +@end smallexample
> >
> > Aren't these ``..'' quotes left verbatim in the printed version of the
> > manual? I think you need literal ".." quotes here, since they are not
> > converted inside @smallexample.
>
> Yes, you are right. I relied on the emacs Texinfo major mode to do the
> right thing here, but I guess it does not in the context of
> @smallexample.
Texinfo mode only does the opposite: inserts ``..'' when you type
"..".
> When you mean literal quotes, do you mean just pasting in '"'?
Yes.
next prev parent reply other threads:[~2011-08-11 18:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 15:07 Phil Muldoon
2011-08-11 16:21 ` Eli Zaretskii
2011-08-11 18:01 ` Phil Muldoon
2011-08-11 18:22 ` Eli Zaretskii [this message]
2011-08-11 21:42 ` Matt Rice
2011-08-12 14:51 ` Phil Muldoon
2011-08-12 15:40 ` Phil Muldoon
2011-08-12 20:22 ` Tom Tromey
2011-08-12 22:20 ` Phil Muldoon
2011-08-13 6:27 ` Eli Zaretskii
2011-08-15 14:03 ` Phil Muldoon
2011-08-15 16:58 ` Eli Zaretskii
2011-08-16 11:22 ` Phil Muldoon
2011-08-16 13:39 ` Eli Zaretskii
2011-08-17 11:02 ` Phil Muldoon
2011-08-15 17:51 ` Tom Tromey
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=83aabfyfjb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@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