Re: Problem with \f at the beginning of a score [updated again]

Thorkil Wolvendans writes: > I'm staring at my source-file for 2 hours now, and can't find the > result to the problem: the forte symbol refuses to appear at the > beginning of the score. It appears that both texts are linked and centered. I have no idea why that may be, dynamic texts and others

Problem with \f at the beginning of a score [updated again]

(this must start to look like spam! I'm sorry: THIS is the correct file -- I'm too tired I guess! ) (to compile the score, please use this file, since the previous email doesn't contain the \f symbol which causes problems...stupid me!) Hi everyone! I'm staring at my source-file for 2 hours now,

Problem with \f at the beginning of a score [updated]

(to compile the score, please use this file, since the previous email doesn't contain the \f symbol which causes problems...stupid me!) Hi everyone! I'm staring at my source-file for 2 hours now, and can't find the result to the problem: the forte symbol refuses to appear at the beginning of the

Problem with \f at the beginning of a score

Hi everyone! I'm staring at my source-file for 2 hours now, and can't find the result to the problem: the forte symbol refuses to appear at the beginning of the score. For some odd reason, the symbol shows up at the next bar, when I want it to show up in the first. Now, this only happens in the

Re: Making a lilypond-book -- IT WORKS...sort of

Jan Nieuwenhuizen wrote: Mats Bengtsson writes: Having had a look at the full files, I realize what's up, Thanks looking into this, Mats, however namely a missing feature in lilypond-book! separate include directory for each \lilypondfile{...} or \begin{lilypond}...\end{lilypond} directive. I

Re: Making a lilypond-book -- IT WORKS...sort of

Mats Bengtsson writes: > Having had a look at the full files, I realize what's up, Thanks looking into this, Mats, however > namely a missing feature in lilypond-book! > separate include directory for each \lilypondfile{...} or > \begin{lilypond}...\end{lilypond} directive. I object to this fe

Re: proper placing of chordnames re: alternative ending brackets

I have added the following example to the Tips and Tricks document (both for 2.2.x and the development series). \version "2.2.0" \header { texidoc = "@cindex ChordNames repeats To make the chord names appear below the brackets of the alternative endings of a repeat, move the Volta_engraver to t

Re: Making a lilypond-book -- IT WORKS...sort of

Having had a look at the full files, I realize what's up, namely a missing feature in lilypond-book! The problem is that your file mvmt1/mvmt1.ly includes other files from the subdirectory mvmt1, using lines such as: \include "violino1.ly" \include "violino2.ly" \include "viola.ly" The same goes fo

Re: [svoboda@mandal.lti.cs.cmu.edu] Lilypond Comments!

[flup to mailing list] >> %% foe >> | a4 b8 >> | c16( d f) >> | c4-2 d > > OK. Is there a BNF grammar I can examine? I'm not sure just what > other kinds of exotic stuff 'what-beat' would have to recognize. No. The specification is in lily/parser.yy, but you can get most impor

Re: Good job on Lilypond

Han-Wen Nienhuys writes: > No, the ordering of expressions controls the ordering of object > creation. For example, due to formatting rules, the clef is always > printed left of the key signature. This is quite obvious if you know LilyPond, shouldn't this be mentioned in the tutorial (next to au

Re: Crazy $TEXMF procmail question

Could it possibly be that the script is run by /bin/sh when called from procmail but /bin/bash when you call it directly. Try: TEXMF='...' export TEXMF /Mats Scott Webber wrote: Hey everybody, I got this brainy idea to setup a procmail address that you email .ly src to and it emails you back a