Thanks for pointing to the Tiny Examples section. Didn't know this existed, good idea. In programming it is a common method to squeeze your problem to something as small as possible. Also a good start for any regression test.
But the top part of the example shown uses an include-file. That is not "tiny", anything can happen there. So I would add to the rules for a tiny example no use of include files.
And the page tells about an example? What example you want:
- what this example of a problem produces (everyone can grab the code and see for himself, but showing it right away is much, much faster for everyone)
- what the author wants to happen (likes something not accomplished but desired)
- or both (my preference)
And how does one place an example there? (and remove when not valid anymore, for example if your tiny tie-problem -- which is ugly indeed! -- is solved in a next version, this example may be updated with the text "Solved" and removed in the next run.)
Regards,
Wim.
P.S. My tiny example:
Wanted attached in a small example (not realized), code I think should produce it:
\version "2.16.0"
{
\key f \major
\time 4/4
\slashedGrace {
\stemDown
d'32[ c']
}
\stemUp
f32[c' f' g' a' g' f' c']
}
On 28 Oct 2012, at 08:19 , Janek Warchoł wrote:
On Sun, Oct 28, 2012 at 3:25 AM, Daniel Rosen <address@hidden> wrote:[...]This is the first time I've answered a question on the list
That's great! I find your answer clear and helpful - hopefully Mark
will like it, too :)but I don't think I'd be out of line by asking you to use tiny examples in the future.
+1 (I agree)
see also http://www.lilypond.org/tiny-examples.html
cheers,
Janek
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user