Return to Answer

Problem rendering LilyPond code with \slurDashed

(See: LilyPond - opacity of objects (slurs specifically))

Wrapping c with code fences (``` & ```):

c

Pass

Wrapping \slurDashed c with code fences (``` & ```):

\slurDashed
c

Fail — Looks find in the editor, and looks fine when first posted, but does not render upon a reload of the page.

Wrapping \slurDashed c with code fences and language hint (```lilypond & ```):

\slurDashed
c

Fail — Same as above

Wrapping \slurDashed c with code fences and language hint (```plaintext & ```):

\slurDashed
c

Fail — Same as above

Wrapping \slurDashed c with HTML preformatted text tags (<pre> & </pre>):

\slurDashed
c

Pass

It looks like the \slurDashed command is trigging jTab or ABCjs (or something else).

Problem rendering LilyPond code with \slurDashed

(See: LilyPond - opacity of objects (slurs specifically))

Wrapping c with code fences (``` & ```):

c

Pass

Wrapping \slurDashed c with code fences (``` & ```):

\slurDashed
c

Fail — Looks find in the editor, and looks fine when first posted, but does not render upon a reload of the page.

Wrapping \slurDashed c with code fences and LilyPond language hint (```lilypond & ```):

\slurDashed
c

Fail — Same as above

Wrapping \slurDashed c with code fences and Plaintext language hint (```plaintext & ```):

\slurDashed
c

Fail — Same as above

Wrapping \slurDashed c with HTML preformatted text tags (<pre> & </pre>):

\slurDashed
c

Pass

It looks like the \slurDashed command is trigging jTab or ABCjs (or something else).

Problem rendering LilyPond code with \slurDashed

(See: LilyPond - opacity of objects (slurs specifically))

Wrapping c with backticks (``` & ```):

c

Pass

Wrapping \slurDashed c with backticks (``` & ```):

\slurDashed
c

Fail — Looks find in the editor, and looks fine when first posted, but does not render upon a reload of the page.

Wrapping \slurDashed c with HTML preformatted text tags (<pre> & </pre>):

\slurDashed
c

Pass

It looks like the \slurDashed command is trigging jTab or ABCjs (or something else).

Problem rendering LilyPond code with \slurDashed

(See: LilyPond - opacity of objects (slurs specifically))

Wrapping c with code fences (``` & ```):

c

Pass

Wrapping \slurDashed c with code fences (``` & ```):

\slurDashed
c

Fail — Looks find in the editor, and looks fine when first posted, but does not render upon a reload of the page.

Wrapping \slurDashed c with code fences and language hint (```lilypond & ```):

\slurDashed
c

Fail — Same as above

Wrapping \slurDashed c with code fences and language hint (```plaintext & ```):

\slurDashed
c

Fail — Same as above

Wrapping \slurDashed c with HTML preformatted text tags (<pre> & </pre>):

\slurDashed
c

Pass

It looks like the \slurDashed command is trigging jTab or ABCjs (or something else).

Problem rendering code

(See: LilyPond - opacity of objects (slurs specifically))

Wrapping c with backticks (``` & ```):

c

Pass

Wrapping \slurDashed c with backticks (``` & ```):

\slurDashed
c

Fail — Looks find in the editor, and looks fine when first posted, but does not render upon a reload of the page.

Wrapping \slurDashed c with html preformatted text tags (<pre> & </pre>):

\slurDashed
c

Pass

It looks like \slurDashed is trigging a jTab or ABCjs command.

Problem rendering LilyPond code with \slurDashed

(See: LilyPond - opacity of objects (slurs specifically))

Wrapping c with backticks (``` & ```):

c

Pass

Wrapping \slurDashed c with backticks (``` & ```):

\slurDashed
c

Fail — Looks find in the editor, and looks fine when first posted, but does not render upon a reload of the page.

Wrapping \slurDashed c with HTML preformatted text tags (<pre> & </pre>):

\slurDashed
c

Pass

It looks like the \slurDashed command is trigging jTab or ABCjs (or something else).