|
From: | Abbé Jacques Peron |
Subject: | Re: [OT] Linux Users |
Date: | Sun, 19 Nov 2017 20:39:19 +0100 |
Neither are called lilypond. It's not particularly great, but there are
examples for the sharing of command and environment. Basically you
check whether @currenvir is set to LilyPond. As long as you don't
_nest_ those constructs...
Basically:
\newenvironment{lilypond}
{...}
{...}
\newcommand{\lilypondcommand}{...}
address@hidden
\protected\def\lilypond{\def\raddress@hidden
address@hidden@currenv address@hidden
\else \expandafter \lilypondcommand \fi}
Ugly, sure. But I think LilyPond upstream would be sympathetic to
making command and environment named differently in the long run.
I don’t know enough about (La?)TeX internals to understand the code above but if you redefined the command \lilypond, would things like the following still be possible?
\newenvironment{dly}{
\center
\ly
\language "deutsch"
\paper {
##(define fonts
(set-global-fonts
##:music "cadence"
##:brace "cadence"
##:roman "Vollkorn"
##:factor (/ staff-height pt 20)))
}
\layout {
% some other general things
}
% some includes and function definitions
}{\endly\endcenter}
[Prev in Thread] | Current Thread | [Next in Thread] |