So, I learnt something new today! I'll revert the patch.
However, there are several examples, both in input/*/*
and in scm/define-context-properties.scm which set these
properties in Staff or Score. Should I change them as well?
Another feature that's slightly confusing is that
\score {
\r
[EMAIL PROTECTED] writes:
>
> Patches:
> Index: lilypond/ChangeLog
> diff -u lilypond/ChangeLog:1.2689 lilypond/ChangeLog:1.2690
> --- lilypond/ChangeLog:1.2689 Fri Oct 8 07:55:20 2004
> +++ lilypond/ChangeLogFri Oct 8 08:02:18 2004
> @@ -1,7 +1,8 @@
> 2004-10-08 Mats Bengtsson <[EMA
[EMAIL PROTECTED] writes:
>
>
> The command @code{\bar [EMAIL PROTECTED] is a short cut for doing
> [EMAIL PROTECTED] Timing.whichBar = [EMAIL PROTECTED] Whenever @code{whichBar}
> [EMAIL PROTECTED] Staff.whichBar = [EMAIL PROTECTED] Whenever @code{whichBar}
why did you make this correction
[EMAIL PROTECTED] writes:
>
> [EMAIL PROTECTED],relative=1]
> [EMAIL PROTECTED] why isn't relative working?
> [EMAIL PROTECTED],relative=1,quote]
> {
>\fatText
>\time 2/2
You need the fragment option as well to make it work.
A related request;` can you make sure that all fragments h
Graham Percival wrote:
I definitely agree with this. The shortcuts also increase readability
and look much friendlier. If I were browsing around Mutopia or other
Lilypond examples, I'd much rather see
\tieUp
than
\override Tie #'direction = #1(or should that be -1 ?)
Why no use \override Tie
On 24-Aug-04, at 3:54 AM, Mats Bengtsson wrote:
I think the main problem is not the work to enter the code, but rather
the work to find out how to do it. I think the shortcuts help both
for newcomers who haven't yet learned how to set properties, somewhat
experienced people who still have problems
I think the main problem is not the work to enter the code, but rather
the work to find out how to do it.
I usually feel uncomfortable editing properties directly because it
feels like interaction with the core at too low a level of abstraction.
If these internal properties are changed or rename
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
May I ask for the reason of this change. I think it's very
convenient to have this kind of shortcut, especially for
scripts, where two different layout objects are involved,
depending on the type of script.
I deemed it unnecessary since there is a
[EMAIL PROTECTED] writes:
> May I ask for the reason of this change. I think it's very
> convenient to have this kind of shortcut, especially for
> scripts, where two different layout objects are involved,
> depending on the type of script.
I deemed it unnecessary since there is already very conve
May I ask for the reason of this change. I think it's very
convenient to have this kind of shortcut, especially for
scripts, where two different layout objects are involved,
depending on the type of script.
/Mats
Han-Wen Nienhuys wrote:
CVSROOT:/cvsroot/lilypond
Module name:lilypond
10 matches
Mail list logo
