Re: Strange error from define-syntax

2020-05-28 Thread David Kastrup
"John Schlomann" writes: > define-macro works perfectly for me, even though the Guile manual seems to > somewhat disparage its use. Well, it's not the modern Scheme way but at the current point of time LilyPond works best with Guile 1.8. -- David Kastrup

RE: Strange error from define-syntax

2020-05-28 Thread John Schlomann
er Mailing List' > Subject: Re: Strange error from define-syntax > > "John Schlomann" writes: > > > Thank you, David, for your quick response. I'm not sure what you mean by > > "stick to macros". I thought define-syntax was the way to define a macro. >

Re: Strange error from define-syntax

2020-05-28 Thread David Kastrup
"John Schlomann" writes: > Thank you, David, for your quick response. I'm not sure what you mean by > "stick to macros". I thought define-syntax was the way to define a macro. > What am I missing? define-macro and defmacro apparently. -- David Kastrup

Re: Strange error from define-syntax

2020-05-28 Thread Valentin Villenave
On 5/28/20, John Schlomann wrote: > Thank you, David, for your quick response. I'm not sure what you mean by > "stick to macros". I thought define-syntax was the way to define a macro. > What am I missing? I think David may have been referring to LilyPond macros; have a look at that for example:

RE: Strange error from define-syntax

2020-05-28 Thread John Schlomann
11:54 AM > To: John Schlomann > Cc: 'Lilypond-User Mailing List' > Subject: Re: Strange error from define-syntax > > "John Schlomann" writes: > > > Dear Ponders & Schemers, > > > > > > > > I wanted to try creating a simple Scheme ma

Re: Strange error from define-syntax

2020-05-28 Thread David Kastrup
"John Schlomann" writes: > Dear Ponders & Schemers, > > > > I wanted to try creating a simple Scheme macro. I've never done this before, > so I may well be going about it all wrong, but the error I get doesn't make > sense. > > > > Here is a minimal non-working example: > > > > \version

Re: Strange error from \new Voice

2020-04-10 Thread David Wright
On Fri 10 Apr 2020 at 09:58:57 (+0200), Michael Gerdau wrote: > > When working with addlyrics it was outside the \new staff construct like > > here: > > > > tenorVoicePart = \new Staff \with { > >   instrumentName = "Tenor" > >   midiInstrument = "choir aahs" > > } { \clef "treble_8" \tenorVoice

Re: Strange error from \new Voice

2020-04-10 Thread David Wright
On Thu 09 Apr 2020 at 18:41:40 (+0200), Noeck wrote: > Am 09.04.20 um 18:18 schrieb Bernhard Kleine: > > This would be worth mentioning in the manual! > > glad it works. What exactly would you mention in the manual? > > 1) How to use the \lyricsto construct? It is explained here: > >

Re: Strange error from \new Voice

2020-04-10 Thread Michael Gerdau
> When working with addlyrics it was outside the \new staff construct like > here: > > tenorVoicePart = \new Staff \with { >   instrumentName = "Tenor" >   midiInstrument = "choir aahs" > } { \clef "treble_8" \tenorVoice } > \addlyrics { \verseVoice } > > Now, it is within > > Soprano = \new

Re: Strange error from \new Voice

2020-04-09 Thread Bernhard Kleine
When working with addlyrics it was outside the \new staff construct like here: tenorVoicePart = \new Staff \with {   instrumentName = "Tenor"   midiInstrument = "choir aahs" } { \clef "treble_8" \tenorVoice } \addlyrics { \verseVoice } Now, it is within Soprano = \new Staff \with {  

Re: Strange error from \new Voice

2020-04-09 Thread Noeck
Am 09.04.20 um 18:18 schrieb Bernhard Kleine: > This would be worth mentioning in the manual! Hi Bernhard, glad it works. What exactly would you mention in the manual? 1) How to use the \lyricsto construct? It is explained here:

Re: Strange error from \new Voice

2020-04-09 Thread Bernhard Kleine
Am 09.04.2020 um 17:18 schrieb Noeck: > > Am 09.04.20 um 17:04 schrieb Bernhard Kleine: >> \new Lyrics \lyricsto „SI“ > Did you copy that verbatim or use the correct "normal quotes": > > \new Lyrics \lyricsto "SI" > > Just to rule out that simple problem. > > Joram This is what is there :

Re: Strange error from \new Voice

2020-04-09 Thread Noeck
Am 09.04.20 um 17:04 schrieb Bernhard Kleine: > \new Lyrics \lyricsto „SI“ Did you copy that verbatim or use the correct "normal quotes": \new Lyrics \lyricsto "SI" Just to rule out that simple problem. Joram

Re: Strange error from \new Voice

