Re: Edition Engraver suppress log files

Am 14. Oktober 2018 08:29:46 MESZ schrieb Jan-Peter Voigt : >Hi Craig, > >not right now, but I will implement a switch ASAP! > Please use the \setOption syntax for that. >Jan-Peter > >Am 14. Oktober 2018 07:30:44 MESZ schrieb Craig Dabelstein >: >>Hi all, >> >>Quick question: Is it possible to

Re: Edition Engraver suppress log files

Hi Craig, not right now, but I will implement a switch ASAP! Jan-Peter Am 14. Oktober 2018 07:30:44 MESZ schrieb Craig Dabelstein : >Hi all, > >Quick question: Is it possible to stop the edition-engraver creating >log >files? > >Craig > > >-- >*Craig Dabelstein* >Maxime's Music >craig.dabelst.

Edition Engraver suppress log files

Hi all, Quick question: Is it possible to stop the edition-engraver creating log files? Craig -- *Craig Dabelstein* Maxime's Music craig.dabelst...@gmail.com *http://maximesmusic.com * ___ lilypond-user mailing list lilypond-

Re: Instructions to install lilypond onto Raspberry Pi

That would be grand if you could send that to me, please! would I just have to install the package that you send following that ? -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org htt

Re: GrandStaff vertical distance

Lukas-Fabian Moser wrote > I disagree that LP does not follow the standard engraving rules. It just > seems to me that \new GrandStaff etc. imply a certain semantics which is > perfectly alright for, e.g., an orchestral Piano part, but just does not > apply for the braces connecting Violin 1 and

Re: Define new articulation with markup or path (instead of glyph)

Hi Aaron, althought this has long left the original thread's purpose I find this extremely interesting. Would you be interested in adding some content to https://scheme-book.ursliska.de, maybe somewhere below https://scheme-book.ursliska.de/scheme/lists/? There is always need for explanations

Re: Define new articulation with markup or path (instead of glyph)

On 2018-10-13 12:29 am, Aaron Hill wrote: According to the docs [1], assoc-set! (and family) may modify the original alist. So whether a copy is made or not depends on an implementation detail. Near as I can tell, the original alist is modified in-place when the key is found within. But when t

Re: GrandStaff vertical distance

Hi, Awesome! Thank you very much Lukas for this handy solution. I wonder why you have added two occurences for the barline (barlineOnly & barline) ? I thought it might be convenient: Since brace, bracket and square _imply_ that a barline is printed, it seemed more logical to me if you can writ

Re: Define new articulation with markup or path (instead of glyph)

On 2018-10-13 12:01 am, Urs Liska wrote: Hi Harm, Am 13.10.2018 um 01:18 schrieb Thomas Morley: Hi Urs, Am Sa., 13. Okt. 2018 um 00:00 Uhr schrieb Urs Liska : %% Not sure if needed, though, better be paranoid and work on a copy of %% default-script-alist to avoid possible bleed-over. #(d

Re: Markup and Score from scheme function

Add-text is even better. Still curious if it's possible to get the "context" inside the function. Isn't that what the location parameter is for? Thomas Morley schrieb am Fr., 12. Okt. 2018, 10:29: > Am Fr., 12. Okt. 2018 um 08:10 Uhr schrieb Jan-Peter Voigt < > jp.vo...@gmx.de>: > > > > Hello Se

Re: Define new articulation with markup or path (instead of glyph)

Hi Harm, Am 13.10.2018 um 01:18 schrieb Thomas Morley: Hi Urs, Am Sa., 13. Okt. 2018 um 00:00 Uhr schrieb Urs Liska : %% Not sure if needed, though, better be paranoid and work on a copy of %% default-script-alist to avoid possible bleed-over. #(define my-script-alist default-script-alist)