"Trevor Daniels" <t.dani...@treda.co.uk> writes: > Simon Albrecht wrote Monday, September 07, 2015 7:16 PM >> > >> Am 07.09.2015 um 20:09 schrieb Dan Eble: >>> Compare >>> >>> https://code.google.com/p/lilypond/issues/detail?id=1677 >>> https://sourceforge.net/p/testlilyissues/issues/1677/ >>> <https://sourceforge.net/p/testlilyissues/issues/1677/> >>> >>> The latter has square brackets around rests, e.g. “[r4]” instead of “r4”. >> >> Oh shoot! That’s not a problem with the port, but it has been a problem >> with Google adding a link to >> <https://code.google.com/p/lilypond/source/detail?r=4>, which in the >> source for Allura markdown reads >> "[r4]<https://code.google.com/p/lilypond/source/detail?r=4>". >> But I imagine it shouldn’t be too complicated to make a script to >> convert [r4] into r4 and similar with different durations. One >> complication is that R1 has been converted into [r1]… > > I don't understand what the url links in GC were supposed to do, but > whatever it was they are broken now. I've never seen links attached > to rests before, so I think this is a one-off, probably caused by pasting > text from elsewhere. In which case it's probably easiest to simply > edit this issue manually.
I guess they link to (non-existent) SVN revisions, just like a full SHA links to a (non-existent) Git revision. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel