<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 29, 2015 at 3:38 PM, Matt Kassawara <span dir="ltr"><<a href="mailto:mkassawara@gmail.com" target="_blank">mkassawara@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I just use "Blah blah blah::" in the networking guide and it seems to handle both config files and CLI.</div><div class=""><div class="h5"><div class="gmail_extra"><br></div></div></div></blockquote><div><br></div><div>Interesting data point Matt, and observation Karen. </div><div><br></div><div>So, what she's pointing out can be seen by looking at <a href="http://docs.openstack.org/networking-guide/misc_libvirt.html">http://docs.openstack.org/networking-guide/misc_libvirt.html</a></div><div>and then looking at the RST source:</div><div><a href="https://raw.githubusercontent.com/openstack/openstack-manuals/master/doc/networking-guide/source/misc_libvirt.rst">https://raw.githubusercontent.com/openstack/openstack-manuals/master/doc/networking-guide/source/misc_libvirt.rst</a><br></div><div><br></div><div>She's asking, why does # virsh net list not have italics but #virsh net net-destroy default is not italicized? Both use the :: convention in the prior paragraph. That's where we may need another convention to use ..code-block:: console throughout books like the Networking Guide. </div><div><br></div><div>What do you think, change conventions to use the ..code-block:: console for those guides?</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5"><div class="gmail_extra"><div class="gmail_quote">On Mon, Jun 29, 2015 at 2:33 PM, Gauvain Pocentek <span dir="ltr"><<a href="mailto:gauvain.pocentek@objectif-libre.com" target="_blank">gauvain.pocentek@objectif-libre.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>Le 2015-06-29 22:12, Karen Bradshaw a écrit :<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi. I have been looking into the use of :: vs .. code-block::<br>
in the newly converted RST guides. I have found some inconsistencies. <br>
I found that using a root-privileged python executable with the pound sign, gets<br>
<br>
formatted like a python comment (italicized). <br>
If there is output shown after the command<br>
then the cmd and output are not italicized but treated as literal<br>
text; the single colon directive is used in this case. <br>
Using the dollar prompt, everything works as expected (not italicized).<br>
We use the literal block directive, double colon, throughout the RST guides.<br>
One way I found to get around this is to always use the dollar prompt.<br>
Another way is .. code-block::java. It is a hack, but it generates the correct<br>
output for the pound sign <python cmd>.<br>
May be someone can shed some light on this problem.<br>
</blockquote>
<br></div></div>
You probably want to use '.. code-block:: console' for interactive shell sessions (a prompt and a command followed by its output). This will show a different color for the prompt and for shell builtin commands.<br>
<br>
If I'm not mistaken :: always uses python syntax highlighting (so italic after a # sign is normal behavior), unless you specified another lexer to use in your document.<br>
<br>
Gauvain Pocentek<br>
<br>
Objectif Libre - Infrastructure et Formations Linux<br>
<a href="http://www.objectif-libre.com" rel="noreferrer" target="_blank">http://www.objectif-libre.com</a><br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Anne Gentle</div><div>Rackspace</div><div>Principal Engineer</div><div><a href="http://www.justwriteclick.com" target="_blank">www.justwriteclick.com</a></div></div></div>
</div></div>