[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated |
Date: |
Mon, 06 Jan 2014 20:50:41 +0000 |
Comment #11 on issue 3592 by address@hidden: \lyrics depracated
http://code.google.com/p/lilypond/issues/detail?id=3592
In general, syntactic sugar that hides necessary constructs is probably not
a good idea.
To succeed with LilyPond, users need to know about contexts. Hiding the
creation of contexts is likely not a good idea. Even though it's less
typing, it's one more alternative construct to learn.
It seems to me like it's always better to use
\new ChordNames { \chordmode {} }
than to use
\chords {}
So I think I'd probably be in favor of eliminating all these shortcuts.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated, lilypond, 2014/01/05
- Message not available
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated, lilypond, 2014/01/05
- Message not available
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated, lilypond, 2014/01/06
- Message not available
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated, lilypond, 2014/01/06
- Message not available
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated, lilypond, 2014/01/06
- Message not available
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated, lilypond, 2014/01/06
- Message not available
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated, lilypond, 2014/01/06
- Message not available
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated,
lilypond <=
- Message not available
- Re: [Lilypond-auto] Issue 3592 in lilypond: \lyrics depracated, lilypond, 2014/01/06