2020-04-09 Thread Bernhard Kleine
this results in an error: the output is in the appendix. Preprocessing graphical objects... programming error: No spring between column 0 and next one continuing, cross fingers programming error: No spring between column 0 and next one continuing, cross fingers programming error: didn't find

Re: Strange error from \new Voice

2020-04-09 Thread Michael Gerdau
Replace \addlyrics... by \new Lyrics \lyricsto „SI“... Kind regards, Michael Mobil gesendet > Am 09.04.2020 um 15:03 schrieb Bernhard Kleine : > > I have the following extract from Mendelssohn Bartholdy. I noticed that > the parentheses in measure seven were not respected and the text was >

Re: Strange error with no traceable cause.

2018-06-05 Thread David Kastrup
Karlin High writes: > On 6/5/2018 4:02 PM, Thomas Morley wrote: >>> For running gdb do: >>> >>> gdb path/to/lilypond-executable >>> >>> For example: gdb lilypond-git/build/out/bin/lilypond >>> You will get some infos about gdb returned, finally it ends with >>> (gdb) >>> >>> Then type: >>> run

Re: Strange error with no traceable cause.

2018-06-05 Thread Karlin High
On 6/5/2018 4:02 PM, Thomas Morley wrote: For running gdb do: gdb path/to/lilypond-executable For example: gdb lilypond-git/build/out/bin/lilypond You will get some infos about gdb returned, finally it ends with (gdb) Then type: run path/to/the/ly-file I forgot, type: bt to get the stack

Re: Strange error with no traceable cause.

2018-06-05 Thread Thomas Morley
2018-06-05 22:45 GMT+02:00 Thomas Morley : > 2018-06-05 22:35 GMT+02:00 : >> Mensagem Original >> Ativo 5 de jun de 2018 17:30, David Kastrup < d...@gnu.org> escreveu: >> >> crimsonsunr...@protonmail.com writes: >> >>> Well, I don't have any experience with gdb, so I wouldn't

Re: Strange error with no traceable cause.

2018-06-05 Thread Thomas Morley
2018-06-05 22:35 GMT+02:00 : > Mensagem Original > Ativo 5 de jun de 2018 17:30, David Kastrup < d...@gnu.org> escreveu: > > crimsonsunr...@protonmail.com writes: > >> Well, I don't have any experience with gdb, so I wouldn't know what to >> do. The strange thing seems to be

Re: Strange error with no traceable cause.

2018-06-05 Thread crimsonsunrise
Mensagem Original Ativo 5 de jun de 2018 17:30, David Kastrup escreveu: crimsonsunr...@protonmail.com writes: > Well, I don't have any experience with gdb, so I wouldn't know what to > do. The strange thing seems to be that, if the score is engraved using > Frescobaldi's

Re: Strange error with no traceable cause.

2018-06-05 Thread David Kastrup
crimsonsunr...@protonmail.com writes: > Well, I don't have any experience with gdb, so I wouldn't know what to > do. The strange thing seems to be that, if the score is engraved using > Frescobaldi's verbose output ( which has a separate engrave button ), > the error doesn't happen. That's not

Re: Strange error with no traceable cause.

2018-06-05 Thread crimsonsunrise
Mensagem Original Ativo 5 de jun de 2018 16:43, David Kastrup escreveu: crimsonsunr...@protonmail.com writes: > ​Sent with ProtonMail Secure Email.​ > > ‐‐‐ Original Message ‐‐‐ > > On 5 June 2018 2:33 PM, David Kastrup wrote: > >> crimsonsunr...@protonmail.com writes:

Re: Strange error with no traceable cause.

2018-06-05 Thread David Kastrup
crimsonsunr...@protonmail.com writes: > ​Sent with ProtonMail Secure Email.​ > > ‐‐‐ Original Message ‐‐‐ > > On 5 June 2018 2:33 PM, David Kastrup wrote: > >> crimsonsunr...@protonmail.com writes: >> >> > I'm working on a large score using 2.21.0, parts all separated into >> > >> >

Re: Strange error with no traceable cause.

2018-06-05 Thread crimsonsunrise
​Sent with ProtonMail Secure Email.​ ‐‐‐ Original Message ‐‐‐ On 5 June 2018 2:33 PM, David Kastrup wrote: > crimsonsunr...@protonmail.com writes: > > > I'm working on a large score using 2.21.0, parts all separated into > > > > different files and such, suddenly, after adding a

Re: Strange error with no traceable cause.

2018-06-05 Thread David Kastrup
crimsonsunr...@protonmail.com writes: > I'm working on a large score using 2.21.0, parts all separated into > different files and such, suddenly, after adding a bar for the 3rd > clarinet, this shows up: > > Parsing... > > Interpreting music...[8][16]ERROR: In procedure ly:trampoline: > > ERROR:

