Re: Scheme question

Am Dienstag, den 14.01.2020, 17:20 -0800 schrieb Aaron Hill: > On 2020-01-14 5:11 pm, Arle Lommel wrote: > > Is that feature explained anywhere in the documentation? I don’t > > recall seeing anything like that anywhere and searching for > > “quasi-quote scheme Lilypond” doesn’t return anything

Re: Trying to locate files

On Wed, Jan 15, 2020 at 12:33 AM Aaron Hill wrote: > On 2020-01-14 9:27 pm, Freeman Gilmore wrote: > > On Wed, Jan 15, 2020 at 12:19 AM Aaron Hill > > wrote: > > > >> On 2020-01-14 8:53 pm, Freeman Gilmore wrote: > >> > On Tue, Jan 14, 2020 at 11:04 PM Aaron Hill > > >> > wrote: > >> > > >> >>

Re: Trying to locate files

On 2020-01-14 9:27 pm, Freeman Gilmore wrote: On Wed, Jan 15, 2020 at 12:19 AM Aaron Hill wrote: On 2020-01-14 8:53 pm, Freeman Gilmore wrote: > On Tue, Jan 14, 2020 at 11:04 PM Aaron Hill > wrote: > >> On 2020-01-14 7:47 pm, Freeman Gilmore wrote: >> > What is the name of the file that

Re: Trying to locate files

On 2020-01-14 8:53 pm, Freeman Gilmore wrote: On Tue, Jan 14, 2020 at 11:04 PM Aaron Hill wrote: On 2020-01-14 7:47 pm, Freeman Gilmore wrote: > What is the name of the file that translate text to Unicode? I am uncertain about this ask. Could you expand on it? It is my understanding that

Re: Distance of a grob from its reference point

Hi all, On Jan 14, 2020, at 10:50 PM, Aaron Hill wrote: > I very much need LilyPond to be able to make the smart decisions on my behalf. Me, too. > That is why I am trying to defend getting the automatic parts working better I think that’s an important goal. > I would disagree with the

Re: Unusual cross-staff stem in Bartók

Hi Andrew, > Not at all uncommon. Agreed. > for the case with the notehead on the opposite, you now have lots o good > solutions. Well… I wouldn’t necessarily call my hack a good solution. It would be nice to have some syntactic sugar that would handle these kinds of cases gracefully,

Re: Trying to locate files

On 2020-01-14 7:47 pm, Freeman Gilmore wrote: Is there a file like makam.ly for the standard accidentals? If so what is its name? You should review lily-library.scm (near the top) and define-note-names.scm, as those files contain the functional equivalent to makam.ly. What is the name of

Re: Distance of a grob from its reference point

From: Paolo Prete Date: Tuesday, January 14, 2020 at 8:10 PM To: Aaron Hill Cc: Lilypond-User Mailing List Subject: Re: Distance of a grob from its reference point I really can't count how many times I had to to that in so many scores. And there's no way to do that automagically. Really

Re: Distance of a grob from its reference point

On 2020-01-14 7:10 pm, Paolo Prete wrote: On Tue, Jan 14, 2020 at 9:08 PM Aaron Hill wrote: I am not connected to the world of modern notation, but I cannot envision any musical meaning for the exact vertical position of an OttavaBracket. This is not true. There are many and many cases in

Re: Syntax highlighting

