[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Rehearsal Mark positioning
From: |
Mats Bengtsson |
Subject: |
Re: Rehearsal Mark positioning |
Date: |
Sun, 02 Sep 2001 22:43:51 +0200 |
> Maybe it would be easier for me to figure out a way to put a counter
> in the normal ^"text..." kind of syntax.
The following LaTeX lines defines a macro \marknumber that
can be used in a text script, for example: c^"\marknumber"
\newcounter{markcounter}
\newcommand{\marknumber}{\stepcounter{markcounter}\arabic{markcounter}}
Unless you use lilypond-book, you have to put these definitions
into a separate file, say global.tex and then add
\header{
...
latexheaders = "global.tex"
}
at the top of your .ly file. Unfortunately, there's a bug in
ly2dvi so it can't find the latexheaders files unless you add the
patch found at the end of this mail (extended compared to the
patch I sent earlier tonight).
> There is a problem when the rehearsal mark is at a linebreak, because
> lilypond is trying to put it on the next line, so the extra-offset
> just moves it into the left margin of the line after the note it
> should be attached to. (see the cantus part letter H in
>
> http://serpent.laymusic.org/lconrad/homepage/toweb/lungi.zip
> http://serpent.laymusic.org/lconrad/homepage/toweb/lungi.ps
>
> for an example.) I can work around this by inserting \noBreak after
> the mark. But I think for my purposes it's probably long-term better to
> go back to the marks over the notes, since it's a mark that goes with
> a note that I want.
You can easily change the way Lilypond handles marks at line
breaks, see the FAQ on "How do I get a fermata on a barline".
/Mats
diff -u scripts/ly2dvi.py~ scripts/ly2dvi.py
--- scripts/ly2dvi.py~ Thu Aug 23 15:21:55 2001
+++ scripts/ly2dvi.py Sun Sep 2 22:39:11 2001
@@ -66,7 +66,6 @@
import operator
import tempfile
import traceback
-import resource
@@ -81,6 +80,15 @@
def _ (s):
return s
+# Attempt to fix problems with limited stack size set by Python!
+# Sets unlimited stack size. Note that the resource module only
+# is available on UNIX.
+try:
+ import resource
+ resource.setrlimit(resource.RLIMIT_STACK, (-1,-1))
+except:
+ pass
+
layout_fields = ['dedication', 'title', 'subtitle', 'subsubtitle',
'footer', 'head', 'composer', 'arranger', 'instrument',
@@ -153,7 +161,7 @@
#
environment = {
'MFINPUTS' : datadir + '/mf' + ':',
- 'TEXINPUTS': datadir + '/tex:' + datadir + '/ps' + ':',
+ 'TEXINPUTS': datadir + '/tex:' + datadir + '/ps:' + os.getcwd() + ':',
'TFMFONTS' : datadir + '/tfm' + ':',
'GS_FONTPATH' : datadir + '/afm:' + datadir + '/pfa',
'GS_LIB' : datadir + '/ps',
@@ -297,10 +305,6 @@
Exit status of CMD
"""
- # Attempt to fix problems with limited stack size set by
Python!
- # Sets unlimited stack size.
- resource.setrlimit(resource.RLIMIT_STACK, (-1,-1))
-
if verbose_p:
progress (_ ("Invoking `%s\'") % cmd)
st = os.system (cmd)