Hi Wol,
> how is lilypond supposed to know whether the g and f are supposed to be
> sharpened? :-)
\keyed \a \harmonicminor { a g g+ a }
Is it really that difficult to figure out a rational input syntax?
I could come up with a dozen completely different ones without breaking a sweat.
Cheers,
Lilypond doesn't know. Somewhere along the line human knowledge/input is
required.
Mark
-Original Message-
From: antlists [mailto:antli...@youngman.org.uk]
Sent: Monday, May 18, 2020 4:33 PM
To: Mark Stephen Mrotek ; lilypond-user@gnu.org
Subject: Re: Suggestion to make sharps and
Freeman Gilmore writes:
> Would someone please tell me what all Ly:make-pitch, is used for?
> Thank you, ƒg
It makes a pitch. A pitch is a data type in LilyPond's Scheme that has
an octave, a notename (actually a whole number within the scale), and an
accidental (a rational measured in terms
On 18/05/2020 22:15, Mark Stephen Mrotek wrote:
The natural a minor scale does not contain any sharps.
But is it a natural scale?
The harmonic a minor scale has the f sharp.
or a harmonic scale?
The melodic a minor scale has the g sharp and the f sharp.
But it also has g and f. So my
Would someone please tell me what all Ly:make-pitch, is used for?
Thank you, ƒg
Hi Elaine,
> Use of \relative is always fine if you realize that you need to explicitly
> define it every time you break it up.
If you have any desire to reuse small bits, that means you need to have dozens
(maybe hundreds?) of pre-defined bits.
I can’t imagine wanting to go through that
> -- Forwarded message --
> From: antlists
> To: lilypond-user@gnu.org
> Cc:
> Bcc:
> Date: Mon, 18 May 2020 20:21:32 +0100
> Subject: Re: Suggestion to make sharps and flats persistent
> On 18/05/2020 17:33, Kieren MacMillan wrote:
> > We (well… modulo me LOL) don’t get this
The natural a minor scale does not contain any sharps.
The harmonic a minor scale has the f sharp.
The melodic a minor scale has the g sharp and the f sharp.
Mark
-Original Message-
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of antlists
Hi Wol,
> Those of us who only use \relative (just me?) don't have any problems with
> cut-n-paste. Or is it just that my workflow is more likely to use "\repeat
> unfold"?
Let’s say you’re writing a piece in sonata form (or even just engraving an
existing one!).
You want to [re]use mm.
On 18/05/2020 17:33, Kieren MacMillan wrote:
We (well… modulo me LOL) don’t get this worked up about how \relative makes
cut-and-paste a nightmare. Why start now?;)
Those of us who only use \relative (just me?) don't have any problems
with cut-n-paste. Or is it just that my workflow is more
Hi,
[1] lists the instruments avaiable that can be used for the
midiInstrument property. Unfortunately the instrument I'm looking for (a
zabumba) isn't listed there.
Is it possible to add a new instrument? What are the necessary steps to
do so? I'm not familiar with this topic and would be glad
> On 18 May, 2020, at 11:30 AM, David Wright wrote:
>
> If you were compiling a C program foo.c into an executable, what you
> would be trying to avoid is recompiling fnbar.c into fnbar.o over
> and over again (and all of its similar companions).
>
> Can you explain which of your files are the
My apologies for the text formatting of my last mail. I wrote the message
on my mobile phone and didn't notice the formatting issue.
>
> [...]. That being said…
>
> Are not
>
> \relative f'
>
> and
>
> \fixed c'''
>
> just "feature requests for laziness with resulting opaqueness"? ;)
[...]
>
We (well… modulo me LOL) don’t get this worked up about how \relative makes
> cut-and-paste a nightmare. Why start now? ;)
Kieren MacMillan writes:
> Hi David,
>
>> LilyPond's input language has no representation for c-natural
>> as opposed to c-unkeyed-yet. Any kind of implementation would be doomed
>> without
>> that, anyway. Once you have that, it really becomes a tricky question
>> of where c-unkeyed-yet would
Am 18. Mai 2020 18:33:09 MESZ schrieb Kieren MacMillan
:
>Hi all,
>
>> This is just a feature request for laziness with resulting
>opaqueness. I think it has been requested several times over the years
>because of other program's bad habits.
>
>I agree with this 100%. That being said…
>
>Are
Kieren MacMillan writes:
> Hi all,
>
>> This is just a feature request for laziness with resulting
> opaqueness. I think it has been requested several times over the years
> because of other program's bad habits.
>
> I agree with this 100%. That being said…
>
> Are not
>
> \relative f'
>
>
On Mon, May 18, 2020 at 11:17 AM Urs Liska wrote:
[...]
> I think there are only two reliable (and therefore reasonable)
> approaches. Either you encode a pitch at what it "is" (a f sharp is
> always an f sharp) or you encode it at how it is printed (a note in the
> first staff space of a treble
Hi David,
> LilyPond's input language has no representation for c-natural
> as opposed to c-unkeyed-yet. Any kind of implementation would be doomed
> without
> that, anyway. Once you have that, it really becomes a tricky question
> of where c-unkeyed-yet would get its final pitch. And how this
Am 18. Mai 2020 18:48:04 MESZ schrieb David Kastrup :
>Urs Liska writes:
>
>> Am Montag, den 18.05.2020, 18:11 +0200 schrieb David Kastrup:
>>> Gianmaria Lari writes:
>>>
>>> > I don't know "how much Frescobaldi knows" of the lilypond code the
>>> > user is editing. If it has a logical
Urs Liska writes:
> Am Montag, den 18.05.2020, 18:11 +0200 schrieb David Kastrup:
>> Gianmaria Lari writes:
>>
>> > I don't know "how much Frescobaldi knows" of the lilypond code the
>> > user is editing. If it has a logical representation of the source
>> > code it could be Frescobaldi (and
Hi all,
> This is just a feature request for laziness with resulting opaqueness. I
> think it has been requested several times over the years because of other
> program's bad habits.
I agree with this 100%. That being said…
Are not
\relative f'
and
\fixed c'''
just "feature
On 18/05/2020 15:29, Fr. Samuel Springuel wrote:
On 18 May, 2020, at 9:37 AM, antlists wrote:
define trombone-notes.ly as a target, define it as changed if its dependencies change,
and say "it doesn't exist as a file that can be created with a command".
Right, that’s the step I’m trying
This is just a feature request for laziness with resulting opaqueness. I
think it has been requested several times over the years because of other
program's bad habits.
Shane
On Mon, May 18, 2020 at 12:17 PM Urs Liska wrote:
> Am Montag, den 18.05.2020, 18:11 +0200 schrieb David Kastrup:
> >
Am Montag, den 18.05.2020, 18:11 +0200 schrieb David Kastrup:
> Gianmaria Lari writes:
>
> > Hello Paul,
> >
> >
> > > [...]If I'm writing music in F, then I suggest that I be able to
> > > use *bF*
> > > as a pitch instead of *bf*. The *F* would indicate that all
> > > subsequent *b*s
> > >
Gianmaria Lari writes:
> Hello Paul,
>
>
>> [...]If I'm writing music in F, then I suggest that I be able to use *bF*
>> as a pitch instead of *bf*. The *F* would indicate that all subsequent *b*s
>> would be flattened until one is encountered with a different accidental or
>> until the end of
Am Montag, den 18.05.2020, 10:35 -0500 schrieb David Wright:
> On Fri 15 May 2020 at 12:03:33 (-0400), Fr. Samuel Springuel wrote:
> > > On 5/15/20, Fr. Samuel Springuel wrote:
> > > > Before I start writing a script to do this, is there an
> > > > existing tool which
> > > > will identify all
On Fri 15 May 2020 at 12:03:33 (-0400), Fr. Samuel Springuel wrote:
> > On 5/15/20, Fr. Samuel Springuel wrote:
> >> Before I start writing a script to do this, is there an existing tool which
> >> will identify all the `\include` files that a LilyPond file depends on?
> >> Even better, one that
On Mon 18 May 2020 at 10:29:22 (-0400), Fr. Samuel Springuel wrote:
> > On 18 May, 2020, at 9:37 AM, antlists wrote:
> >
> > define trombone-notes.ly as a target, define it as changed if its
> > dependencies change, and say "it doesn't exist as a file that can be
> > created with a command".
>
Hi all,
Is it possible to use the command in lilypond-book and
not create a link to the LY file
in an HTML document? I'm hoping there is some automation available
with lilypond-book.
Thanks,
David
Hello Paul,
> [...]If I'm writing music in F, then I suggest that I be able to use *bF*
> as a pitch instead of *bf*. The *F* would indicate that all subsequent *b*s
> would be flattened until one is encountered with a different accidental or
> until the end of the current music expression. It
> On 18 May, 2020, at 9:37 AM, antlists wrote:
>
> define trombone-notes.ly as a target, define it as changed if its
> dependencies change, and say "it doesn't exist as a file that can be created
> with a command".
Right, that’s the step I’m trying to automate. Make itself cannot determine
Am Montag, den 18.05.2020, 14:37 +0100 schrieb antlists:
> On 18/05/2020 13:44, David Kastrup wrote:
> > antlists writes:
> >
> > > On 15/05/2020 21:17, Fr. Samuel Springuel wrote:
> > > > Now I just need to turn this list into something that can be
> > > > used to
> > > > figure out if the
On 18/05/2020 13:44, David Kastrup wrote:
antlists writes:
On 15/05/2020 21:17, Fr. Samuel Springuel wrote:
Now I just need to turn this list into something that can be used to
figure out if the target needs to be recompiled.
As Jacques said, "make".
At the top of your directory structure
antlists writes:
> On 15/05/2020 21:17, Fr. Samuel Springuel wrote:
>> Now I just need to turn this list into something that can be used to
>> figure out if the target needs to be recompiled.
>
> As Jacques said, "make".
>
> At the top of your directory structure you can have a makefile, and it
On 15/05/2020 21:17, Fr. Samuel Springuel wrote:
Now I just need to turn this list into something that can be used to figure out
if the target needs to be recompiled.
As Jacques said, "make".
At the top of your directory structure you can have a makefile, and it
just contains a list of all
36 matches
Mail list logo