Federico, Is it just me or is the documentation for Pygments really hard to understand? I can't even find anywhere they discuss the setup.py file. I've opened a repo (https://github.com/craigdab/pygments-lilypond-test) and cut and paste from other peoples repositories as a start, but I really

Re: # and $ (was Re: metronome-mark-alignment)

Aaron Hill writes: > On 2020-01-14 5:18 pm, David Kastrup wrote: >> No, it's that \notes is identical to $notes (apart from the syntax) in >> that it creates a copy. So whenever you write \something and do >> something with it, whatever you do with it will not affect the original >> stuff

RE: Three short questions from Bartók around fingering, about 90% there

Arle, Very welcome. Had the same issue in a Mozart Piano Sonata and someone on the list provided the commands. Mark From: Arle Lommel [mailto:arle.lom...@gmail.com] Sent: Tuesday, January 14, 2020 5:02 PM To: Mark Stephen Mrotek Cc: Lilypond-User Mailing List Subject: Re: Three

Re: # and $ (was Re: metronome-mark-alignment)

On 2020-01-14 5:18 pm, David Kastrup wrote: No, it's that \notes is identical to $notes (apart from the syntax) in that it creates a copy. So whenever you write \something and do something with it, whatever you do with it will not affect the original stuff stored in the Scheme variable

Re: Scheme question

On 2020-01-14 5:11 pm, Arle Lommel wrote: Is that feature explained anywhere in the documentation? I don’t recall seeing anything like that anywhere and searching for “quasi-quote scheme Lilypond” doesn’t return anything relevant. If it isn’t there, this seems like rather a nice thing to have

Re: # and $ (was Re: metronome-mark-alignment)

Aaron Hill writes: > On 2020-01-14 2:39 pm, David Kastrup wrote: >> Ok, let me try again. >> # and $ differ in several respects. # inserts Scheme constructs in >> places where LilyPond can decide how they fit into its syntax without >> looking at their value first. In that case, evaluation of

Re: Scheme question

> Since you have a variable, you would need the quasi-quote feature if you > wanted the shorthand: `(,padding . 0) But, (cons padding 0) should > work. > > > -- Aaron Hill Thank you, Aaron. The quasi-quote version did it. Is that feature explained anywhere in the documentation? I don’t

Re: Scheme question

On 2020-01-14 5:01 pm, Arle Lommel wrote: I am a total neophyte to Scheme, but not to coding. I’ve written a simple function, but it does not work (I’ve reduced it to just the problematic lines. Can anyone tell me how to write the line indicated below? shifter = #(define-music-function

Re: Three short questions from Bartók around fingering, about 90% there

> On Jan 14, 2020, at 18:05, Mark Stephen Mrotek wrote: > > Arle, > > Add these before the b! > > \once \override Accidental.extra-offset = #'(3 . 0) > \once \override NoteColumn.force-hshift = #2.5 > > Mark Thanks. I’m finding I have to play around with the numbers a bit and add an

Scheme question

I am a total neophyte to Scheme, but not to coding. I’ve written a simple function, but it does not work (I’ve reduced it to just the problematic lines. Can anyone tell me how to write the line indicated below? shifter = #(define-music-function (parser location padding) (number?) #{

Re: Distance of a grob from its reference point

On Tue, Jan 14, 2020 at 10:10 PM kieren_macmillan kieren_macmillan < kieren_macmil...@sympatico.ca> wrote: > Hi Paolo (et al.), > > > Why do I need to move a grob? > > For the simple fact that any score, in order to have a * professional * > > appearance, needs HUNDREDS of these adjustments. > >

Re: Syntax highlighting

Thank you gentlemen, I'll have a go at taking the python-ly work and seeing if I can use it work to make syntax highlighting with pygments. It's highly possible that I will totally fail, but I'll give it a try. Craig On Tue, 14 Jan 2020 at 23:38, Federico Bruni wrote: > Il giorno mar 14 gen

Extending manual (was Re: metronome-mark-alignment)

> -Original Message- > From: David Kastrup [mailto:d...@gnu.org] > Sent: Tuesday, January 14, 2020 5:39 PM > To: Thomas Morley > Cc: Daniel Rosen ; lilypond-user Mailing List (lilypond- > u...@gnu.org) ; David Nalesnik > > Subject: Re: metronome-mark-alignment > > > Ok, let me try

Re: metronome-mark-alignment

Thomas Morley writes: > Am Di., 14. Jan. 2020 um 23:39 Uhr schrieb David Kastrup : >> >> Thomas Morley writes: >> >> > Am Mo., 13. Jan. 2020 um 07:14 Uhr schrieb Daniel Rosen >> > : >> >> >> >> > The hash mark # method of embedding Scheme is a natural fit for this >> >> > system. >> >> > Once

# and $ (was Re: metronome-mark-alignment)

On 2020-01-14 2:39 pm, David Kastrup wrote: Ok, let me try again. # and $ differ in several respects. # inserts Scheme constructs in places where LilyPond can decide how they fit into its syntax without looking at their value first. In that case, evaluation of those Scheme expressions is done

Re: metronome-mark-alignment

Am Di., 14. Jan. 2020 um 23:39 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Mo., 13. Jan. 2020 um 07:14 Uhr schrieb Daniel Rosen > > : > >> > >> > The hash mark # method of embedding Scheme is a natural fit for this > >> > system. > >> > Once the lexer sees a hash mark, it

RE: Three short questions from Bartók around fingering, about 90% there

Arle, Add these before the b! \once \override Accidental.extra-offset = #'(3 . 0) \once \override NoteColumn.force-hshift = #2.5 Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Arle Lommel Sent: Tuesday, January 14, 2020 2:30

Re: metronome-mark-alignment

Thomas Morley writes: > Am Mo., 13. Jan. 2020 um 07:14 Uhr schrieb Daniel Rosen : >> >> > The hash mark # method of embedding Scheme is a natural fit for this >> > system. >> > Once the lexer sees a hash mark, it calls the Scheme reader to read one >> > full Scheme >> > expression (this can be

Re: Running LilyPond on Amazon Linux 2

I know I’m not the first to run LilyPond in a Lambda function. For instance, LilyBin (http://lilybin.com ) has been using Lambda and S3 for a while to power their website. I took some cues from their site (which is open source on Github), but ultimately went my own route

Re: Unusual cross-staff stem in Bartók

Hi Arie, Not at all uncommon. In the New Complexity scores that I engrave for a colleague composer we have this continuously, in the piano music. It's actually a fairly standard modernist notation, and true enough indicates the distribution of hands but also that this is a single dyadic chord

Re: metronome-mark-alignment

Am Mo., 13. Jan. 2020 um 07:14 Uhr schrieb Daniel Rosen : > > > -Original Message- > > From: Thomas Morley [mailto:thomasmorle...@gmail.com] > > Sent: Sunday, January 12, 2020 6:04 PM > > To: Daniel Rosen > > Cc: David Nalesnik ; lilypond-user Mailing List > > (lilypond-user@gnu.org) > >

Re: Distance of a grob from its reference point

Hi Paolo (et al.), > Why do I need to move a grob? > For the simple fact that any score, in order to have a * professional * > appearance, needs HUNDREDS of these adjustments. > Even the simplest ones. I think we all agree on that. Now… At one end of a philosophical spectrum lies the point

Re: Distance of a grob from its reference point

Sorry, broken link Here's the correct one: https://filebin.net/sy6z7b39fcounb5j > > I am a convinced open source developer and already 10 years ago I used > Lilypond to create my scores, because I wanted to avoid Finale, Sibelius > and other proprietary software (which I used before). In the

Re: Distance of a grob from its reference point

Hi Aaron, thanks for the detailed reply. Why do I need to move a grob? For the simple fact that any score, in order to have a * professional * appearance, needs HUNDREDS of these adjustments. Even the simplest ones. I am a convinced open source developer and already 10 years ago I used Lilypond

Re: Distance of a grob from its reference point

Hi Aaron, > > My mind was a little blown by the result of changing that to > You and me both. Well, that at least makes me feel a little better. #miserylovescompany > > Hence the ability to offset (e.g.) an OttavaBracket precisely X staff > > spaces while still [re-]engaging the spacing engine

Re: Distance of a grob from its reference point

On 2020-01-14 7:16 am, Kieren MacMillan wrote: My mind was a little blown by the result of changing that to \override $grob-path .before-line-breaking = #proc Doing so made it *deeply* and *immediately* clear that, despite being a serious power-user of Lilypond for almost twenty years, I

Re: hide Stuff

Thank you very much for the detailed examples. I think I can make it now. regards

Re: Running LilyPond on Amazon Linux 2

I'm curious to know about your use case/workflow for running Lilypond in AWS Lambda. Seems interesting. Saul On Tue, Jan 14, 2020, 6:34 AM Peter Anglea wrote: > I think I got it fixed… recording this here for anyone else who stumbles > upon the same issue as I did. > > I downloaded an RPM

Re: Unusual cross-staff stem in Bartók

> The more things interact unnecessarily, the harder it becomes doing > things reliably. The more we manage to get LilyPond to behave to naive > expectations, the more useable power the average user has at their > convenience. > > So we should not try overexercising the "music is complex, so

Re: Getting readline to work in scheme-sandbox

This is weird. Seems that strace does not recognize the shebang in the lilypond script. Could you please to try to execute the steps in the startup script directly? I assume you used the vanilla lilypond installer and installed to your home directory /home/knute/: export

Re: Unusual cross-staff stem in Bartók

Arle Lommel writes: >> Hope that helps more! >> Kieren. > > > Thanks much. One of the challenging things for folks like me who dip > in and out is keeping track of all the different ways that things can > be done and how all the elements interact. But that is inherent to > this: Music notation

Re: Getting readline to work in scheme-sandbox

It looks like I get an error in strace. The sandbox is never executed: execve("/home/knute/bin/lilypond", ["lilypond", "scheme-sandbox.ly"], 0x7ffe4792c428 /* 53 vars */) = -1 ENOEXEC (Exec format error) strace: exec: Exec format error +++ exited with 1 +++ --- Knute Snortum (via Gmail) On

Re: Unusual cross-staff stem in Bartók

> Hope that helps more! > Kieren. Thanks much. One of the challenging things for folks like me who dip in and out is keeping track of all the different ways that things can be done and how all the elements interact. But that is inherent to this: Music notation is orders of magnitude more

Re: How to increase shift dynamic and end of hairpin

Kieren MacMillan writes: > Hi David, > >> It's kind of embarrassing after that accolade that this particular >> solution (the \after function) is probably the least brilliant and >> involved of all. > > Sometimes, the most brilliant solutions are the most elegant ones. In > particular, your

Re: Distance of a grob from its reference point

Hi Aaron, > If we borrow some of the underlying logic, we get the following: Wow… You are my patronus of late. =) > #{ \override $grob-path .after-line-breaking = #proc #}) My mind was a little blown by the result of changing that to \override $grob-path .before-line-breaking = #proc

Re: How to increase shift dynamic and end of hairpin

Hi David, > It's kind of embarrassing after that accolade that this particular > solution (the \after function) is probably the least brilliant and > involved of all. Sometimes, the most brilliant solutions are the most elegant ones. In particular, your \after function was the first time I ever

Re: Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

Carl Sorensen writes: > On 1/14/20, 6:58 AM, "Arle Lommel" wrote: > > So schrieb David: > > > Either way is acting as it should. > > > > The manual has an index entry "beam, with lyrics" for the chapter > > "Setting automatic beam behavior" but there is no usable

Re: Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

On 1/14/20, 6:58 AM, "Arle Lommel" wrote: So schrieb David: > Either way is acting as it should. > > The manual has an index entry "beam, with lyrics" for the chapter > "Setting automatic beam behavior" but there is no usable reference > whatsoever in that

Re: Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

Arle Lommel writes: > So schrieb David: > >> Either way is acting as it should. >> >> The manual has an index entry "beam, with lyrics" for the chapter >> "Setting automatic beam behavior" but there is no usable reference >> whatsoever in that chapter. I actually find rather little elsewhere

Re: Running LilyPond on Amazon Linux 2

I think I got it fixed… recording this here for anyone else who stumbles upon the same issue as I did. I downloaded an RPM containing libcrypt.so.1, extracted the file, and put it inside LilyPond’s /usr/lib/ directory. I made sure to include the LilyPond directory as part of the include path

Re: Unusual cross-staff stem in Bartók

Hi Arle, > That did indeed help. It got me 90% of the way there. When I actually applied > it in the piece I’m setting, I found that the length of the overridden stem > was pushing the other staff away. It didn’t do this in the example you made, > so I’m not sure what was interfering You

Re: Unusual cross-staff stem in Bartók

Írta Kieren: > p.s. Maybe this helps? That did indeed help. It got me 90% of the way there. When I actually applied it in the piece I’m setting, I found that the length of the overridden stem was pushing the other staff away. It didn’t do this in the example you made, so I’m not sure what

Re: Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

So schrieb David: > Either way is acting as it should. > > The manual has an index entry "beam, with lyrics" for the chapter > "Setting automatic beam behavior" but there is no usable reference > whatsoever in that chapter. I actually find rather little elsewhere > either, there are mostly just

Re: hide Stuff

Please keep all conversation on the list. Am 14.01.20 um 11:36 schrieb bb: Thanks for reply. Works only partially. 1st there stays a Staff artefact This is because you tagged only the music inside the staff, not the staff itself. 2nd ther is no midi sound for the hidden notes I need the

Re: Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

Arle Lommel writes: > Thanks very much to Carl Sorenson for a response that got me to start paring > things > down even more and led me to find the problem in my score where I didn’t > previously look. Took a while > > Basically, if autoBeam is off (somehow I’d turned it off outside a >

Re: Syntax highlighting

Il giorno mar 14 gen 2020 alle 12:34, Urs Liska ha scritto: Pygments is also what Pandoc uses for its syntax highlighting, so that would also make sense for that (e.g. generating PDF documentation from Markdown). Are you sure? I think that pygments is the name of the default style in Pandoc,

Re: hide Stuff

Am 14.01.20 um 11:36 schrieb bb: > Thanks for reply. Works only partially. > > 1st there stays a Staff artefact > > 2nd ther is no midi sound for the hidden notes > > I need the midi sound, but not the grafics. > > Is there a solution? > > \version "2.19.2" >   metronome = \tag #'A  {\relative

Re: How to increase shift dynamic and end of hairpin

On Tue, 7 Jan 2020 at 23:23, Guy Stalnaker wrote: > > Sorry, Knute -- Harm's suggestion is less work LOL Hi, Even less work would be to change Hairpin.minimum-length. %% MWE \version "2.19" \language "english" \layout { \context { \Voice \override Hairpin.minimum-length = #8 } }

Re: Syntax highlighting

Am Dienstag, den 14.01.2020, 12:27 +0100 schrieb Federico Bruni: > > Il giorno mar 14 gen 2020 alle 09:13, Craig Dabelstein > ha scritto: > > Hi all, > > > > I'd like to add LilyPond syntax highlighting to highlight.js ( > > https://highlightjs.readthedocs.io/en/latest/ ) so that I can > >

Re: Syntax highlighting

Il giorno mar 14 gen 2020 alle 09:13, Craig Dabelstein ha scritto: Hi all, I'd like to add LilyPond syntax highlighting to highlight.js ( https://highlightjs.readthedocs.io/en/latest/ ) so that I can experiment with documentation tools such as mkDocs/readthedocs. Does anyone have any

Users of scholarly.choice or scholarly.editorial-markup?

Hi all, does anyone know if the openLilyLib modules scholarly.choice and scholarly.editorial-markup are actually used by people? The reason I'm asking is that I have the impression that I should rename the command \editorialMarkup to something different and would like to know if this would

Re: How to increase shift dynamic and end of hairpin

Kieren MacMillan writes: > Hi Guy, > >> You sir are a gentleman and a scholar! > > Well, ½ of each means I’m a total of 1. ;) > >> I didn't want to say anything, but each of the three previous >> suggestions worked for the MWE, but when applied to my score either >> either did not work at all,

Re: Distance of a grob from its reference point

On 2020-01-13 7:05 pm, Paolo Prete wrote: 1) its *calculated* distance from its reference point? (from what I see, the reference Y of an OttavaBracket is the middle line of the associated staff...) I tried ly:grob-staff-position (see the snippet below), but it doesn't seem to give this info