Inline code in the docs - the correct way

[H. S. Teoh]

On Thu, Feb 01, 2018 at 09:09:28AM -0500, Steven Schveighoffer via Digitalmars-d 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.

Yeah, vim has had this *by default* since who knows how long ago.  I've
been surprised that things like this still bother people today --
non-vim users are missing out!


> When I'm reviewing a PR, I don't see the matching as easily. Even with
> an editor tool, it's a lot of parentheses to look at.
[...]

This is one reason I'm not a fan of browser-based tools. They're
essentially just 90's technology in fancy dress.  For reviewing
complicated PRs, I still prefer just fetching the git branch directly
into my local Phobos fork and using vim to look through the code.  Seb's
git scripts for fetching/pushing PRs is pretty useful for this; see the
Maintainer's guidelines page on the wiki.


T

-- 
Valentine's Day: an occasion for florists to reach into the wallets of
nominal lovers in dire need of being reminded to profess their
hypothetical love for their long-forgotten.