[Xastir-dev] How to escape in Github

[km5vy Tom Russo]

Also, the thing mentioned in that github issue as an API call that could
be tried is way off base, and was probably written by someone who doesn't 
know what a "ref" is in Git.  It has nothing to do with github issue
autolinking.

On Tue, May 07, 2019 at 02:29:32PM -0700, we recorded a bogon-computron collision of the <curt.we7u at gmail.com> flavor, containing:
> That sucks, but at least it's understandable. Human nature means it will
> happen again.
> 
> On Tue, May 7, 2019 at 2:28 PM Tom Russo <russo at bogodyn.org> wrote:
> 
> > On Tue, May 07, 2019 at 03:22:15PM -0600, we recorded a bogon-computron
> > collision of the <russo at bogodyn.org> flavor, containing:
> > > 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.
> >
> > Unfortunately, once the "#1" thing gets done, Github automatically puts a
> > notation on issue #1 (or PR #1 or whatever #1 is) that it was referenced
> > from
> > elsewhere.  There is no way to delete these references after the fact.
> > There is an open request for that sort of thing on github:
> >
> > https://github.com/isaacs/github/issues/1235
> >
> > There may be a way to do it through the API, but it's not clear that anyone
> > has actually tried it.
> >
> >
> > Previewing comments before clicking the "Comment" button would help to
> > avoid
> > doing this before the confusing references are created, but there's nothing
> > to be done after the fact, it seems.
> >
> > This is bound to happen again, because the information that was pasted in
> > was relevant, and editing every line of it isn't the rational way to deal.
> > Gonna have to be careful in the future to remember to block-quote or
> > code-quote
> > such things.
> >
> > > On Tue, May 07, 2019 at 01:30:14PM -0700, we recorded a bogon-computron
> > collision of the <curt.we7u at 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 at lists.xastir.org
> > > http://xastir.org/mailman/listinfo/xastir-dev
> >
> > --
> > 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 at lists.xastir.org
> > http://xastir.org/mailman/listinfo/xastir-dev
> >
> 
> 
> -- 
> Curt, WE7U        http://we7u.wetnet.net        http://www.sarguydigital.com

-- 
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]