Re: several problems to solve (positioning of objects)
Jozef Riha wrote: thank you, i implemented fixes to http://zefo.szm.com/donotdelete/latex/imanuel2.pdf i've got however few notes/questions: - there is no way to enter (D) or G/H (first play G, then H) chord names Try these: 1. \set chordNameFunction = #(lambda p (make-simple-markup "(D)")) d \unset chordNameFunction 2. \set chordNameFunction = #(lambda p (make-simple-markup "G/H")) g \unset chordNameFunction - no idea how to put "Refr." string on line 17, before lyrics "Imanuel, na stupen vitezu..." \set stanza = "Refr."' I -- ma -- nu -- el -- Bert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Text-Interface Bug?
J L wrote: Hi, I'm not sure whether this is a bug or not. After trying to add text spanners and fermatas to a piece, LilyPond crashes, saying that the assertion in text-interfaces.cc on line 61 failed. I've attached the offending files and also the lilypond logs of that. Use \fermataMarkup iso. \fermata for R rests. I've put up real support for R^\fermata as a sponsored feature, for 65 EUR. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: several problems to solve (positioning of objects)
i am sorry but could you please incorporate/show me where to put these code snippets into my lilypond code? i am kinda lost. thank you very much. kindest regards, -- joe 2005/11/27, Bertalan Fodor <[EMAIL PROTECTED]>: > Jozef Riha wrote: > > >thank you, i implemented fixes to > >http://zefo.szm.com/donotdelete/latex/imanuel2.pdf > > > >i've got however few notes/questions: > > > >- there is no way to enter (D) or G/H (first play G, then H) chord names > > > > > Try these: > 1. > \set chordNameFunction = #(lambda p (make-simple-markup "(D)")) > d > \unset chordNameFunction > > 2. > \set chordNameFunction = #(lambda p (make-simple-markup "G/H")) > g > \unset chordNameFunction > > >- no idea how to put "Refr." string on line 17, before lyrics > >"Imanuel, na stupen vitezu..." > > > > > \set stanza = "Refr."' I -- ma -- nu -- el > > -- > Bert > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
> "MH" == Michael Haynie <[EMAIL PROTECTED]> writes:
MH> If I didn't have so many files to manage, I might consider that.
MH> However, there are enough that the double maintenance would drive me to
MH> distraction.
MH> The other problem with that solution is that it doesn't allow for the
MH> placement of a song number beside the title -- think of the typical
MH> layout of a hymnal.
MH> So I really do need to figure out how to get lilypond to leave the
MH> titling to LaTeX, somehow.
I have the same problem, but I do basically what Bernard suggested,
and write the .lytex file with a script that extracts the header
fields from the lilypond (or, in my case, the ABC file that's the
input for abc2ly).
MH> On Nov 26, 2005, at 9:16 PM, Bernard Hurley wrote:
>> If you are using lilypond-book it is probably easier to forget about
>> header fields and do something like:
>>
>> \section{Prelude}
>> --- some other text
>> \lilypondfile[indent=1.2\cm]{prelude.ly}
>>
>> in your lytex file. You can then easily generate a TOC.
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Re: Text-Interface Bug?
I had the same problem recently - it's caused by a \fermata command on a whole-bar or multi-measure rest. If you change this: R2.\fermata to this: R2.^\fermataMarkup you should be fine. >From: Linda Cantoni <[EMAIL PROTECTED]> >Date: Sat Nov 26 23:45:09 CST 2005 >To: J L <[EMAIL PROTECTED]> >Subject: Re: Text-Interface Bug? > >>From: J L <[EMAIL PROTECTED]> >>Date: Sat Nov 26 23:45:09 CST 2005 >>To: lilypond-user@gnu.org >>Subject: Text-Interface Bug? > >>Hi, >> >>I'm not sure whether this is a bug or not. After trying to add text spanners >>and fermatas to a piece, LilyPond crashes, saying that the assertion in >>text-interfaces.cc on line 61 failed. I've attached the offending files and >>also the lilypond logs of that. >> >>Aligorith >> >>_ >>Find the coolest online games @ http://xtramsn.co.nz/gaming >> >> >>___ >>lilypond-user mailing list >>lilypond-user@gnu.org >>http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
So it looks like you want to be able to do something like defining a
LaTeX macro \includesong {songfile} whose effect is something like:
--- do something with header info
\lilypondfile{songfile}
for that you do need lily to write the header info to a file. Actually
older versions of lily did do this before the days when it produced eps
files for lilypond-book so I can't see why it couldn't be reintroduced
as an option. You would also need an extra file so that header info
could be matched up with snippets. You would probably need to run LaTeX
several times for it to work, but if you are gereating a TOC you need to
do that anyway.
On Sun, 2005-11-27 at 00:48 -0500, Michael Haynie wrote:
> If I didn't have so many files to manage, I might consider that.
> However, there are enough that the double maintenance would drive me to
> distraction.
>
> The other problem with that solution is that it doesn't allow for the
> placement of a song number beside the title -- think of the typical
> layout of a hymnal.
>
> So I really do need to figure out how to get lilypond to leave the
> titling to LaTeX, somehow.
>
--
Bernard Hurley <[EMAIL PROTECTED]>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
On Sun, 2005-11-27 at 07:12 -0500, Laura Conrad wrote: > I have the same problem, but I do basically what Bernard suggested, > and write the .lytex file with a script that extracts the header > fields from the lilypond (or, in my case, the ABC file that's the > input for abc2ly). You could write a script to extract header information from the .ly file. However to be completely general it would have to follow includes and follow the same rules as lily e.g. recognising when one header definition overrides another. It would be better if lily did this for you. There was a time when it did - it probably still does if you use the tex backend. But lilypond-book now uses the eps backend. -- Bernard Hurley <[EMAIL PROTECTED]> ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
> "BH" == Bernard Hurley <[EMAIL PROTECTED]> writes:
BH> You could write a script to extract header information from
BH> the .ly file. However to be completely general it would have
BH> to follow includes and follow the same rules as lily
BH> e.g. recognising when one header definition overrides another.
That's why I didn't post my script; of course, it isn't completely
general, but it works for the way I do it. And anyone with enough
files to maintain that they have Michael's problem will have some kind
of method that doesn't need a completely general script.
BH> It would be better if lily did this for you.
I agree, but I also think that having the lilypond developers spend
time writing software that duplicates latex features (e.g. tables of
contents) is not a good use of resources.
BH> There was a time when it did - it probably still does if you
BH> use the tex backend. But lilypond-book now uses the eps
BH> backend.
The 2.6.x lilypond-book does in fact take care of extracting title,
composer, and maybe a couple of other headers for you and putting them
in the lilypond-book output. I think Michael's problem is that he
doesn't know how to get this output in the form he wants. I haven't
looked at the problem much. But it seems that it would be reasonable
to have some kind of hooks, so that, for instance, the title could be
output like:
\section*{this is the title}
so that the latex table of contents could be used. Or even:
\section*{$hymn_number. this is the title}.
where $hymn_number could be replaced by the value of the header
"hymn_number".
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
Bernard Hurley wrote: On Sun, 2005-11-27 at 07:12 -0500, Laura Conrad wrote: I have the same problem, but I do basically what Bernard suggested, and write the .lytex file with a script that extracts the header fields from the lilypond (or, in my case, the ABC file that's the input for abc2ly). You could write a script to extract header information from the .ly file. However to be completely general it would have to follow includes and follow the same rules as lily e.g. recognising when one header definition overrides another. It would be better if lily did this for try lilypond -H title foo.ly -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Trying to do a template
Version 2.6.3
I tried section 9.1.5, and I have tried about 30 variations of something similar to what they have in that section with no luck...
Here is one unsuccessful try... it must be that I am really missing some main concept of Lilypond?
\layout {
\context
{
\name MyChordNames
\override BarLine #'bar-size = #4
voltaOnThisStaff = ##t
\consists Bar_engraver
\consists "Volta_engraver"
\consists "Percent_repeat_engraver"
\alias ChordNames
}
\context
{
\Staff
\accepts "MyChordNames"
}
}
\chordmode{ \repeat volta 2 {
\partial 8 s8 | f2:maj f:7 \repeat "percent" 2 {bes1:7}
c:maj c:maj c:maj c:maj c:maj c:maj c:maj
} \alternative {
es e }
}
Sent from the Gnu - Lilypond - User forum at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: several problems to solve (positioning of objects)
Jozef Riha wrote: i am sorry but could you please incorporate/show me where to put these code snippets into my lilypond code? i am kinda lost. I think it's easy: \set chordNameFunction = #(lambda p (make-simple-markup "(D)")) d \unset chordNameFunction this goes to the chords section you already have (d is the chord which should be written as "(D)") And this: \set stanza = "Refr."' I -- ma -- nu -- el Goes to where there is Im -- ma -- nu -- el in the lyrics. (Search for stanza in lilypond doc for more examples) Bert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
Yes, that's exactly what I was thinking about doing.
So: Which scheme functions do I need to replace to accomplish that?
Are the suggested hooks are documented/supported hooks?
Thanks.
On Nov 27, 2005, at 8:46 AM, Bernard Hurley wrote:
So it looks like you want to be able to do something like defining a
LaTeX macro \includesong {songfile} whose effect is something like:
--- do something with header info
\lilypondfile{songfile}
for that you do need lily to write the header info to a file. Actually
older versions of lily did do this before the days when it produced eps
files for lilypond-book so I can't see why it couldn't be reintroduced
as an option. You would also need an extra file so that header info
could be matched up with snippets. You would probably need to run LaTeX
several times for it to work, but if you are gereating a TOC you need
to
do that anyway.
On Sun, 2005-11-27 at 00:48 -0500, Michael Haynie wrote:
If I didn't have so many files to manage, I might consider that.
However, there are enough that the double maintenance would drive me
to
distraction.
The other problem with that solution is that it doesn't allow for the
placement of a song number beside the title -- think of the typical
layout of a hymnal.
So I really do need to figure out how to get lilypond to leave the
titling to LaTeX, somehow.
--
Bernard Hurley <[EMAIL PROTECTED]>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: several problems to solve (positioning of objects)
thank you. now (probably) my last question about this score: how to typeset the set of slurs on the last line in http://www.3pe.cz/PDFnoty/Immanuel.pdf particularly those around "a g fis fis fis e" thanks. cheers, -- joe 2005/11/27, Bertalan Fodor <[EMAIL PROTECTED]>: > Jozef Riha wrote: > > >i am sorry but could you please incorporate/show me where to put these > >code snippets into my lilypond code? i am kinda lost. > > > > > I think it's easy: > > \set chordNameFunction = #(lambda p (make-simple-markup "(D)")) > d > \unset chordNameFunction > > this goes to the chords section you already have (d is the chord which should > be written as "(D)") > > And this: > \set stanza = "Refr."' I -- ma -- nu -- el > > Goes to where there is Im -- ma -- nu -- el in the lyrics. (Search for stanza > in lilypond doc for more examples) > > Bert > > > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: several problems to solve (positioning of objects)
Well, I suppose don't do that :-) You need only one slur and ties. However, if you still want to typeset your score so ugly, you can achieve that using phrasing slur \( Bert Jozef Riha wrote: thank you. now (probably) my last question about this score: how to typeset the set of slurs on the last line in http://www.3pe.cz/PDFnoty/Immanuel.pdf particularly those around "a g fis fis fis e" thanks. cheers, -- joe 2005/11/27, Bertalan Fodor <[EMAIL PROTECTED]>: Jozef Riha wrote: i am sorry but could you please incorporate/show me where to put these code snippets into my lilypond code? i am kinda lost. I think it's easy: \set chordNameFunction = #(lambda p (make-simple-markup "(D)")) d \unset chordNameFunction this goes to the chords section you already have (d is the chord which should be written as "(D)") And this: \set stanza = "Refr."' I -- ma -- nu -- el Goes to where there is Im -- ma -- nu -- el in the lyrics. (Search for stanza in lilypond doc for more examples) Bert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
On Sun, 2005-11-27 at 15:56 +0100, Han-Wen Nienhuys wrote: > try > >lilypond -H title foo.ly > Interesting this is not listed as a command line options in the docs, but lilypond --help tells you what happens. To use with lilypond-book, I suppose you could do: lilypond-book --process="lilypond -H title" > > -- Bernard Hurley <[EMAIL PROTECTED]> ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
On Sun, 2005-11-27 at 13:13 -0500, Michael Haynie wrote:
> Yes, that's exactly what I was thinking about doing.
>
> So: Which scheme functions do I need to replace to accomplish that?
> Are the suggested hooks are documented/supported hooks?
>
I don't think scheme is going to help. I thnk the solution is to modify
lilypond-book slightly.
However if you take the files
--- test.lytex ---
\documentclass{article}
\usepackage{graphicx}
\begin{document}
\lilypondfile{test.ly}
\end{document}
--
and
test.ly ---
\version "2.7.18"
\header {
title="The test title"
composer="Bernard Hurley"
}
{a b c}
and run:
lilypond-book --psfonts --process="lilypond -b eps -H title " test.lytex
you get a file called something like:
lily-1915112629.title
which contains the text of the header "title" - you can do the same with
any other header.
in addition to the generated test.tex
Now the file test.tex contains the code:
-test.tex
\ifx\preLilyPondExample \undefined
\relax
\else
\preLilyPondExample
\fi
\def\lilypondbook{}%
\input lily-1915112629-systems.tex
...
Now
\input lily-1915112629-systems.tex
Notice:
1] The files lily-1915112629-systems.tex and lily-1915112629.title both
start with "lily-1915112629" so this prefix must be available to
lilypond-book when it generates this code.
2] notice the macro call \preLilyPondExample (it only takes effect if
the macro is defined). If lilypond-book were modified so that it
generated the parameter {lily-1915112629}. Then it would be possible for
you to define the macro so that it read the file with the header.
Actually this modification looks quite easy. The real problem is whether
this would break any existing lytex code. (It can't be upgraded with
convert-ly because that just upgrades lily files). Another solution
would be to have two user-definable macros in the same place, which
seems a bit silly.
I'll have a think about it and then submit a patch.
--
Bernard Hurley <[EMAIL PROTECTED]>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
> "BH" == Bernard Hurley <[EMAIL PROTECTED]> writes: BH> Notice: BH> 1] The files lily-1915112629-systems.tex and lily-1915112629.title both BH> start with "lily-1915112629" so this prefix must be available to BH> lilypond-book when it generates this code. This seems a little baroque (in the bad sense) to me. Why not just run "lilypond -H title test.ly" and get test.title, which you can then include quite easily? -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
That looks like a nice hook.
I suppose I'd also have to tell lilypond to not generate the header for
each song somehow, since I'm going to be handling that myself.
The change to \preLilypondExample can be made backward compatible by
defining a variable that preLilypondExample can rely on -- it's a bit
of a hack, though. Using a parameter might be worth a little breakage,
since there will not likely be a huge number of places to edit.
One thing, though: using 2.6.4 (on Mac OS X, at least), lilypond-book
seems to insist on parsing the --process arguments, and so complains
that -b isn't a valid option. If a patch is possible against 2.6, that
should also be corrected.
I'll be delighted to test the patch.
On Nov 27, 2005, at 5:22 PM, Bernard Hurley wrote:
On Sun, 2005-11-27 at 13:13 -0500, Michael Haynie wrote:
Yes, that's exactly what I was thinking about doing.
So: Which scheme functions do I need to replace to accomplish that?
Are the suggested hooks are documented/supported hooks?
I don't think scheme is going to help. I thnk the solution is to modify
lilypond-book slightly.
However if you take the files
--- test.lytex ---
\documentclass{article}
\usepackage{graphicx}
\begin{document}
\lilypondfile{test.ly}
\end{document}
--
and
test.ly ---
\version "2.7.18"
\header {
title="The test title"
composer="Bernard Hurley"
}
{a b c}
and run:
lilypond-book --psfonts --process="lilypond -b eps -H title "
test.lytex
you get a file called something like:
lily-1915112629.title
which contains the text of the header "title" - you can do the same
with
any other header.
in addition to the generated test.tex
Now the file test.tex contains the code:
-test.tex
\ifx\preLilyPondExample \undefined
\relax
\else
\preLilyPondExample
\fi
\def\lilypondbook{}%
\input lily-1915112629-systems.tex
...
Now
\input lily-1915112629-systems.tex
Notice:
1] The files lily-1915112629-systems.tex and lily-1915112629.title both
start with "lily-1915112629" so this prefix must be available to
lilypond-book when it generates this code.
2] notice the macro call \preLilyPondExample (it only takes effect if
the macro is defined). If lilypond-book were modified so that it
generated the parameter {lily-1915112629}. Then it would be possible
for
you to define the macro so that it read the file with the header.
Actually this modification looks quite easy. The real problem is
whether
this would break any existing lytex code. (It can't be upgraded with
convert-ly because that just upgrades lily files). Another solution
would be to have two user-definable macros in the same place, which
seems a bit silly.
I'll have a think about it and then submit a patch.
--
Bernard Hurley <[EMAIL PROTECTED]>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
If you have a song book with 20 songs, it would be nice if you could
define \preLilyPondExample _once_ and then include the songs with
\lilypondfile. That way they would all be handled identically. You could
add and delete songs at will. Also you could change the way they are
handled by changing the macro \preLilyPondExample. The problem at
present is that lilypond-book does not generate a macro with a parameter
so there is no way to get hold of the .title file in the generated latex
code except by adding it by hand. You would also have to work out which
file you need - it's not obvious -look at the generated latex. So I
think the problem is most easily solved by changing llypond-book.
The way it would work is:
lilypond-book would have an extra option (-M or --mparam, say). If used
it would cause lilypond-book to generate a call to \preLilyPondExample
with an extra parameter, which would have the value of the base name of
the snippet file. So for instance if you were writing:
\section {title-of-song-1}
\lilypondfile {song1}
\section {title-of-song-2}
\lilypondfile {song2}
\section {title-of-song-n}
\lilypondfile {songn}
You could instead code:
\newcommand {\preLilyPondExample}[1]{\section {\protect\input #1.title }}
and then
\lilypondfile {song1}
\lilypondfile {song2}
\lilypondfile {songn}
Bernard
On Sun, 2005-11-27 at 18:19 -0500, Laura Conrad wrote:
> > "BH" == Bernard Hurley <[EMAIL PROTECTED]> writes:
>
> BH> Notice:
> BH> 1] The files lily-1915112629-systems.tex and lily-1915112629.title
> both
> BH> start with "lily-1915112629" so this prefix must be available to
> BH> lilypond-book when it generates this code.
>
> This seems a little baroque (in the bad sense) to me. Why not just
> run "lilypond -H title test.ly" and get test.title, which you can then
> include quite easily?
>
--
Bernard Hurley <[EMAIL PROTECTED]>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
On Sun, 2005-11-27 at 18:38 -0500, Michael Haynie wrote: > The change to \preLilypondExample can be made backward compatible by > defining a variable that preLilypondExample can rely on -- it's a bit > of a hack, though. Using a parameter might be worth a little breakage, > since there will not likely be a huge number of places to edit. > No it can't be made backward compatible like that, since an optional parameter has to be declared in the definition of a macro, what lilypond-book generates is a _call_ to the macro. However (I hadn't thought of this in my previous post) you can get backward compatibility by adding another command line option for lilypond-book > One thing, though: using 2.6.4 (on Mac OS X, at least), lilypond-book > seems to insist on parsing the --process arguments, and so complains > that -b isn't a valid option. If a patch is possible against 2.6, that > should also be corrected. > That looks like a bug to me. It doesn't happen using 2.6.3 on Debian. Are you sure you quoted the arguments correctly? Check it again and if it still doesn't work email the bug list > I'll be delighted to test the patch. > Thanks, I have been working with 2.7.x, but I don't think lilypond-book has changed much so I'll see what I can do! > -- Bernard Hurley <[EMAIL PROTECTED]> ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting header fields for use by e.g. LaTeX?
On Nov 27, 2005, at 9:36 PM, Bernard Hurley wrote: On Sun, 2005-11-27 at 18:38 -0500, Michael Haynie wrote: The change to \preLilypondExample can be made backward compatible by defining a variable that preLilypondExample can rely on -- it's a bit of a hack, though. two different ideas here -- global variable above, parameter below. Sorry about that. Using a parameter might be worth a little breakage, since there will not likely be a huge number of places to edit. No it can't be made backward compatible like that, since an optional parameter has to be declared in the definition of a macro, what lilypond-book generates is a _call_ to the macro. However (I hadn't thought of this in my previous post) you can get backward compatibility by adding another command line option for lilypond-book Having lilypond-book write two different forms of the call might be OK. One thing, though: using 2.6.4 (on Mac OS X, at least), lilypond-book seems to insist on parsing the --process arguments, and so complains that -b isn't a valid option. If a patch is possible against 2.6, that should also be corrected. That looks like a bug to me. It doesn't happen using 2.6.3 on Debian. Are you sure you quoted the arguments correctly? Check it again and if it still doesn't work email the bug list I did, it doesn't, and I will. I'll be delighted to test the patch. Thanks, I have been working with 2.7.x, but I don't think lilypond-book has changed much so I'll see what I can do! -- Bernard Hurley <[EMAIL PROTECTED]> ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Hammer-Ons and Pull-Offs
Can someone please tell me how I might be able to remove the "H" and "P" from slurs in tablature? Also, is there a way to change the angle of a gliss line? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
