Re: Custom dynamic vertical positioning

2015-10-19 Thread Malte Meyn
Am 20.10.2015 um 07:59 schrieb Andrew Bernard: When making a simple custom dynamic, a p followed by an em dash, compared to the same thing for a p followed by a hyphen, the vertical alignment differs. What am I doing wrong, or not understanding? I thought the alignment of the two in the same

Custom dynamic vertical positioning

2015-10-19 Thread Andrew Bernard
When making a simple custom dynamic, a p followed by an em dash, compared to the same thing for a p followed by a hyphen, the vertical alignment differs. What am I doing wrong, or not understanding? I thought the alignment of the two in the same context would be identical. [I have pasted a unic

Re: [OT] Printer with or without Postscript

2015-10-19 Thread David Wright
Quoting Johan Vromans (jvrom...@squirrel.nl): > On Mon, 19 Oct 2015 10:59:42 -0500 > David Wright wrote: > > > A very common workflow but IMO a very poor one. If you have problems > > printing, where do you start looking for the cause? (for example, > > artifacts like those in the right side of y

Serpent Publications

2015-10-19 Thread Simon Albrecht
Hello Laura, I just had a look at your collection. Very nice project you have there! I like the concept of using parts and retaining the original ‘measure notation’. (Personally, I also think we might gain a lot by just turning to use the traditional c clefs ag

Re: Emacs lilypond-mode

2015-10-19 Thread David Kastrup
Laura Conrad writes: >> "Simon" == Simon Albrecht writes: > > Simon> On 19.10.2015 18:01, Laura Conrad wrote: > >> The problem is > >> when entering long note values, which are common in early 16th century > >> music, I have to leave the keypad to type \breve and \longa > >

Re: Emacs lilypond-mode

2015-10-19 Thread Laura Conrad
> "Simon" == Simon Albrecht writes: Simon> On 19.10.2015 18:01, Laura Conrad wrote: >> The problem is >> when entering long note values, which are common in early 16th century >> music, I have to leave the keypad to type \breve and \longa Simon> Except you’d enter it with

Re: Emacs lilypond-mode

2015-10-19 Thread Simon Albrecht
On 19.10.2015 18:01, Laura Conrad wrote: The problem is when entering long note values, which are common in early 16th century music, I have to leave the keypad to type \breve and \longa Except you’d enter it with shortened note values (say to 1/4) and use e.g. the Frescobaldi Rhythm Tools to

Re: [OT] Printer with or without Postscript

2015-10-19 Thread Johan Vromans
On Mon, 19 Oct 2015 10:59:42 -0500 David Wright wrote: > A very common workflow but IMO a very poor one. If you have problems > printing, where do you start looking for the cause? (for example, > artifacts like those in the right side of your lpev.png). > > I only ever print from applications to

Re: Emacs lilypond-mode

2015-10-19 Thread David Kastrup
Laura Conrad writes: >> "David" == David Kastrup writes: > > David> What it does do is trying to track the current "tonality". > David> That's an interesting idea but requires an editing mode that > David> will _propagate_ corrections in order to work nicely. Of > David> cou

Re: Emacs lilypond-mode

2015-10-19 Thread Laura Conrad
> "David" == David Kastrup writes: David> What it does do is trying to track the current "tonality". David> That's an interesting idea but requires an editing mode that David> will _propagate_ corrections in order to work nicely. Of David> course, the same will be needed in o

Re: [OT] Printer with or without Postscript

2015-10-19 Thread David Wright
Quoting Johan Vromans (jvrom...@squirrel.nl): > On Tue, 13 Oct 2015 21:17:19 +1100 > Andrew Bernard wrote: > > > I am not convinced evince is very good at anything at all. Would this not > > be an issue with evince, rather than other parts of the toolchain? > > That could very well be the case.

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

2015-10-19 Thread David Kastrup
Paul Morris writes: >> On Oct 19, 2015, at 10:59 AM, David Kastrup wrote: >> >> Paul Morris writes: >>> >>> That did the trick and now it works, thanks! >>> >>> \version “2.19.22” >>> >>> myfunc = >>> #(define-music-function () () >>> #{ >>> \context Staff >>> \applyContext >>>

Re: any slur after-line-breaking [automated] hacks?

2015-10-19 Thread Simon Albrecht
On 19.10.2015 04:47, Kieren MacMillan wrote: a great number of trial-and-error adjustment+compilation cycles Well, \shapeII by Janek in openlilylib does offer the facility of giving a list of lists for each of the siblings of a broken bezier (that’s not documented, IIRC), like: \shapeII #'((

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

2015-10-19 Thread Paul Morris
> On Oct 19, 2015, at 10:59 AM, David Kastrup wrote: > > Paul Morris writes: >> >> That did the trick and now it works, thanks! >> >> \version “2.19.22” >> >> myfunc = >> #(define-music-function () () >> #{ >> \context Staff >> \applyContext >> #(lambda (context) >>;; a

Re: ScholarLy newbie, running annotate.ly, gets error message

2015-10-19 Thread Graham King
On Mon, 2015-10-19 at 16:48 +0200, Urs Liska wrote: > > > > Am 19.10.2015 um 16:36 schrieb Urs Liska: > > > > > You didn't do anything wrong but stumbled over a stupid bug I didn't > > have the time to look into. It seems that at some point I have > > reversed the logic of an 'if' statement s

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

2015-10-19 Thread David Kastrup
Paul Morris writes: >> On Oct 19, 2015, at 1:56 AM, David Kastrup wrote: >> >> I think your main problem is that you are using \applyContext here at >> Voice level where it does not really do anything worthwhile. > > Ah, I see. > >> Try \context Staff \applyContext … > > That did the trick and

Re: ScholarLy newbie, running annotate.ly, gets error message

2015-10-19 Thread Urs Liska
Am 19.10.2015 um 16:53 schrieb David Kastrup: > Urs Liska writes: > >> Am 19.10.2015 um 16:36 schrieb Urs Liska: >>> You didn't do anything wrong but stumbled over a stupid bug I didn't >>> have the time to look into. It seems that at some point I have >>> reversed the logic of an 'if' statement

Re: ScholarLy newbie, running annotate.ly, gets error message

2015-10-19 Thread David Kastrup
Urs Liska writes: > Am 19.10.2015 um 16:36 schrieb Urs Liska: >> You didn't do anything wrong but stumbled over a stupid bug I didn't >> have the time to look into. It seems that at some point I have >> reversed the logic of an 'if' statement so it spits out that error >> when everything is OK. >

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

2015-10-19 Thread Paul Morris
> On Oct 19, 2015, at 1:56 AM, David Kastrup wrote: > > I think your main problem is that you are using \applyContext here at > Voice level where it does not really do anything worthwhile. Ah, I see. > Try \context Staff \applyContext … That did the trick and now it works, thanks! \version “2

Re: ScholarLy newbie, running annotate.ly, gets error message

2015-10-19 Thread Urs Liska
Am 19.10.2015 um 16:36 schrieb Urs Liska: > You didn't do anything wrong but stumbled over a stupid bug I didn't > have the time to look into. It seems that at some point I have > reversed the logic of an 'if' statement so it spits out that error > when everything is OK. > > So if the results are

Re: ScholarLy newbie, running annotate.ly, gets error message

2015-10-19 Thread Urs Liska
You didn't do anything wrong but stumbled over a stupid bug I didn't have the time to look into. It seems that at some point I have reversed the logic of an 'if' statement so it spits out that error when everything is OK. So if the results are what you expect please ignore *this* kind of error mes

ScholarLy newbie, running annotate.ly, gets error message

2015-10-19 Thread Graham King
excuse the haiku! In my first attempt at using ScholarLy, I'm trying to compile the supplied example, openlilylib/ly/scholarly/usage-examples/annotate.ly The include path for Frescobaldi 2.18.1 is: /Users/grahamk/Documents/lilypond/include_gk /Users/grahamk/Documents/lilypond/mus

Prall and trill in "articulate" script

2015-10-19 Thread Gilles
Hello. It's the first time I use the "\articulate" command. Very nice improvement on the plain MIDI rendering! Two remarks: 1. "prall" is interpreted in a way that (IMO) better corresponds to "prallprall" (which itself is not implemented). [A comment in the code indicates that the "inverte