I placed it after mu version statement but it threw a lot of errors and
clashed with about fifteen other calls in my file.
I am not asking anyone to help me debug that, dont worry, I take your
word for it it works, but it is a good example to add the compiled pdfs
to the manual sources. If I didnt use this group and downloaded it I
would have given up as I would not know if it is worth to debug why it
doesnt work in my lilypond file.
The pdf manuals would have given me the extra initiative to do the
efoort and debug as I know what I can get seeing it in the pdf manual..
Just a remark (IMHO common sense).
Thanks, you guys gave me two great ways to do Analysis markups and you
do not deserve criticism. Criticism it is not as I have a valid point to
have way more people using this great unit.
So the problem is solved, thanks all for the great help.
On 2018-08-06 16:41, ma...@masonhock.com wrote:
On 08/06, liebre...@grossmann-venter.com wrote:
I dont want to go through the process of installing a package
You don't need to install anything. Just put
"roman_numeral_analysis_tool.ily" in the same directory as your
lilypond file, and put
\include "roman_numeral_analysis_tool.ily"
in your lilypond file after your version statement.
and then find
it is not what I need.
Having already started using it, I'm pretty sure it's what you want.
It does everything the lsr snippet does and adds some additional
functionality.
Mason
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
