@Bug Squad I've noticed a couple of things about Allura which are worth mentioning:
a) When you add a new issue or change the status, patch, label, etc, of an existing one, it takes some time, i.e. several minutes, before it shows up in searches involving the new value. Allura maintains a large inverted index in order to reduce the time and resource needed to perform complex searches, but the price for this is the increased time required to modify that index when one of the field values changes. b) This is a real nuisance. The body text of issues uses markup. See "Formatting Help" underneath the search buttons. Some of this is useful, but some not. In particular, a line with # in column one means "format as a huge header". So a line of Scheme which is not indented appears huge. This means that Lily source code should be either indented by four spaces or a tab. Alternatively, insert a line containing 4 (or more) tildes before and after the Lily code. As an example, see https://sourceforge.net/p/testlilyissues/issues/4581/ before Simon works out how to fix it ;) Trevor _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel