Hi There,
My name is Sally and I am writing because I’m a freelance writer for a small
music education site. Recently, we released an eye opening guide highlighting
how a simple trick known as the circle of fifths can help all musicians,
especially new ones, learn to master their instruments
Hi Sally,
thank you for coming here.
Do you think you can come up with a topic that actually relates to music
notation and still allows you to introduce your article? As it is I'm
not sure if it fits our blog, although it's surely an interesting topic
for many of our readers and users.
I wouldn'
On Wed, 21 Jun 2017, Urs Liska wrote:
> Do you think you can come up with a topic that actually relates to music
> notation and still allows you to introduce your article? As it is I'm not
I would advise caution here. It sounds to me like the person didn't know
she was writing to a mailing list,
Hi Sally,
While your article is interesting, lilypond is a tool for advanced music
engraving, and this mailing list and the website focus on that and the use
of the lilypond engraving software pretty much exclusively rather than
music theory or practice matters. You may find a more appropriate for
Hi all,
I searched the bug tracker for the following issue but did not find
anything...
Consider two files:
foo.ily:
\version "2.19.59"
\include "bar.ly"
bar.ly:
\version "2.19.59"
\include "foo.ily"
{ c4 d e f }
If you try to compile bar.ly the parsing process continues forever,
appare
On Wed, 21 Jun 2017, Michael Käppler wrote:
> foo.ily:
> \include "bar.ly"
> bar.ly:
> \include "foo.ily"
> Am I right to consider this a bug?
I don't think so - at least not a bug in Lilypond. It's just doing what
you told it to do, and most other language parsers that have an "include"
facili
On 21.06.2017 22:03, msk...@ansuz.sooke.bc.ca wrote:
On Wed, 21 Jun 2017, Michael Käppler wrote:
foo.ily:
\include "bar.ly"
bar.ly:
\include "foo.ily"
Am I right to consider this a bug?
I don't think so - at least not a bug in Lilypond. It's just doing what
you told it to do, and most other la
What would be wrong about just outputting a warning "Trying to include
already included file" or something like that and reject
the recursive \include statement?
I came across this when working with a include file collecting cue notes
like that:
\include "foo1.ly"
\include "foo2.ly"
\include "
On 21.06.2017 22:32, Michael Käppler wrote:
Honestly I did not try it, but I am quite sure that it would be easy
to implement a IFDEF mechanism like in C preprocessing with a few
lines of Scheme, however.
That won’t be Scheme involved there. IIRC \include statements are
resolved even before
On Wed, 21 Jun 2017, Simon Albrecht wrote:
> It would be even better, I think, if Lily noticed the circular dependency and
> aborted with an informative message instead of just running on forever.
This may be a problem if there's any possibility of an include being
conditional. Then, someone coul
On Wed, 21 Jun 2017 15:57:59 -0500 (CDT), msk...@ansuz.sooke.bc.ca wrote:
> This may be a problem if there's any possibility of an include being
> conditional. Then, someone could write a non-infinite recursive include
> deliberately, and be disappointed when Lilypond breaks it.
Instead of abort
On 06/21/2017 11:10 PM, Johan Vromans wrote:
If you have a non-infinite recursive include it will continue.
I think that would require solving the Halting Problem first.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailm
On Wed, 21 Jun 2017, Johan Vromans wrote:
> Instead of aborting, LP could issue a warning that it detected a circular
> include. If it then hangs, you have a clue what is going on. If you have a
> non-infinite recursive include it will continue.
If it's only a warning (we need not get back into th
On Wed, 21 Jun 2017, caag...@gmail.com wrote:
> On 06/21/2017 11:10 PM, Johan Vromans wrote:
> > If you have a non-infinite recursive include it will continue.
>
> I think that would require solving the Halting Problem first.
That's true if it has to determine whether the recursion is infinite, bu
On 21.06.2017 23:24, msk...@ansuz.sooke.bc.ca wrote:
my understanding of the proposal was that Lilypond would continue with a
warning in any case, not trying to decide whether it's infinite, and let
the user deal with shutting it down if in fact it is infinite.
I was going to write that not eve
Am 21.06.2017 um 23:24 schrieb msk...@ansuz.sooke.bc.ca:
On Wed, 21 Jun 2017, caag...@gmail.com wrote:
On 06/21/2017 11:10 PM, Johan Vromans wrote:
If you have a non-infinite recursive include it will continue.
I think that would require solving the Halting Problem first.
That's true if it ha
Hello all,
I need some bookparts to use a different staff size than the rest of a
book, thus the usage of layout-set-staff-size. This resets the afore
defined fonts and I cannot seem to find a place where to re-define the
fonts. See the reduced example below. Any ideas?
\version "2.19.59"
#(set
Hi Lilyponders,
I've been working on a very big score, adding staves one at a time.
There are 34 staves, and the PDF is 107 pages long. When I add in either of
the final two staves I get this error message:
lilypond(43147,0xa70c91c0) malloc: *** mach_vm_map(size=1048576) failed
(error code=3)
*
Simon Albrecht writes:
> On 21.06.2017 22:32, Michael Käppler wrote:
>> Honestly I did not try it, but I am quite sure that it would be easy
>> to implement a IFDEF mechanism like in C preprocessing with a few
>> lines of Scheme, however.
>
> That won’t be Scheme involved there. IIRC \include st
"Maxime's Music" writes:
> Hi Lilyponders,
>
> I've been working on a very big score, adding staves one at a time.
> There are 34 staves, and the PDF is 107 pages long. When I add in either of
> the final two staves I get this error message:
>
>
> lilypond(43147,0xa70c91c0) malloc: *** mach_vm_ma
On Thu, 22 Jun 2017 06:39:08 +0200, David Kastrup wrote:
> I don't really see this as calling for changes. If you want to create
> utility files to be included at most once, you can try working with
> guards like it is customary for C/C++ include files.
I think we're shifting topic here from re
21 matches
Mail list logo
