Re: [OT] Linux Users
Just tried that, and it doesn’t work :
\let\lilypond@envcode\lilypond
\protected\def\lilypond{\def\reserved@a{lilypond}%
\ifx\reserved@a\@currenv \expandafter\lilypond@envcode
\else \expandafter \lily \fi}
I think it has something to do with \expandafter, but I don’t know TeX
enough to be sure…
2017-11-19 20:39 GMT+01:00 Abbé Jacques Peron
:
> 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...
>>>
>>> The environment is defined as `ly`, but there is a `lilypond` alias. So
> `\begin{lilypond}` just works.
>
> Basically:
>>>
>>> \newenvironment{lilypond}
>>> {...}
>>> {...}
>>>
>>> \newcommand{\lilypondcommand}{...}
>>>
>>> \let\lilypond@envcode\lilypond
>>> \protected\def\lilypond{\def\reserved@a{lilypond}%
>>>\ifx\reserved@a\@currenv \expandafter\lilypond@envcode
>>>\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'm going to try it just now.
>
> 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}
>
>
> As you are using `\ly`, as soon as I don't modify it, it'll work.
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [OT] Linux Users
And @David Kastrup : thank you very much for telling me how to achieve the
same name for environment and command !
2017-11-19 22:05 GMT+01:00 Abbé Jacques Peron
:
> I found the problem : it came from @currenv, that is in fact @currenvir.
> After last modifications
> <https://github.com/jperon/lyluatex/commit/53ed227b4857b19d95598f1d25100e508c685c3c>,
> I think lyluatex should work as a drop-in replacement for lilypond-book,
> while keeping backward compatibility for those who already used lyluatex.
>
> Please feel free to test and report bugs
> <https://github.com/jperon/lyluatex/issues> !
>
>
> 2017-11-19 20:54 GMT+01:00 Abbé Jacques Peron <
> abbe.jacques.pe...@gmail.com>:
>
>> Just tried that, and it doesn’t work :
>>
>> \let\lilypond@envcode\lilypond
>> \protected\def\lilypond{\def\reserved@a{lilypond}%
>> \ifx\reserved@a\@currenv \expandafter\lilypond@envcode
>> \else \expandafter \lily \fi}
>>
>> I think it has something to do with \expandafter, but I don’t know TeX
>> enough to be sure…
>>
>>
>>
>> 2017-11-19 20:39 GMT+01:00 Abbé Jacques Peron <
>> abbe.jacques.pe...@gmail.com>:
>>
>>> 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...
>>>>>
>>>>> The environment is defined as `ly`, but there is a `lilypond` alias.
>>> So `\begin{lilypond}` just works.
>>>
>>> Basically:
>>>>>
>>>>> \newenvironment{lilypond}
>>>>> {...}
>>>>> {...}
>>>>>
>>>>> \newcommand{\lilypondcommand}{...}
>>>>>
>>>>> \let\lilypond@envcode\lilypond
>>>>> \protected\def\lilypond{\def\reserved@a{lilypond}%
>>>>>\ifx\reserved@a\@currenv \expandafter\lilypond@envcode
>>>>>\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'm going to try it just now.
>>>
>>> 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}
>>>
>>>
>>> As you are using `\ly`, as soon as I don't modify it, it'll work.
>>>
>>
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [OT] Linux Users
>
> 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...
>>
>> The environment is defined as `ly`, but there is a `lilypond` alias. So
`\begin{lilypond}` just works.
Basically:
>>
>> \newenvironment{lilypond}
>> {...}
>> {...}
>>
>> \newcommand{\lilypondcommand}{...}
>>
>> \let\lilypond@envcode\lilypond
>> \protected\def\lilypond{\def\reserved@a{lilypond}%
>>\ifx\reserved@a\@currenv \expandafter\lilypond@envcode
>>\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'm going to try it just now.
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}
As you are using `\ly`, as soon as I don't modify it, it'll work.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [OT] Linux Users
I found the problem : it came from @currenv, that is in fact @currenvir.
After last modifications
<https://github.com/jperon/lyluatex/commit/53ed227b4857b19d95598f1d25100e508c685c3c>,
I think lyluatex should work as a drop-in replacement for lilypond-book,
while keeping backward compatibility for those who already used lyluatex.
Please feel free to test and report bugs
<https://github.com/jperon/lyluatex/issues> !
2017-11-19 20:54 GMT+01:00 Abbé Jacques Peron
:
> Just tried that, and it doesn’t work :
>
> \let\lilypond@envcode\lilypond
> \protected\def\lilypond{\def\reserved@a{lilypond}%
> \ifx\reserved@a\@currenv \expandafter\lilypond@envcode
> \else \expandafter \lily \fi}
>
> I think it has something to do with \expandafter, but I don’t know TeX
> enough to be sure…
>
>
>
> 2017-11-19 20:39 GMT+01:00 Abbé Jacques Peron <
> abbe.jacques.pe...@gmail.com>:
>
>> 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...
>>>>
>>>> The environment is defined as `ly`, but there is a `lilypond` alias. So
>> `\begin{lilypond}` just works.
>>
>> Basically:
>>>>
>>>> \newenvironment{lilypond}
>>>> {...}
>>>> {...}
>>>>
>>>> \newcommand{\lilypondcommand}{...}
>>>>
>>>> \let\lilypond@envcode\lilypond
>>>> \protected\def\lilypond{\def\reserved@a{lilypond}%
>>>>\ifx\reserved@a\@currenv \expandafter\lilypond@envcode
>>>>\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'm going to try it just now.
>>
>> 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}
>>
>>
>> As you are using `\ly`, as soon as I don't modify it, it'll work.
>>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lyluatex, call for pre-beta review
Hello,
Le 11 mars 2018 00:24:48 GMT+01:00, Craig Dabelstein
a écrit :
>Hi Urs,
>
>I can't get it to find my
>installation of Lilypond. Could you give me an example of the code I
>need
>to point lyluatex to a Lilypond installation?
You should use the option "program":
\usepackage[program= PATH/TO/LILYPOND]{lyluatex}
Hoping this helps,
Fr. Jacques Peron +
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating multi-score books
Hello,
Another alternative is lyluatex, that you may find here :
https://github.com/jperon/lyluatex.
For this to work, you'll have to use lualatex.
Jacques Peron +
Le 16 févr. 2017 14:32, "Urs Liska" a écrit :
Am 16. Februar 2017 07:02:10 MEZ schrieb Don Gingrich <
gingr...@internode.on.net>:
>I've got a basic problem, and I'm not having much
>joy with the documentation.
>
>Over the past few years I've created several scores
>for folk songs.
>
>Now, I'm going to be doing a workshop discussing
>their origins.
>
>What I'd like to create is:
>
>
>
>
>
>
>
>
>
>
>
>and so on
>
>I'm probably more familiar with LaTeX than
>LilyPond, so I'd really prefer to do the cover
>page and discussion in TeX and the scores
>in LilyPond.
If I don't misunderstand you I would compile the songs individually and
include them using \includepdf.
HTH
Urs
>
>Note that some of the scores were originally
>entered using MuseScore and the converted
>using xml2ly -- so the LilyPond code is *ugly*
>but works as a standalone score. In my copious
>free time I'd like to shift these converted scores
>into clean code, but it's in the "if it ain't broke."
>category unless the converted stuff is likely to be
> breaking things.
>
>My minimal example winds up being several hundred
>lines, so I've not included it.
>
>I tried this:
>
>\header {
> title = "Eight miniatures"
> composer = "Igor Stravinsky"
>}
>\score {
> …
> \header { piece = "Romanze" }
>}
>\markup {
> …text of second verse…
>}
>\markup {
> …text of third verse…
>}
>\score {
> …
> \header { piece = "Menuetto" }
>}
>
>With including the score files and it
>did not work.
>
>I tried this first:
>
>\documentclass[a4paper]{article}
>
>\begin{document}
>
>Documents for \verb+lilypond-book+ may freely mix music and text.
>For example,
>
>Options are put in brackets.
>
>Larger examples can be put into a separate file, and introduced with
>\verb+\lilypondfile+.
>
>\lilypondfile[quote,noindent]{MyFileName.ly}
>
>(If needed, replace @file{screech-and-boink.ly} by any @file{.ly} file
>you put in the same directory as this file.)
>
>\end{document}
>
>And all that I got was the filename printed where the score should
>have been.
>
>I also looked at the thread titled:
>"Problem with lilypond-book and \markup blocks" from 2007
>But when I tried to add a header after the \score{ -- e.g.
>\score {
> \header{
> title = "some silly thing"
> composer = "Not Mozart"
>}
>{
><<
>
>The title and composer disappeared into the ether -- clearly
>the method here only works for snippets, not full or multi-page
>scores.
>
>I keep banging at this and getting nowhere.
>
>
>As putting a bunch of individual scores together into a book may
>be a more or less common task, a good template would be brilliant
>and potentially useful for others
>
>Thanks,
>
>-Don
>
>--
>Don Gingrich
>
>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
