[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ly:parser-parse-string again
From: |
David Kastrup |
Subject: |
Re: ly:parser-parse-string again |
Date: |
Tue, 05 Jul 2016 19:54:44 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Urs Liska <address@hidden> writes:
> Am 05.07.2016 um 18:01 schrieb David Kastrup:
>
>> The alternative is cloning a fresh parser. There might be some
>> incentive to carry over the current notename language automatically.
>> But it does not make sense to carry over the whole state stack when
>> cloning. So what to do if we are not actually in notemode currently?
>
> Makes sense.
> But actually one would rather expect the default to be active just like
> with regular files.
Regular files don't get a fresh parser. They get the parser in the
state where \maininput in ly/init.ly leaves it.
You'll notice that ly/init.ly sets up the default notename language
before that.
I'm not saying that this is all fabulous. But in the current state,
including/interpreting LilyPond files via Scheme code is more or less
playing around with internals, and the internals have behavior tied to
LilyPond's architecture more than to user expectations.
--
David Kastrup