Ah! Now I get it! Thank you very much!
On Sat, Oct 2, 2021 at 6:39 PM David Kastrup wrote:
> "Omid Mo'menzadeh" writes:
>
> > I'm just re-stating this to make sure I'm getting it right: Definitions
> are
> > lazy, and the expression in front of # is lazy too, so it gets a chance
> to
> > see
"Omid Mo'menzadeh" writes:
> I'm just re-stating this to make sure I'm getting it right: Definitions are
> lazy, and the expression in front of # is lazy too, so it gets a chance to
> see the definition once it's done? Am I right?
It's not a definition but an assignment, and the assignment is
I'm just re-stating this to make sure I'm getting it right: Definitions are
lazy, and the expression in front of # is lazy too, so it gets a chance to
see the definition once it's done? Am I right?
That's good to know!
On Sat, Oct 2, 2021 at 4:00 PM David Kastrup wrote:
> "Omid Mo'menzadeh"
"Omid Mo'menzadeh" writes:
> Of course!I just attached two files that demonstrate the difference.
>
> On Sat, Oct 2, 2021 at 3:30 PM David Kastrup wrote:
>
>> "Omid Mo'menzadeh" writes:
>>
>> > I didn't know about $ at all! Where in the documentation can I find more
>> > about it? It was hard
Of course!I just attached two files that demonstrate the difference.
On Sat, Oct 2, 2021 at 3:30 PM David Kastrup wrote:
> "Omid Mo'menzadeh" writes:
>
> > I didn't know about $ at all! Where in the documentation can I find more
> > about it? It was hard to search for!
> >
> > I tried it, but
"Omid Mo'menzadeh" writes:
> I didn't know about $ at all! Where in the documentation can I find more
> about it? It was hard to search for!
>
> I tried it, but it doesn't seem to find my variable "vocal" defined in the
> same .ily file. I tried using #(top-repl) and $(top-repl) too, in the #
>
I didn't know about $ at all! Where in the documentation can I find more
about it? It was hard to search for!
I tried it, but it doesn't seem to find my variable "vocal" defined in the
same .ily file. I tried using #(top-repl) and $(top-repl) too, in the #
version it knows what \vocal is, but in
Le 01/10/2021 à 15:05, David Kastrup a écrit :
Right. Sorry.
No need to be sorry. Just happens.
It's not like there is no potential for confusion,
cf. commits 662c549602 and e12ee4107c0…
Jean
Jean Abou Samra writes:
> Le 01/10/2021 à 14:09, David Kastrup a écrit :
>> $*undefined*
>
> I think you mean
>
> $*unspecified*
Right. Sorry.
--
David Kastrup
Le 01/10/2021 à 14:09, David Kastrup a écrit :
$*undefined*
I think you mean
$*unspecified*
Jean
"Omid Mo'menzadeh" writes:
> Thank you for your reply. This is working, but like this:
> main = #(if (not (defined? 'is-loaded-file))
> #{
> \score { \vocal }
> #}
> )
>
> \main
>
> Any idea why it wouldn't work without defining the main variable? It's fine
> for me, but I don't get why
Funny!
I have no idea. Smarter people on this list will certainly know, though.
> 1 okt. 2021 kl. 13:31 skrev Omid Mo'menzadeh :
>
> Thank you for your reply. This is working, but like this:
> main = #(if (not (defined? 'is-loaded-file))
> #{
> \score { \vocal }
> #}
> )
>
> \main
>
Thank you for your reply. This is working, but like this:
main = #(if (not (defined? 'is-loaded-file))
#{
\score { \vocal }
#}
)
\main
Any idea why it wouldn't work without defining the main variable? It's fine
for me, but I don't get why the following snippet does not work for me:
#(if
There might be more elegant ways to do it (there probably is), but I have a
variable I define in my output files, is-loaded-file and then I can use #(if
(defined? 'is-loaded-file) … ) in the definition files to test. This requires a
situation where there’s a clear separation between ”definition
Hello all. This might be a weird thing to seek, but here is the scenario:
I have several files defining (but not using) different parts of the score,
which other files use to construct several output types.
But the problem is the command `lilypond -l WARNING -o /path/to/file.ly`
does not show a
15 matches
Mail list logo
