I have now added both methods to the LSR awaiting approval.
Once they are published we can then link them to the LSR URLs instead of
filling up the tracker with lots of different methods.
James
On 15/12/2010 12:56, Phil Holmes wrote:
----- Original Message ----- From: "James" <james.l...@datacore.com>
However as a general question from all this regarding workarounds,
while we don't document workarounds in the Notation Reference or the
Learning manual and while we use Snippets and LSR for 'tweaks' like
this; I wondered from the point of view of a new user or someone
hunting on how to do something like this and then getting pointed to
the tracker as 'known bug', or 'enhancement that no one is working
on', can we put a/the current workaround for said bug/enhancement in
the tracker?
James
Reckon so.
http://code.google.com/p/lilypond/issues/list?can=2&q=workaround
--
Phil Holmes
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
