This is good info; does anybody want to submit changes to the manual?
It would be good if it were a "normal user" who suggested the changes.
http://lilypond.org/web/devel/participating/documentation-adding
- Graham
Mats Bengtsson wrote:
Some further clarifications below.
Quoting Erik Sandbe
Juergen Reuter wrote:
On Sun, 27 Aug 2006, Mats Bengtsson wrote:
Some further clarifications below.
...
However, as Erik says below, if you want to store the lyrics into a
variable, you have to do
mylyrics = \lyricmode { Here is my ly -- rics }
and then \lyricsto ... \mylyrics
Still remain
On Sun, 27 Aug 2006, Mats Bengtsson wrote:
Some further clarifications below.
...
However, as Erik says below, if you want to store the lyrics into a variable,
you have to do
mylyrics = \lyricmode { Here is my ly -- rics }
and then \lyricsto ... \mylyrics
Still remains the question why at a
Some further clarifications below.
Quoting Erik Sandberg <[EMAIL PROTECTED]>:
On Sunday 27 August 2006 07:26, Graham Percival wrote:
Ted Walther wrote:
> The documentation of lyrics has got me befuddled on the notion of
> contexts, as I haven't seen anywhere it clearly says what I can do in
>
On Sunday 27 August 2006 07:26, Graham Percival wrote:
> Ted Walther wrote:
> > The documentation of lyrics has got me befuddled on the notion of
> > contexts, as I haven't seen anywhere it clearly says what I can do in
> > lyricsmode that I can't do in lyricsto, although the documentation does
> >
Ted Walther wrote:
The lilypond manual is so good, and appears so
complete, that I forgot I was still in Unix land.
Burn! That was harsh. I'm going to save this for .sig material. :)
On a serious note...
In Windows, there is
an immense amount of repetition, which saves people from huntin
Quoting Donald Axel <[EMAIL PROTECTED]>:
Is it
= #"oboe"
or is it
= "oboe"
Both work equally well (at least in versions 2.8 and later).
/Mats
On Thu, 24 Aug 2006 14:47:33 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>>
>>> \new Staff {
>>> \time 3/4
>>> \key
Is it
= #"oboe"
or is it
= "oboe"
On Thu, 24 Aug 2006 14:47:33 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> >>
> >>> \new Staff {
> >>> \time 3/4
> >>> \key d \major
> >>> \clef treble
> >>> \set Staff.midiInstrument = #"oboe"
> >>
> >>
> >> That work
On Thu, Aug 24, 2006 at 02:47:33PM +0200, Mats Bengtsson wrote:
I think the problem here was the general knowledge of how to set
properties, which certainly is described in the manual, but probably
not in the parts of the manual which you read the first time. In my
opinion, we cannot keep repeati
Graham Percival wrote:
Ted Walther wrote:
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
Just as any other property setting that applies to a certain Staff, you
have to do the setting within the Staff context, for example:
\new Staff {
\time 3/4
\key d \major
Ted Walther wrote:
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
Just as any other property setting that applies to a certain Staff, you
have to do the setting within the Staff context, for example:
\new Staff {
\time 3/4
\key d \major
\clef treble
\set Sta
Ted Walther wrote:
Is there a Debian-format repository where I can install the latest
stable version of lilypond using apt-get?
I don't believe anyone is packaging LilyPond for Debian. As you
probably the latest Debian package is 2.6.3. The GUB's work fine even
if there may be some redundanc
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
\set Staff.midiInstrument = #"oboe"
I have tried it in the top level, and inside a \score section. It
makes no difference; the resulting midi file always uses the default
grand piano.
Just as any other property setting that appli
Quoting Ted Walther <[EMAIL PROTECTED]>:
I am running Debian unstable, with lilypond 2.6.3 for typesetting,
timidity 2.13.2 to play midi files, and freepats 20060219 to provide the
midi patchsets.
I recommend you to upgrade to the latest stable version, 2.8. The
installation package available
I am running Debian unstable, with lilypond 2.6.3 for typesetting,
timidity 2.13.2 to play midi files, and freepats 20060219 to provide the
midi patchsets.
I notice in the manual it says the patch set has to be named exactly,
with no variance in case allowed. So I have been pasting in different
15 matches
Mail list logo
