Re: using Scholarly?

[N. Andrew Walsh]

Hi Urs,

I solved my issue by adding the full path to one of my .ily files and including that at the top of the master. Now it works great. Such a nice system!

Now: would these colors be preserved in a printed PDF output? How can I change them? It's nice to have them in frescobaldi's preview window, but I don't want them in a printed output (which, ultimately, this score will have to be).

Second question: is there a way to know which grobs can be used as the last argument? In examples, it's things like "DynamicText" or "NoteHead". But I'm not sure what other grobs can be specified. Any at all? Or are there limits?

Cheers,

A

On Thu, May 14, 2015 at 4:31 PM, Urs Liska <address@hidden> wrote:

Am 14.05.2015 um 15:07 schrieb N. Andrew Walsh:

So, I really want to use ScholarLy for my current project (the OE has typos and mistakes, they need to be noted, etc). 

I cloned the entire git repository into a subdirectory of my ~/.lilypond directory, and have the following in my master .ly file for the project:

\include "openlilylib"

\useLibrary Scholarly

\useModule scholarly.annotate

In my .ly file for music, I have the following:

\musicalIssue \with {

author = "me"

message = "Typfehler"

source = "Fascimile der Stimme"

}

NoteHead %% Typo noted, Bar 32

  c

This is inside a \Voice block. Compiling fails, complaining that the string is unrecognized. The \musicalIssue tag also does not show up on the auto-complete dropdown in frescobaldi.

So, it isn't working for me. What am I doing wrong?

I can't tell for sure if I don't see the actual file and/or at least the full error message.
But if I take your report literally you have to add openLilyLib to LilyPond's include path - which you'll do in the Frescobaldi preferences.

Currently you'll have to add *two* directories there, namely openLilyLib's root directory plus the ly directory inside that. Someday, when the migration has completed the root won't be necessary anymore.

Frescobaldi doesn't know about openLilyLib's keywords, so you won't get any syntax highlighting either. Maybe I'll be able to do something about that in the future, but originally Frescobaldi claims to support the full syntax of the current stable version of LilyPond.

If that doesn't help you out please send the relevant part of the error messages completely (for example I would suspect that LilyPond already doesn't find "openlilylib").

Best
Urs

Cheers,

A

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user