You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mark down file in gtiles with a **--text** (may require this in a header)
results in a &ndash being output, instead of "--", which breaks searching for
that text.
Ex:
https://code.google.com/p/chromium/codesearch#chromium/src/tools/gn/docs/referen
ce.md
"## **--args**: Specifies build arguments overrides."
Produces:
https://chromium.googlesource.com/chromium/src/+/master/tools/gn/docs/reference.
md
"–args: Specifies build arguments overrides."
But I expect:
"--args: Specifies build arguments overrides."
Original issue reported on code.google.com by scheib@chromium.org on 28 Apr 2015 at 8:35
The text was updated successfully, but these errors were encountered:
Yes, but the double dash transformation appears to be an undesired markdown
transformation? I don't see that in spec anywhere, and it seems to be a
destructive presentation formatting change.
Original comment by scheib@chromium.org on 28 Apr 2015 at 10:25
there is a lot of variation in markdown specs and implementations, and I
believe there are a number of implementations that do automatically turn --
into –
Which isn't to say this is a bug, just that it's not a particularly surprising
one if it is, and it would be understandable if it was the default behavior and
considered not a bug (at least, for non-code blocks).
Original comment by dpranke@chromium.org on 28 Apr 2015 at 10:32
Original issue reported on code.google.com by
scheib@chromium.org
on 28 Apr 2015 at 8:35The text was updated successfully, but these errors were encountered: