Inline code in the docs - the correct way

[Steven Schveighoffer]

On 2/2/18 7:10 PM, Walter Bright wrote:
> On 2/1/2018 6:09 AM, Steven Schveighoffer wrote:
>> On 1/31/18 9:58 PM, Walter Bright wrote:
>>> On 1/31/2018 5:37 PM, Steven Schveighoffer wrote:
>>>> Where it breaks down is when you have many nested tags, and you end 
>>>> with )))))
>>>
>>> Long ago, I adjusted my text editor so that when the cursor is placed 
>>> on ), the matching ( is found. Ditto for { }, [ ], < >, and 
>>> #if/#elif/#else/#endif (!). It's been incredibly convenient.
>>
>> This has literally been in vim since I started using it, what, 15 
>> years ago? It doesn't matter.
> 
> The #if too?

Yes. http://vim.wikia.com/wiki/Moving_to_matching_braces

>> When I'm reviewing a PR, I don't see the matching as easily.
> 
> True, but that applies to anything with a block structure.

Sure, I also have a difficult time with loads of parentheses in function 
calls too.

I don't have a hard time with braces. It tends to be worse with 
parentheses. Generally these are indented properly, and not }}}}} all on 
one line.

Note: if there are brace issues, the auto-tester fails it. Why did that 
example I posted not catch the extra closing paren? Can we have it do so?

-Steve