On 21-Aug-05, at 4:31 AM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
no, it means:
WTF is a file that doesn't parse doing in the ly/ directory?
Well, WTF can't lily parse it?
It has been documented (probably as BUG); the problem is that
{ \override Foo ... }
is a music expression.
Graham Percival wrote:
no, it means:
WTF is a file that doesn't parse doing in the ly/ directory?
Well, WTF can't lily parse it?
It has been documented (probably as BUG); the problem is that
{ \override Foo ... }
is a music expression. You can't put music expressions in \context {
\
On 20-Aug-05, at 3:36 PM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
Do you mean "WTF doesn't this just use \voiceOne", or "WTF does
bagpipe music have all stems down, slurs up, and ties up" ?
no, it means:
WTF is a file that doesn't parse doing in the ly/ directory?
Well, WTF can't l
Graham Percival wrote:
On 19-Aug-05, at 11:18 AM, Han-Wen Nienhuys wrote:
Index: lilypond/ly/bagpipe.ly
diff -u lilypond/ly/bagpipe.ly:1.3 lilypond/ly/bagpipe.ly:1.4
% Layout tweaks.
+%{
+
+% WTF is this? --hwn
\layout {
\context {
\Voice
@@ -63,6 +66,8 @@
\tieUp
}
}
Do
On 19-Aug-05, at 11:18 AM, Han-Wen Nienhuys wrote:
Index: lilypond/ly/bagpipe.ly
diff -u lilypond/ly/bagpipe.ly:1.3 lilypond/ly/bagpipe.ly:1.4
% Layout tweaks.
+%{
+
+% WTF is this? --hwn
\layout {
\context {
\Voice
@@ -63,6 +66,8 @@
\tieUp
}
}
Do you mean "WTF doesn't this
On 10-Jan-05, at 5:41 AM, Mats Bengtsson wrote:
- I normally use a separate identifier for annotations like
tempo changes ("Andante", ...) that should only appear on the
top of the full score but in all the individual parts. Of course,
such a thing can also be done with \tag commands, but it
[EMAIL PROTECTED] writes:
>
> On 9-Jan-05, at 8:21 AM, Han-Wen Nienhuys wrote:
>
> > [EMAIL PROTECTED] writes:
> >> This would _greatly_ improve the organization of large LilyPond
> >> projects.
> >> I very enthusiastically second this motion. :)
> >
> > There is a -e SCHEME-CODE command line op
I both agree and disagree! My main objections are:
- I normally use a separate identifier for annotations like
tempo changes ("Andante", ...) that should only appear on the
top of the full score but in all the individual parts. Of course,
such a thing can also be done with \tag commands, but
On 9-Jan-05, at 8:21 AM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
This would _greatly_ improve the organization of large LilyPond
projects.
I very enthusiastically second this motion. :)
There is a -e SCHEME-CODE command line option, which can be used to
pass arbitrary code into Lily. It
[EMAIL PROTECTED] writes:
>
> On 7-Jan-05, at 3:36 AM, Erik Sandberg wrote:
>
> > Also, if there would be a command-line option to select/unselect
> > certain tags,
> > there would be a clear advantage to use tags for extracting parts.
> > E.g.,
> > lilypond -usetag viola quartet.ly
> > could e
Graham Percival wrote:
On 7-Jan-05, at 9:15 AM, Paul Scott wrote:
Juergen Reuter wrote:
Another requested feature at that time was the cue notes problem:
You want to print cue notes only when extracting parts, but not when
printing the whole score. Hence, just tag all cue notes and filter
them
This isn't to demonstrate \tag. If I wanted to do that, I'd add it to
the Notation
chapter. Example templates isn't the place to demonstrate such things.
No, the reason is that I have a pathological dislike of having anything
in the individual instrument files that doesn't need to be there.
Sur
On 7-Jan-05, at 3:36 AM, Erik Sandberg wrote:
Also, if there would be a command-line option to select/unselect
certain tags,
there would be a clear advantage to use tags for extracting parts.
E.g.,
lilypond -usetag viola quartet.ly
could extract the viola part. This approach would result in the n
On 7-Jan-05, at 9:15 AM, Paul Scott wrote:
Juergen Reuter wrote:
Another requested feature at that time was the cue notes problem: You
want to print cue notes only when extracting parts, but not when
printing the whole score. Hence, just tag all cue notes and filter
them out when printing the w
Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> I use \tag to define marks or markups that should appear only above the
> first staff of a system, or below the last staff. For instance:
hmm this was not a good example, as setting the direction of marks
could have done the same result. This is better
Mats Bengtsson <[EMAIL PROTECTED]> writes:
> Now I realize that you did this to get an example of how to use \tag.
> Still, the problem is that it doesn't really show any advantage (as
> far as I can see). Can't we find a better example where the command
> gives a clearer advantage?
>
> /Mats
Juergen Reuter wrote:
Another requested feature at that time was the cue notes problem: You want
to print cue notes only when extracting parts, but not when printing the
whole score. Hence, just tag all cue notes and filter them out when
printing the whole score.
Not to negate your point for
On Friday 07 January 2005 11.03, Mats Bengtsson wrote:
> (Normally it's a good idea to read the emails in reverse order
> to avoid answering a question that has already been answered by
> others, but in this case it was a mistake not to have read the
> earlier emails related to the subject.)
>
> No
On Fri, 7 Jan 2005, Mats Bengtsson wrote:
> ...
>
> Now I realize that you did this to get an example of how to use \tag.
> Still, the problem is that it doesn't really show any advantage (as
> far as I can see). Can't we find a better example where the command
> gives a clearer advantage?
>
>
ng string quartet \tag part extraction. Large section with
@verbose. I think it's ok, but if anything breaks web-doc, it would
be this untested patch.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/examples.itely.diff?tr1=1.28&tr2=1.29&
avannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/examples.itely.diff?tr1=1.28&tr2=1.29&r1=text&r2=text
Patches:
Index: lilypond/Documentation/user/examples.itely
diff -u lilypond/Documentation/user/examples.itely:1.28 lilypond/Documentation/user/examples.itely:1.29
---
21 matches
Mail list logo
