From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: in sphinx docs, what is "@b barebox" markup supposed to do?
Date: Mon, 30 Jun 2014 08:50:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406300846400.3759@localhost> (raw)
In-Reply-To: <CAOpc7mGu=VYE_9uRJ8-dKmDaqgQaok40u_2EFgSHQCRG=67oXQ@mail.gmail.com>
On Mon, 30 Jun 2014, Holger Schurig wrote:
> I found a Sphinx cheat sheet:
> http://openalea.gforge.inria.fr/doc/openalea/doc/_build/html/source/sphinx/rest_syntax.html
> (where you have all the important things on just one page).
>
> So you can convert "This is @b foo bar" to "This is **foo** bar".
hmmmmm ... a handy page but i'm puzzled by one of the first things
listed there; that is, that double backquotes are used to make a text
"verbatim". it also appears to render it in courier, which is what i
use to represent things like commands, filenames, etc.
other than that, that's a nice cheat sheet, thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-06-30 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 13:06 in sphinx docs, what is "@b barebox" markup supposed to do? Robert P. J. Day
2014-06-30 6:01 ` Sascha Hauer
2014-06-30 9:38 ` Holger Schurig
2014-06-30 9:56 ` Robert P. J. Day
2014-06-30 12:56 ` Sascha Hauer
2014-06-30 12:50 ` Robert P. J. Day [this message]
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=alpine.LFD.2.11.1406300846400.3759@localhost \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.