search for: yypvr

...;reason" for preferring the Python style > is that I've sometimes had to squint to tell apart ------ and ~~~~~~, but I > have never had that problem with ====== and -------. btw, if you use vim, > an easy way to make an ===== underline of the same width as the current > line is yypVr= and a similar command works for ----- or any other character. > I agree with you that the tilde does not work well as a highlighter. Also, I'm on Windows and I use SlickEdit - and occasionally gedit. btw, if you haven't found out that sphinx generally puts a "show source" &...

...ncredibly weak "reason" for preferring the Python style is that I've sometimes had to squint to tell apart ------ and ~~~~~~, but I have never had that problem with ====== and -------. btw, if you use vim, an easy way to make an ===== underline of the same width as the current line is yypVr= and a similar command works for ----- or any other character. btw, if you haven't found out that sphinx generally puts a "show source" link on the HTML it generates, you should be aware of it. it's really useful to quickly see what the reST source code looks like corresponding t...

...;reason" for preferring the Python style > is that I've sometimes had to squint to tell apart ------ and ~~~~~~, but I > have never had that problem with ====== and -------. btw, if you use vim, > an easy way to make an ===== underline of the same width as the current > line is yypVr= and a similar command works for ----- or any other character. > > btw, if you haven't found out that sphinx generally puts a "show source" > link on the HTML it generates, you should be aware of it. it's really > useful to quickly see what the reST source code looks l...

I just finished up the first draft of the FAQ translated verbatim from HTML to Sphinx. Sphinx did puzzle me a few times but I got used to its approximate error messages and figured out what the problems were. Perhaps you could take a quick glance at this file and tell me if I am doing something wrong? Otherwise I'll send it off to llvm-commits and see what they say. Thanks, Mikael

> 8. A Technical Writer FAQ (should include the Sphinx documentation from the lld docs). I'm working on the Sphinx stuff; if you have any questions about writing Sphinx docs feel free to ask. --Sean Silva On Wed, Jun 13, 2012 at 4:37 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > I think the best way that I can currently contribute to the project is > through technical