Re: ScholarLY

[Urs Liska]

Am 17.10.2018 um 03:00 schrieb Craig Dabelstein:

Hi all,

Is this the right code to use to turn off the colors in ScholarLy? I'm 
using the latest version, but I'm using the \editorialMarkup commands.


This line is having no effect. I'm sure I'm doing something wrong 
somewhere.


\setOption scholarly.annotate.use-colors ##f


Does it really have *no* effect? I can't reproduce that, so you should 
provide a MWE.

However, what you will probably want to do in addition is

\setOption stylesheets.span.use-colors ##f

because the span provides its own coloring. Concretely: the span colors 
the whole annotated music expression while the annotation colors the 
*anchor* element *on top* of that.


HTH
Urs



Craig

--
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com 
/http://maximesmusic.com/


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

ScholarLY

[Craig Dabelstein]

Hi all,

Is this the right code to use to turn off the colors in ScholarLy? I'm
using the latest version, but I'm using the \editorialMarkup commands.

This line is having no effect. I'm sure I'm doing something wrong somewhere.

\setOption scholarly.annotate.use-colors ##f

Craig

-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Edition Engraver suppress log files

[Craig Dabelstein]

No problem. Thank you Jan-Peter.

On Tue., 16 Oct. 2018, 6:49 pm Jan-Peter Voigt,  wrote:

> Hi Craig,
>
> I merged to master, but added a comment, that the names of the option
> and the file will change, like Urs and I discussed.
>
> This change shall be integrated soon, but right now I have to do some
> other jobs with higher priority.
>
> Jan-Peter
>
>
> Am 15.10.2018 um 22:00 schrieb Craig Dabelstein:
> > The new branch worked perfectly for me Jan-Peter.
> >
> > Craig
> >
> >
> > On Mon, 15 Oct 2018 at 21:53, Craig Dabelstein
> > mailto:craig.dabelst...@gmail.com>> wrote:
> >
> > You two are amazing. I don't know where any of us would be without
> you.
> >
> > Craig
> >
> > On Mon., 15 Oct. 2018, 7:19 pm Jan-Peter Voigt,  > > wrote:
> >
> > Am 15.10.2018 um 11:13 schrieb Urs Liska:
> > >
> > >
> > > Am 15.10.2018 um 11:07 schrieb Jan-Peter Voigt:
> > >> Hi Urs,
> > >>
> > >> I combine the answers:
> > >> The *.edition.log file might be named differently - not .log
> > - as this
> > >> file has a purpose outside the debug-log realm. And this is
> > the reason
> > >> I'd vote against writing the edition-context-information in a
> > global log
> > >> file.
> > >
> > > Yes, that points in the right direction. In that sense the EE
> > "log" is
> > > comparable to scholarLY's export files.
> > >
> > >> But for all debug-logs piping them into one (optional) files
> > makes
> > >> absolutely sense. How this file should be formatted is
> > another question.
> > >> And sometimes it is helpful if the log is written before Lily
> > crashes
> > >> ;-) so it might be worth writing immediatly.
> > >
> > > That's also true, and I had thought about this. But with your
> > previous
> > > comment we can solve the issue. If we're separating package
> > specific
> > > export files from traditional logs the logs don't have to be
> > sectioned.
> > > So we can format them similarly to usual log files, have a
> package
> > > identifier at the beginning of each entry and simply write
> > them out
> > > immediately.
> > >
> > > And if I think of it, most of that is already implemented in
> > oll-core.
> > > There we have the functions  oll:log, oll:debug, oll:warn
> > etc., combined
> > > with the possibility to set the log-level. The only things
> > we'd need is
> > > the option to write the log or not, and the tagging of
> > messages with the
> > > package prefix.
> > >
> > > So I suggest you rename both the export filename and the
> > option in the
> > > EE, and we'll do the other thing separately.
> > > OK I'll do that later and will think about the edition-context
> > file
> > structure. The paths shall be copyable ...
> >
> > Jan-Peter
> >
> >
> >
> > --
> > *Craig Dabelstein*
> > Maxime's Music
> > craig.dabelst...@gmail.com 
> > /http://maximesmusic.com/
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Edition Engraver suppress log files

[Jan-Peter Voigt]

Hi Craig,

I merged to master, but added a comment, that the names of the option
and the file will change, like Urs and I discussed.

This change shall be integrated soon, but right now I have to do some
other jobs with higher priority.

Jan-Peter


Am 15.10.2018 um 22:00 schrieb Craig Dabelstein:
> The new branch worked perfectly for me Jan-Peter.
> 
> Craig
> 
> 
> On Mon, 15 Oct 2018 at 21:53, Craig Dabelstein
> mailto:craig.dabelst...@gmail.com>> wrote:
> 
> You two are amazing. I don't know where any of us would be without you.
> 
> Craig
> 
> On Mon., 15 Oct. 2018, 7:19 pm Jan-Peter Voigt,  > wrote:
> 
> Am 15.10.2018 um 11:13 schrieb Urs Liska:
> >
> >
> > Am 15.10.2018 um 11:07 schrieb Jan-Peter Voigt:
> >> Hi Urs,
> >>
> >> I combine the answers:
> >> The *.edition.log file might be named differently - not .log
> - as this
> >> file has a purpose outside the debug-log realm. And this is
> the reason
> >> I'd vote against writing the edition-context-information in a
> global log
> >> file.
> >
> > Yes, that points in the right direction. In that sense the EE
> "log" is
> > comparable to scholarLY's export files.
> >
> >> But for all debug-logs piping them into one (optional) files
> makes
> >> absolutely sense. How this file should be formatted is
> another question.
> >> And sometimes it is helpful if the log is written before Lily
> crashes
> >> ;-) so it might be worth writing immediatly.
> >
> > That's also true, and I had thought about this. But with your
> previous
> > comment we can solve the issue. If we're separating package
> specific
> > export files from traditional logs the logs don't have to be
> sectioned.
> > So we can format them similarly to usual log files, have a package
> > identifier at the beginning of each entry and simply write
> them out
> > immediately.
> >
> > And if I think of it, most of that is already implemented in
> oll-core.
> > There we have the functions  oll:log, oll:debug, oll:warn
> etc., combined
> > with the possibility to set the log-level. The only things
> we'd need is
> > the option to write the log or not, and the tagging of
> messages with the
> > package prefix.
> >
> > So I suggest you rename both the export filename and the
> option in the
> > EE, and we'll do the other thing separately.
> > OK I'll do that later and will think about the edition-context
> file
> structure. The paths shall be copyable ...
> 
> Jan-Peter
> 
> 
> 
> -- 
> *Craig Dabelstein*
> Maxime's Music
> craig.dabelst...@gmail.com 
> /http://maximesmusic.com/


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user