Displaying 10 results from an estimated 10 matches for "literalinclude".
2012 Dec 03
3
[LLVMdev] LLVM documentation work help
...ple uvbook seems put the html and pdf on different github directory. Do you put html and pdf on github with version control?
Jonathan
On 2012/12/3, at 上午7:43, Sean Silva <silvas at purdue.edu> wrote:
> It looks like things are going well.
>
> One suggestion. Instead of using `.. literalinclude::` for displaying
> the terminal sessions, you can use `.. code-block:: bash` instead. The
> reason that uvbook uses `.. literalinclude` is that they are showing
> parts of real compilable programs. If you just want to show a snippet
> of code or terminal snippet, you can use `.. code-b...
2012 Dec 02
0
[LLVMdev] LLVM documentation work help
It looks like things are going well.
One suggestion. Instead of using `.. literalinclude::` for displaying
the terminal sessions, you can use `.. code-block:: bash` instead. The
reason that uvbook uses `.. literalinclude` is that they are showing
parts of real compilable programs. If you just want to show a snippet
of code or terminal snippet, you can use `.. code-block::` and avoid
ha...
2012 Dec 03
0
[LLVMdev] LLVM documentation work help
...on different github directory. Do you put html and pdf on github with version control?
>
> Jonathan
>
>
> On 2012/12/3, at 上午7:43, Sean Silva <silvas at purdue.edu> wrote:
>
>> It looks like things are going well.
>>
>> One suggestion. Instead of using `.. literalinclude::` for displaying
>> the terminal sessions, you can use `.. code-block:: bash` instead. The
>> reason that uvbook uses `.. literalinclude` is that they are showing
>> parts of real compilable programs. If you just want to show a snippet
>> of code or terminal snippet, you ca...
2012 Nov 29
2
[LLVMdev] LLVM documentation work help
Sean,
By try, I seems realize the github.com is free for register. So, just ignore my last mail.
Anoushe,
You can register with email and get an account on
https://github.com/
I have put the our document reStructuredText on git.hub.com. You can clone it without register.
After you get an account and I add it to collaborators, then you can do check in with our project as follows,
2012 Dec 04
5
[LLVMdev] LLVM documentation work help
...on different github directory. Do you put html and pdf on github with version control?
>
> Jonathan
>
>
> On 2012/12/3, at 上午7:43, Sean Silva <silvas at purdue.edu> wrote:
>
>> It looks like things are going well.
>>
>> One suggestion. Instead of using `.. literalinclude::` for displaying
>> the terminal sessions, you can use `.. code-block:: bash` instead. The
>> reason that uvbook uses `.. literalinclude` is that they are showing
>> parts of real compilable programs. If you just want to show a snippet
>> of code or terminal snippet, you ca...
2012 Dec 04
0
[LLVMdev] LLVM documentation work help
...gt; > Jonathan
> >
> >
> > On 2012/12/3, at 上午7:43, Sean Silva <silvas at purdue.edu<http://mc/compose?to=silvas at purdue.edu>>
> wrote:
> >
> >> It looks like things are going well.
> >>
> >> One suggestion. Instead of using `.. literalinclude::` for displaying
> >> the terminal sessions, you can use `.. code-block:: bash` instead. The
> >> reason that uvbook uses `.. literalinclude` is that they are showing
> >> parts of real compilable programs. If you just want to show a snippet
> >> of code or term...
2012 Dec 04
0
[LLVMdev] LLVM documentation work help
...ntrol?
> >
> > Jonathan
> >
> >
> > On 2012/12/3, at 上午7:43, Sean Silva <silvas at purdue.edu> wrote:
> >
> >> It looks like things are going well.
> >>
> >> One suggestion. Instead of using `.. literalinclude::` for displaying
> >> the terminal sessions, you can use `.. code-block:: bash` instead. The
> >> reason that uvbook uses `.. literalinclude` is that they are showing
> >> parts of real compilable programs. If you just want to show a snippet
> >>...
2012 Dec 04
1
[LLVMdev] LLVM documentation work help
...ntrol?
> >
> > Jonathan
> >
> >
> > On 2012/12/3, at 上午7:43, Sean Silva <silvas at purdue.edu> wrote:
> >
> >> It looks like things are going well.
> >>
> >> One suggestion. Instead of using `.. literalinclude::` for displaying
> >> the terminal sessions, you can use `.. code-block:: bash` instead. The
> >> reason that uvbook uses `.. literalinclude` is that they are showing
> >> parts of real compilable programs. If you just want to show a snippet
> >>...
2012 Nov 29
0
[LLVMdev] LLVM documentation work help
> I am happy to introduce Anoushe, my llvm backend documentation work helper for English and edit.
Awesome! Great to see people helping out. Thank you both for working on this.
> Is it possible, me and Anoushe can get a git free space and access right for the reStructuredText files (include .png pictures) of me and Anoushe create in future? If not allowed. Can we hand over the
2012 Dec 04
2
[LLVMdev] LLVM documentation work help
...n different github directory. Do you put html and pdf on github with version control?
>
> Jonathan
>
>
> On 2012/12/3, at 上午7:43, Sean Silva <silvas at purdue.edu> wrote:
>
>> It looks like things are going well.
>>
>> One suggestion. Instead of using `.. literalinclude::` for displaying
>> the terminal sessions, you can use `.. code-block:: bash` instead.
The
>> reason that uvbook uses `.. literalinclude` is that they are showing
>> parts of real compilable programs. If you just want to show a snippet
>> of code or terminal snippet, you c...