Graham Percival writes:
> On Sun, Sep 19, 2010 at 10:07:28PM +0200, Martin Tarenskeen wrote:
>>
>> I agree, but: Since many people use these abbreviations, Would it be
>> an an idea to mention those abreviations on manuals.html and in the
>> titles at the top of the manuals. something like:
>>
On 9/19/10 3:46 PM, "Patrick Schmidt" wrote:
> Hi all,
>
> I have several files with definitions of guitar fret diagrams for
> various chord shapes (e.g. c-shape.ly, a-shape.ly, g-shape.ly, e-
> shape.ly and d-shape.ly). I can't include all of these files at the
> same time in the main file a
Hi all,
I have several files with definitions of guitar fret diagrams for
various chord shapes (e.g. c-shape.ly, a-shape.ly, g-shape.ly, e-
shape.ly and d-shape.ly). I can't include all of these files at the
same time in the main file as quite a few chord alternatives start on
the same pit
Sorry about that, brief problem with my email that resulted in
double-posting.
Excellent answer sorted my question out immediately, thanks again.
Gerard
On Sun, Sep 19, 2010 at 3:17 PM, Phil Holmes wrote:
> Check your inbox for the answer to this question you were sent yesterday.
>
>
__
On Sun, Sep 19, 2010 at 10:07:28PM +0200, Martin Tarenskeen wrote:
>
> On Sun, 19 Sep 2010, David Kastrup wrote:
>
> >It is agreed-upon best practice _not_ to use those abbreviations on the
> >general user list.
>
> I agree, but: Since many people use these abbreviations, Would it be
> an an ide
- Original Message -
From: "David Kastrup"
To:
Sent: Sunday, September 19, 2010 8:36 PM
Subject: Re: best practices
"Phil Holmes" writes:
I'm generally normally quite helpful (or try to be). It was just that
Graham had given you all the information you needed - you just needed
to
On Sun, 19 Sep 2010, David Kastrup wrote:
"Phil Holmes" writes:
Graham had given you all the information you needed - you just needed
to read it and spend a little while wondering what LM could stand for.
It is agreed-upon best practice _not_ to use those abbreviations on the
general user
On Sun, Sep 19, 2010 at 09:36:21PM +0200, David Kastrup wrote:
> "Phil Holmes" writes:
>
> > I'm generally normally quite helpful (or try to be). It was just that
> > Graham had given you all the information you needed - you just needed
> > to read it and spend a little while wondering what LM c
"Phil Holmes" writes:
> I'm generally normally quite helpful (or try to be). It was just that
> Graham had given you all the information you needed - you just needed
> to read it and spend a little while wondering what LM could stand for.
It is agreed-upon best practice _not_ to use those abbre
> >>> Phil Holmes philholmes.net> writes:
> And anyway, I only said "Um"
It was an angry Um! :)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
- Original Message -
From: "Trevor Daniels"
To: "Graham Percival" ; "aliteralmind"
Cc:
Sent: Sunday, September 19, 2010 6:20 PM
Subject: Re: best practices
Graham Percival wrote Sunday, September 19, 2010 5:22 PM
On Sun, Sep 19, 2010 at 5:09 PM, aliteralmind
wrote:
Phil Holmes
Graham Percival wrote Sunday, September 19, 2010 5:22 PM
On Sun, Sep 19, 2010 at 5:09 PM, aliteralmind
wrote:
Phil Holmes philholmes.net> writes:
> Where exactly are they, please?
Um. Learning Manual 5. Entitled "Working on LilyPond
projects".
I read the learning manual. I didn't find th
- Original Message -
From: "aliteralmind"
To:
Sent: Sunday, September 19, 2010 5:34 PM
Subject: Re: best practices
Ok. I give I give.
I have been studying the documentation intensely and
thought there was something I missed. I already read it.
It was a genuine question and I was su
Ok. I give I give.
I have been studying the documentation intensely and
thought there was something I missed. I already read it.
It was a genuine question and I was surprised by the
response.
Devs don't want to be pin pricked, and newbies don't
want to be fearful.
I appreciate and am amazed
On Sun, Sep 19, 2010 at 5:09 PM, aliteralmind
wrote:
> Phil Holmes philholmes.net> writes:
>> > Where exactly are they, please?
>>
>> Um. Learning Manual 5. Entitled "Working on LilyPond
> projects".
>
> I read the learning manual. I didn't find the words "best
> practices" in it, and thought t
On Sep 19, 2010, at 6:09 PM, aliteralmind wrote:
> Phil Holmes philholmes.net> writes:
>>> Where exactly are they, please?
>>
>> Um. Learning Manual 5. Entitled "Working on LilyPond
> projects".
>
> I read the learning manual. I didn't find the words "best
> practices" in it, and thought t
Phil Holmes philholmes.net> writes:
> > Where exactly are they, please?
>
> Um. Learning Manual 5. Entitled "Working on LilyPond
projects".
I read the learning manual. I didn't find the words "best
practices" in it, and thought there was something else I
was missing.
I don't appreciate the
Thanks a lot!!!
-akj
On Sep 19, 2010, at 10:11 AM, Alexander Kobel wrote:
> On 2010-09-19 15:38, Alex Jones wrote:
>> I am having a problem with bar lines, if I put the following around a staff
>> break
>>
>> \bar "||"
>> \break
>> \bar "|:"
>>
>> I get the repeat sign on the start of the sta
- Original Message -
From: "aliteralmind"
To:
Sent: Sunday, September 19, 2010 4:01 PM
Subject: Re: best practices
Graham Percival gmail.com>
We *have* a set of "best practices". They're LM 5
Working on
LilyPond projects. I wrote them two years ago, and
AFAIK nobody
has ever
Graham Percival gmail.com>
> We *have* a set of "best practices". They're LM 5
Working on
> LilyPond projects. I wrote them two years ago, and
AFAIK nobody
> has ever read them.
Where exactly are they, please?
___
lilypond-user mailing list
lilyp
Check your inbox for the answer to this question you were sent yesterday.
--
Phil Holmes
- Original Message -
From: Gerard McConnell
To: lilypond-user@gnu.org
Sent: Saturday, September 18, 2010 12:41 PM
Subject: piano staves and lyrics
Hello,
I've included a minimal ex
On 2010-09-19 15:38, Alex Jones wrote:
I am having a problem with bar lines, if I put the following around a staff
break
\bar "||"
\break
\bar "|:"
I get the repeat sign on the start of the staff, but not the double bar on the
end of the previous staff. [...]
Anyone have any ideas what I'm do
I am having a problem with bar lines, if I put the following around a staff
break
\bar "||"
\break
\bar "|:"
I get the repeat sign on the start of the staff, but not the double bar on the
end of the previous staff.
I am using partial bars before and after the break, but through
experimentat
Hello,
I've included a minimal example below; why doesn't it work and how do I
correct it?
(It works fine without the alto and tenor parts.)
Many thanks yet again,
Gerard
\version "2.12.2"
\score {
\new PianoStaff {
<<
\new Staff {
<<
\new Voice="soprano" { \voiceOne
On 19 September 2010 08:11, Joshua Armenta wrote:
>
> Hello,
> I have a score with multiple staves. One instrument enter into unmetered
> timing and performs a cadenza, the other five instruments rest. The problem
> is that when the file is compiled, the barlines in the output is completely
> thro
25 matches
Mail list logo
