Inline code in the docs - the correct way

[Seb]

On Saturday, 3 February 2018 at 04:37:44 UTC, Adam D. Ruppe wrote:
> On Friday, 2 February 2018 at 20:15:11 UTC, H. S. Teoh wrote:
>> This is the kind of thing you should be promoting to Andrei to 
>> convince him that dpldocs is better. ;-)
>
> I'm updating my fork now and check out this merge conflict:
>
> <<<<<<< HEAD
>      *  source = The [isInputRange|input range] to encode.
> =======
>      *  source = The $(REF_ALTTEXT input range, isInputRange, 
> std,range,primitives)
>      *           to _encode.
>>>>>>>> b905180b1fffa78f922677ee90ed8ae9b803fc4f
>
>
>
> My syntax is so much prettier. (note that the stupid leading _ 
> is something I strip out too. Ddoc's most moronic "feature". 
> Can we PLEASE kill that?!?!?!!)

Have you thought of simply postprocessing REF_ALTTEXT for your 
documentation engine for now?
That won't lead to merge conflicts ;-)
e.g.

sed -i "s/[$](REF_ALTTEXT \([^,]*\),\([^,]*\),[^)]*)/[\2|\1]" 
**/*.d