Re: Fretboard diagrams: Why does LilyPond sometimes try to interpret ":7" as a duration?

Kevin Cole writes: > On Mon, Jul 25, 2022 at 5:56 PM Aaron Hill wrote: >> >> On 2022-07-25 1:56 pm, Kevin Cole wrote: >> >> frets = \chordmode { f4 c4:7 g4:7 c4 bf4 d4:m } >> ^^ >> Input is in chord mode. Modifiers like :m and :7 work. >> >> >> frets = { g4 c4 a4 d4:7 } >>

Re: A new Scheme tutorial

Jean Abou Samra writes: > Le 25 juil. 2022 à 14:51, David Kastrup a écrit : >> >> syntax-rules/syntax-case introduce a completely new and arbitrary syntax >> intended to be human-readable. That's sort of a counterthesis to the >> LISP philosophy of representing programs by the data

Re: Fretboard diagrams: Why does LilyPond sometimes try to interpret ":7" as a duration?

On Mon, Jul 25, 2022 at 5:56 PM Aaron Hill wrote: > > On 2022-07-25 1:56 pm, Kevin Cole wrote: > >> frets = \chordmode { f4 c4:7 g4:7 c4 bf4 d4:m } > ^^ > Input is in chord mode. Modifiers like :m and :7 work. > > >> frets = { g4 c4 a4 d4:7 } >^ > Missing

Re: Fretboard diagrams: Why does LilyPond sometimes try to interpret ":7" as a duration?

> > > respectively, work fine. The third has a bit more going on, but adding: > > > > > > > > frets = { g4 c4 a4 d4:7 } > > > > > > > now gives me: > > > > > error: not a duration > > > g4 c4 a4 d4: > > > 7 > > > > (Without the frets score, everything is fine.) > You are

Re: Fretboard diagrams: Why does LilyPond sometimes try to interpret ":7" as a duration?

On 2022-07-25 1:56 pm, Kevin Cole wrote: frets = \chordmode { f4 c4:7 g4:7 c4 bf4 d4:m } ^^ Input is in chord mode. Modifiers like :m and :7 work. frets = { g4 c4 a4 d4:7 } ^ Missing \chordmode. :7 indicates a tremolo with an invalid duration. -- Aaron Hill

Re: Fretboard diagrams: Why does LilyPond sometimes try to interpret ":7" as a duration?

On Mon, Jul 25, 2022 at 4:56 PM Kevin Cole wrote: > > Hi, > > I decided to move all of the fretboards from various scores to a > "summary" score at the top -- sort of a "legend" so that the scores > would not take up so much space. > > I'm defining a variable named frets and then, later: > >

Re: A new Scheme tutorial

> Le 25 juil. 2022 à 14:51, David Kastrup a écrit : > > Jean Abou Samra writes: > Le 25 juil. 2022 à 09:01, Andrew Bernard a écrit : >>> >>>  >>> Hello Jean, >>> >>> This is a great effort. >>> >>> A couple of suggestions. I suppose there are a few web pages with >>> lists

Fretboard diagrams: Why does LilyPond sometimes try to interpret ":7" as a duration?

Hi, I decided to move all of the fretboards from various scores to a "summary" score at the top -- sort of a "legend" so that the scores would not take up so much space. I'm defining a variable named frets and then, later: \score { << \new ChordNames \frets \new FretBoards \frets

Re: Custom scheme engraver (Barline) problem

Jean - Merci! This is exactly what I needed. -kwb On Jul 24, 2022, 11:50 PM -0700, Jean Abou Samra , wrote: > > > > Le 25 juil. 2022 à 08:23, Kyle Baldwin a écrit : > > > > I'm trying to create a custom bar number engraver that will respond to > > couple of different events, but wanted to

Re: Issue with download link

On Mon, Jul 25, 2022 at 6:56 AM Simon Albrecht wrote: > > Hello everyone, > > On 24/07/2022 19:44, Jonas Hahnfeld via LilyPond user discussion wrote: > > Please refer to the Installing section in the > > Learning Manual for instructions how to set up the provided binaries: > >

Re: Markup command trouble

Hi David, On 25/07/2022 16:35, David Kastrup wrote: You probably meant \markup spanish = \markup \italic \etc which defines a markup command. The way you wrote it, \spanish is just a scheme function that happens to return the internals of a markup command definition. I did mean that.

Re: Going back in MIDI time

On Mon, Jul 25, 2022 at 2:38 AM Jean Abou Samra wrote: > > > > Le 25 juil. 2022 à 11:05, Mario Moles a écrit : > > Hi lilponders! > > Do you know how to eliminate this warning? I have not found anything either > on the list or on google: > "programming error: Going back in MIDI time. > go on,

Re: LilyPond 2.23.11

On Sun, Jul 24, 2022 at 3:37 PM Jean Abou Samra wrote: > > > > Le 25/07/2022 à 00:36, Jean Abou Samra a écrit : > > Le 25/07/2022 à 00:32, Knute Snortum a écrit : > >> Okay, it's even stranger than I thought. It's this URL: > >> > >> https://lilypond.org/doc/v2.23/Documentation/web/unix > >> > >>

Re: Markup command trouble

Simon Albrecht writes: > Dear list, > > I wanted to define a markup command for easy switchable styling of > text and ran into an issue which seems hard to understand: > > > \version "2.23.9" > > spanish = \markup\italic \etc > > \markup \column { >   \spanish \justify { test } > }

Issue with download link