Re: Strange error

2016-12-18 Thread Br. Samuel Springuel
On 2016-12-18 1:12 PM, David Kastrup wrote: I beg to differ. Have you actually tried compiling the result or just glanced over it? I just glanced it over and didn't see any changes in the code. Doing it again now that I know what to look for, I do indeed spot the change. Guess that's what

Re: Strange error

2016-12-18 Thread David Kastrup
"Br. Samuel Springuel" writes: > On 2016-12-18 12:24 PM, Malte Meyn wrote: >> Try an additional \with: >> >> \new Staff \with \timeless { c' } > > That does indeed work, but isn't that redundant programming? timeless = \with { } \new StaffGroup { \new Staff \timeless {

Re: Strange error

2016-12-18 Thread David Kastrup
"Br. Samuel Springuel" writes: > When I compile the following snippet I get an error under 2.19.53 that > wasn't there under 2.18.2: > > \version "2.19.53" > > timeless = \with { > \remove "Time_signature_engraver" } > > \new Staff \with { > \remove

Re: Strange error

2016-12-18 Thread Br. Samuel Springuel
On 2016-12-18 12:24 PM, Malte Meyn wrote: Try an additional \with: \new Staff \with \timeless { c' } That does indeed work, but isn't that redundant programming? -- ✝ Br. Samuel, OSB St. Anselm’s Abbey Washington, DC (R. Padraic Springuel) PAX ☧ ΧΡΙΣΤΟΣ

Re: Strange error

2016-12-18 Thread Malte Meyn
Am 18.12.2016 um 18:03 schrieb Br. Samuel Springuel: When I compile the following snippet I get an error under 2.19.53 that wasn't there under 2.18.2: \version "2.19.53" timeless = \with { \remove "Time_signature_engraver" } \new Staff \with { \remove "Time_signature_engraver" } {

Re: Strange error(?) message when invoking lilypond-book

2015-11-20 Thread David Kastrup
Speldosa writes: > I'm running OS X 10.11 and LilyPond version 2.18.2-1. I'm trying to invoke > lilypond-book via terminal by typing the following (I've tried getting the > path option to work, but I've given up after a gazillion tries): > >

Re: Strange error(?) message when invoking lilypond-book

2015-11-20 Thread Speldosa
Thanks! Running the same terminal code with "python2" at the beginning did the trick! -- View this message in context: http://lilypond.1069038.n5.nabble.com/Strange-error-message-when-invoking-lilypond-book-tp183876p183884.html Sent from the User mailing list archive at Nabble.com.

Re: strange error message - cannot open .ly file

2015-10-30 Thread Thomas Scharkowski
Original-Nachricht \version "2.19.29" \language "italiano" \header { title = "禱願" subtitle = "Prayer Willing" poet = "雨打芭蕉" % Remove default LilyPond tagline tagline = ##f} \paper { #(set-paper-size "letter")} \layout { \context {\Voice\consists

Re: strange error message - cannot open .ly file

2015-10-30 Thread Simon Albrecht
Hi Ming, On 30.10.2015 01:01, MING TSANG wrote: Hi lilyponders: Frecobaldi can open the file, yet when I hit to run lilypond, I got strange error message: I can’t confirm that either: I get two failed barchecks, but else it compiles fine. It would seem odd that Lily didn’t recognise the

Re: strange error message - cannot open .ly file

2015-10-30 Thread MING TSANG
Cc: Lilypond-user Mailinglist <lilypond-user@gnu.org> Sent: Friday, October 30, 2015 9:38 AM Subject: Re: strange error message - cannot open .ly file On Fri 30 Oct 2015 at 00:01:44 (+), MING TSANG wrote: > Hi lilyponders: Hi, please post text, not HTML, and if you can't avoid

Re: strange error message - cannot open .ly file

2015-10-30 Thread David Wright
On Fri 30 Oct 2015 at 00:01:44 (+), MING TSANG wrote: > Hi lilyponders: Hi, please post text, not HTML, and if you can't avoid that, please post source code etc as attachments rather than inline. > Frecobaldi can open the file, yet when I hit to run lilypond, I got strange > error message: >

Re: strange error message - cannot open .ly file

2015-10-30 Thread lily...@lionunicorn.co.uk
On Fri 30 Oct 2015 at 14:03:30 (+), MING TSANG wrote: > Thank you David,simon, Jacques & Thomas: > > Turn out it was the file name that cause the problem. > As suggest by David, > 1.. I rename the .ly file not using any utf-8 code and it complies fine. > 2.. I change the first utf-8

Re: strange error message - cannot open .ly file

2015-10-30 Thread Michael Gerdau
> Turn out it was the file name that cause the problem.As suggest by > David, 1.. I rename the .ly file not using any utf-8 code and it > complies fine.2.. I change the first utf-8 character "禱" to another "主" > and the file complies fine as well3.. the file name with utf-8 "禱" when > comply

Re: strange error message - cannot open .ly file

2015-10-30 Thread Jacques Menu
Hello Ming, Your example runs fine with 2.19.30. JM > Le 30 oct. 2015 à 10:07, Thomas Scharkowski a > écrit : > > Original-Nachricht >> \version "2.19.29" >> \language "italiano" >> \header { title = "禱願" subtitle = "Prayer Willing" poet =

Re: strange error message - cannot open .ly file

2015-10-30 Thread Michael Gerdau
> Turn out it was the file name that cause the problem.As suggest by > David, 1.. I rename the .ly file not using any utf-8 code and it > complies fine.2.. I change the first utf-8 character "禱" to another "主" > and the file complies fine as well3.. the file name with utf-8 "禱" when > comply

Re: strange error after reducing music rhythm by an half

2012-12-27 Thread Marc Hohl
Am 27.12.2012 22:31, schrieb Federico Bruni: Hi while transcribing a piece of music, I realized that it may work better if written with a different rhythm, so I used the Frescobaldi option which reduces the rhythms by an half. Then I removed all the bar checks. But I cannot compile this

Re: strange error after reducing music rhythm by an half

2012-12-27 Thread Federico Bruni
Il 27/12/2012 22:40, Marc Hohl ha scritto: 313: 29* [ly:pitch-tones ... 313: 30* [list-ref (#Pitch e' #Pitch b #Pitch g ...) {7}] translation-functions.scm: In procedure list-ref in expression (list-ref tuning (1- string)): translation-functions.scm: Argument 2 out of range: 7 It looks as

RE: Strange error in compiling 2.13.0

2009-04-02 Thread Nick Payne
I got the same warning message, see http://www.nabble.com/New-warning-msg-2.13-td22658865.html. I didn't get any response on it. I went back to using 2.12.2. Nick From: lilypond-user-bounces+nick.payne=internode.on@gnu.org

Re: strange error message with tuplet

2009-02-07 Thread M Watts
Stefan Thomas wrote: Dear lilypond-users, when compiling one of my scores I get the following error message, which I don't understand: musik/musik_ab115.ly:63:16: warning: No tuplet to end s8\fp\ s\f\ \times 4/6 { s32*5\p\ s 32\!} \pedtrem s4...\ff \startTextSpan s32

Re: strange error -beam and tremolo

2008-07-22 Thread Trevor Daniels
Seems to work ok in the latest development version, 2.11.52, so I guess you're using an earlier version. The development version is now at least as stable as 2.10, so it might be worth upgrading, although you will need to run convert-ly on your files. Trevor - Original Message - From:

Re: strange error when creating context

2008-06-30 Thread Werner LEMBERG
Now the strange warning comes, saying it can't create the CHordMarks context. This comes from the MIDI processing (and admittedly, there is no indication for that in the warning message). You can ignore it safely. Werner  ___ lilypond-user

Re: strange error causes Lilypond refuse to compile

2008-06-22 Thread Graham Percival
(for your other email) I would attempt to isolate and fix these problems before playing with virtual memory. I must admit that the error message looks like a problem with memory allocation, but I think the solution to this lies in either your tweaks, or in a bug with 2.11.49. Unfortunately,

Re: strange error

2008-02-29 Thread Graham Percival
I'm 95% certain that you missed a } or somewhere, but I don't have the time to analyze your file to see where it is. HTH, - Graham On Sat, 1 Mar 2008 09:39:43 +0800 (CST) hhpmusic [EMAIL PROTECTED] wrote: Hi, I'm coping the opening of my violin concerto (just an experiment to try braille

Re: strange error

2008-02-29 Thread Ledocq-Boccart
Hi, Just a suggestion... If not yet the case, using jedit as code editor could maybe make it easier for checking missing { or } (pairs of linked brackets are highlighted when mouse cursor is positionned just after the character). http://www.jedit.org Also check separately each instrument

RE: strange error

2008-02-29 Thread Trevor Daniels
Hi Haipeng Line 20 - missing before Andante. Should be: toptextA = \markup { \bold \italic Andante } This is the mistake which causes the error in init.ly. There are a couple of other minor errors: Line 39 - incorrect string ae\!. Maybe should be: \repeat tremolo 16 { f\ ees } \repeat

Re: strange error in converted file

2004-06-03 Thread Arvid Grøtting
Arvid Grøtting [EMAIL PROTECTED] writes: I've run across a strange error in a file converted from 1.6.9 to 2.2.1. Never mind; it was in a context redefinition (to get midi from voice contexts) that I don't need right now. -- Arvid ___