Inline code in the docs - the correct way

[Steven Schveighoffer]

On 2/5/18 2:53 AM, Walter Bright wrote:
> On 2/4/2018 11:34 AM, Steven Schveighoffer wrote:
>> 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
> 
> So I see. I wonder when that was added to vim. I put it in MicroEmacs in 
> the late 1980s, and vi definitely didn't have it then. I didn't put in 
> Pascal begin/end, because I didn't care for Pascal :-)

I should clarify -- the matching parentheses feature has been in vim 
forever (note -- vim didn't exist in the last 80s, straight vi I think 
doesn't have these features). I don't know how long the matching 
#if/#endif feature has been there, I haven't used it much.

A nice feature of this is that the "jump to match" command is like any 
other move command in vim -- you can hook it to copy/pasting, deleting, 
formatting, etc. It's very useful.

But this is a bit off topic :)

-Steve