Hello everyone, On 24/07/2022 19:44, Jonas Hahnfeld via LilyPond user discussion wrote: Please refer to the Installing section in the Learning Manual for instructions how to set up the provided binaries: https://lilypond.org/doc/v2.23/Documentation/learning/installing This link leads to a

Markup command trouble

Dear list, I wanted to define a markup command for easy switchable styling of text and ran into an issue which seems hard to understand: \version "2.23.9" spanish = \markup\italic \etc \markup \column {   \spanish \justify { test } } => “error: not a markup” My

Re: A new Scheme tutorial

Jean Abou Samra writes: >> Le 25 juil. 2022 à 09:01, Andrew Bernard a >> écrit : >> >>  >> Hello Jean, >> >> This is a great effort. >> >> A couple of suggestions. I suppose there are a few web pages with >> lists of recommended texts for Scheme, but I think it would be great >> if you

Re: A new Scheme tutorial

Yes, that is a downside - and I suppose if one is just learning Scheme one would not be aware of the issue. Andrew On 25/07/2022 10:11 pm, Jean Abou Samra wrote: Gosh, it seems to teach Lisp-style non-hygienic macros instead of syntax-rules/syntax-case. That’s heresy against my religion! OK,

Re: A new Scheme tutorial

> Le 25 juil. 2022 à 09:01, Andrew Bernard a écrit > : > >  > Hello Jean, > > This is a great effort. > > A couple of suggestions. I suppose there are a few web pages with lists of > recommended texts for Scheme, but I think it would be great if you added this > one to the 'where to go

Re: Help needed with arranger.ly

Eef Weenink writes: > :-) works fine. So if I understandn this correctly, inside a scheme > part it is possible to insert lilypondinstructions like this: > > (scheme instructions #{ lilypondinstructions #}) > > (that was not in the manual ;-)

Re: Help needed with arranger.ly

Ok, I start studying . (I meant the manual if arranger.Ly) Met vriendelijke groet, Eef H.E. Weenink MBA > Op 25 jul. 2022 om 12:17 heeft David Kastrup het volgende > geschreven: > > Eef Weenink writes: > >> :-) works fine. So if I understandn this correctly, inside a scheme >> part it

Re: Help needed with arranger.ly

:-) works fine. So if I understandn this correctly, inside a scheme part it is possible to insert lilypondinstructions like this: (scheme instructions #{ lilypondinstructions #}) (that was not in the manual ;-) regards, Eef > Op 25 jul. 2022, om 11:53 heeft Eef Weenink het > volgende

Re: Help needed with arranger.ly

Merci beaucoup, I will check. regards, Eef > Op 25 jul. 2022, om 10:07 heeft Gilles Thibault het > volgende geschreven: > > Le 2022-07-24 13:38, Eef Weenink a écrit : >> I need some help to get this nice program really running. >> I read the manual several times,studied

Re: Going back in MIDI time

> Le 25 juil. 2022 à 11:05, Mario Moles a écrit : > > Hi lilponders! > > Do you know how to eliminate this warning? I have not found anything either > on the list or on google: > "programming error: Going back in MIDI time. > go on, cross your fingers " > > Thanks It’s mentioned on this

Re: Going back in MIDI time

Am Mo., 25. Juli 2022 um 11:05 Uhr schrieb Mario Moles : > > Hi lilponders! > > Do you know how to eliminate this warning? I have not found anything > either on the list or on google: > "programming error: Going back in MIDI time. > go on, cross your fingers " > > Thanks > > Haven't seen this for

Going back in MIDI time

Hi lilponders! Do you know how to eliminate this warning? I have not found anything either on the list or on google: "programming error: Going back in MIDI time. go on, cross your fingers " Thanks

Re: Spacing between Lyrics and Chordnames

On Mon, 25 Jul 2022 at 09:25, Randy Josleyn wrote: > > Hi everyone! > > I'm trying to increase the spacing between the bottom line of lyrics and the ChordNames in the next system. > > My score looks like the MWE below. I played with example below and even without the ChordNames, the override

Re: Help needed with arranger.ly

Le 2022-07-24 13:38, Eef Weenink a écrit : I need some help to get this nice program really running. I read the manual several times,studied NOTES.ly etcetera and now able to get the first parts of music on the correct place. :-) (I am using a score with 6 instruments and I am

Spacing between Lyrics and Chordnames

Hi everyone! I'm trying to increase the spacing between the bottom line of lyrics and the ChordNames in the next system. My score looks like the MWE below. I played with example below and even without the ChordNames, the override doesn't behave as I expected it would. I checked the IR and it

Re: A new Scheme tutorial

Hello Jean, This is a great effort. A couple of suggestions. I suppose there are a few web pages with lists of recommended texts for Scheme, but I think it would be great if you added this one to the 'where to go from here' section: Teach Yourself Scheme in Fixnum Days (ds26gte.github.io)

Re: Custom scheme engraver (Barline) problem

> Le 25 juil. 2022 à 08:23, Kyle Baldwin a écrit : > >  > I'm trying to create a custom bar number engraver that will respond to couple > of different events, but wanted to initially try and clone the Bar number > engraver in c to scheme. Everything seems to work the way I want it to, >

Custom scheme engraver (Barline) problem

I'm trying to create a custom bar number engraver that will respond to couple of different events, but wanted to initially try and clone the Bar number engraver in c to scheme. Everything seems to work the way I want it to, except for the positioning seems to be wrong. The numbers appear in