The right thing to do here was probably just change the entire block to a code block rather than inline text. That ignores markdown and just quotes it exactly.
It was a direct cut and paste from email. I have gone back to #66 and re-edited it to remove the "\# " and just put the whole thing into a code-quoted block. On Tue, May 07, 2019 at 01:30:14PM -0700, we recorded a bogon-computron collision of the <curt.w...@gmail.com> flavor, containing: > We had one Github issue where we had a series of numbers in a comment ( > https://github.com/Xastir/Xastir/issues/66#issuecomment-486514563 ) like: > > #1 blah > #2 blah blah > #3 blah blah blah > > Those numbers got auto-linked to other things in Github because of the > hash/number format used. I fixed it with a backslash before plus a space > after the hash mark to get them to unlink. I edited the comment on Github > to do this fix. > > Several methods of escaping such sequences are listed here: > > https://stackoverflow.com/questions/20532546/escape-pound-or-number-sign-in-github-issue-tracker -- Tom Russo KM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] _______________________________________________ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
