<div dir="ltr">I would like to keep these changes on hold as I am writing a parser which parses these code-blocks to BASH for automating testing of install guides. Could we hold on to the current structure for a couple of weeks? As I have to edit/change a few things in install guides too for the same.<div><br></div><div>Pranav</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 6, 2016 at 8:36 AM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2016-07-06 00:05, Lana Brindley wrote:<br>
> Ah, this looks great!<br>
><br>
> Andreas: how easy is it to install this extension? Will it break things?<br>
<br>
</span>Installation:<br>
<br>
It needs to be added to global-requirements, to local test-requirements<br>
for each repo and to each conf.py.<br>
<br>
So, small changes - but lots of them...<br>
<br>
And then RST files need to use it.<br>
<br>
Andreas<br>
<div><div class="h5"><br>
><br>
> Lana<br>
><br>
> On 06/07/16 05:26, Ronald Bradford wrote:<br>
>> I tested the demo and highlighting of code conveniently excludes prompts (achieved via css syntax).<br>
>> It is certainly a plus to be able to cut/paste code blocks more easily.<br>
>><br>
>> +1<br>
>><br>
>> Ronald Bradford<br>
>><br>
>> Web Site: <a href="http://ronaldbradford.com" rel="noreferrer" target="_blank">http://ronaldbradford.com</a> <<a href="http://ronaldbradford.com/" rel="noreferrer" target="_blank">http://ronaldbradford.com/</a>><br>
>> LinkedIn: <a href="http://www.linkedin.com/in/ronaldbradford" rel="noreferrer" target="_blank">http://www.linkedin.com/in/ronaldbradford</a><br>
>> Twitter: @RonaldBradford <<a href="http://twitter.com/ronaldbradford" rel="noreferrer" target="_blank">http://twitter.com/ronaldbradford</a>><br>
>> Skype: RonaldBradford<br>
>> GTalk: Ronald.Bradford<br>
>> IRC: rbradfor<br>
>><br>
>><br>
>> On Tue, Jul 5, 2016 at 4:43 AM, Adrien Cunin <<a href="mailto:adrien@adriencunin.fr">adrien@adriencunin.fr</a> <mailto:<a href="mailto:adrien@adriencunin.fr">adrien@adriencunin.fr</a>>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> From what I can see we usually use<br>
>><br>
>> .. code-block:: console<br>
>><br>
>> or<br>
>><br>
>> .. code-block:: shell-session<br>
>><br>
>> (which actually are the same)<br>
>><br>
>> to show commands that are to be executed by the user such as<br>
>><br>
>> # apt-get install foo<br>
>> # echo 1 > bar<br>
>><br>
>> The main issue, and the reason I started looking into this, is that the<br>
>> html output doesn't make it easy to select commands (for copy/pasting<br>
>> typically) without the prompt.<br>
>><br>
>> Turns out there is a Sphinx extension to do just this:<br>
>> <a href="https://github.com/sbrunner/sphinx-prompt" rel="noreferrer" target="_blank">https://github.com/sbrunner/sphinx-prompt</a><br>
>><br>
>> With this extension, the following<br>
>><br>
>> .. prompt:: bash #<br>
>><br>
>> apt-get install foo<br>
>> echo 1 > bar<br>
>><br>
>> will have the expected result.<br>
>> That is: looks similar to the previous version, but one can easily<br>
>> select commands without the prompt.<br>
>><br>
>> Does it sound like a good idea?<br>
>><br>
>> We'd need first to enable the Sphinx extension wherever we use Sphinx.<br>
>> Does that actually require to patch each git repository that contains<br>
>> documentation or do we have another way of doing it globally?<br>
>> Then, documentations should start using ".. prompt:: bash" instead of<br>
>> ".. code-block:: console" when appropriate - the change could be<br>
>> automated or not.<br>
>><br>
>> Adrien<br>
>><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-docs mailing list<br>
>> <a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a> <mailto:<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>
>><br>
>><br>
>><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>
><br>
<br>
<br>
--<br>
</div></div> Andreas Jaeger aj@{<a href="http://suse.com" rel="noreferrer" target="_blank">suse.com</a>,<a href="http://opensuse.org" rel="noreferrer" target="_blank">opensuse.org</a>} Twitter: jaegerandi<br>
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Felix Imendörffer, Jane Smithard, Graham Norton,<br>
HRB 21284 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
<div class="HOEnZb"><div class="h5"><br>
<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>
</div></div></blockquote></div><br></div>