On 11/21/22 05:36, Silas S. Brown wrote:
% In 2/4 time, I want to write 4 bars rest
% followed by 2 minims (half-notes).
% The bar numbering comes out differently:
\version "2.22.2"
\relative c' {
\set Score.skipBars = ##t
\time 2/4 R2*4 c ^"This is bar 5" \break
d ^"I think this should be bar
in the top staff ( or top of each group of
staves).
You may see how this relates to your solution.
HTH
Paul Scott
> <<
> \new Staff { \time 4/4 c''1 \time 3/4 c''2. }
> \new Staff { \time 4/4 c''1 \time 3/4 \grace b'8 c''2. }
&
That should be R2.\fermataMarkup
for a whole measure rest.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
y? just *any*
> note?) then what about adding a note or measure?
>
> It could be memory related - using some excessive NPP for instance - but
> it sounds odd that a 'single note' would make that much difference.
This is exactly what I have seen:
Debian Linux sid
LilyPond 2.1
The following changes the clef for the cancelled key signature but uses
the previous clef for the new key signature.
\version "2.19.5"
{
\key f \major R1 \cueClef bass \key g \major R1 \cueClefUnset
R1 \cueClef alto \key bes \major R1
}
global= {
> \time 4/4
> \key c \major
> s4*4 \bar "||"
\grace s8 %here should fix the problem
HTH
Paul Scott
> s4*4 \bar "|."
> }
>
> violinOne = \relative c'' {
> c1
> \grace f8 e1
> }
>
> violinTwo = \relative
On 11/11/2011 06:09 PM, Peekay Ex wrote:
Hello,
2011/11/12 Paul Scott:
..
The text representation of f sharp in germany and austria is fis. When
you want to describe a note in text, that's how you do it. In english, we
write "f sharp";
In a book probably. In an email F#.
ribe a note in text, that's how you do it. In english, we
> write "f sharp";
In a book probably. In an email F#.
Paul Scott
> in german, they write "fis".
>
>> Using those signs in a text file would be a new thing. Maybe
>> accidentals should be wr
On 03/24/2011 08:31 AM, Phil Holmes wrote:
"Paul Scott" wrote in message
news:4d8a4f6e.6030...@ultrasw.com...
The half rest at the end of the line has almost no space.
Attached is an example with a second line with less notes that looks
normal compared to the first line.
That&
Hi,
The following code produces a spacing error near the end of the line
that looks to me similar to
Issue 1472.
\version "2.13.54"
\relative c'' {
\key ges \major a1 b c d c8 b c b c b c b a4 b c d r8 e d c r2
\key fis \major \break
This says 2.13.48.
Paul Scott
On 01/29/2011 09:45 PM, Jay Anderson wrote:
Below is the gdb trace from the segfault:
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later<http://gnu.org/licenses/gpl.html>
This is free so
On 01/06/2011 08:10 AM, Phil Holmes wrote:
- Original Message - From: "Paul Scott"
To:
Sent: Thursday, January 06, 2011 6:29 AM
Subject: collision between MMR and key signature
Hi,
This seemed to have started several development versions ago but I
haven't
verified i
s.
Most important is workaround:
\once \override Score.MetronomeMark #'non-break-align-symbols = #'()
\override Score.MetronomeMark #'break-align-symbols = #'(time-signature)
Paul Scott
___
bug-lilypond mailing list
bug-li
On Mon, Sep 06, 2010 at 09:50:11PM +0100, Neil Puttock wrote:
> On 6 September 2010 20:03, Paul Scott wrote:
>
> > Now I get mixed results with \tempo placement. (bug 684) Some start over
> > the
> > time signature and some start over the key signature. One of those
On Mon, Sep 06, 2010 at 10:57:36AM -0700, Paul Scott wrote:
> On Mon, Sep 06, 2010 at 08:32:24AM +, lilyp...@googlecode.com wrote:
> > Status: Accepted
> > Owner:
> > Labels: Type-Defect Priority-Critical Regression
> >
> > New issue 1251 by brownian.box:
com/p/lilypond/issues/detail?id=1251
>
> Sorry, could not describe better.
>
> This seems to be caught and "almost fixed"; anyway, "for the record".
>
> Reported by Paul Scott:
> http://lists.gnu.org/archive/html/bug-lilypon
On Fri, Sep 03, 2010 at 11:30:58PM -0700, Paul Scott wrote:
> I'm getting a seg. fault with 2.13.32. I haven't got the exact
> cause yet but one variable is that I only see the fault when I add a
> second \new Staff in a StaffGroup. I have two parts based on the
> same sc
est #'expand-limit = #1
a'1 R1*2 \clef bass R1*2 b1 b1 R1*2 \clef treble R1*10
}
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi,
2.13.29
If there are two identical \tempo's in sequence the second one will not
be printed.
\version "2.13.29"
{
\tempo \markup{ Tempo } a'1 a' a'
s1*0^\markup{ Tempo } a'1 a'
\tempo \markup{ Tempo } a' a'
\tempo \markup{ Temp
I saw that email, and this one. Our mailing lists do not send you
an email if you're the one who sent it, and if you are CC'd on an
email, it only sends it to you once.
If I understand you correctly the lists always send me my posts.
C
tBeamCount = #2 \set stemRightBeamCount = #1 c16 c8 }
\time 3/8 c8. c16 c8 %works as expected outside of triplet
}
Thanks,
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
much of a response.
(I'm not complaining considering all the work that is being done on the
great documentation and getting us close to 2.12)
I find that some combinations of dash ("-") like ---> inhibit emacs
indentation. I just use ^ or _ instead to keep em
down menus.
You need to read some of the manual before attempting to run LilyPond.
http://lilypond.org/web/documentation
HTH,
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
portant thing is that the documentation is being completely
rewritten and no fixes will probably me made to the 2.10.x
documentation. Have a look at the 2.11.x documentation.
HTH
Paul Scott
> Thank you about your time, i am newbie ☺, just t
> \paper{
> printallheaders=##t
> }
> \header{
> title = "Title"
> }
> \score{
> \relative c'{
> c
> }
> }
> = end example.ly =
>
That's a pretty old ver
2.11.37
Attaching "--->" to a note name seems to break the tabbing code in
lilypond-mode. When that occurs in a line pressing the Tab key on the
next line does nothing.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond
the end of the repeated section
since ":||" is apparently undefined:
{ a'1 \repeat volta 2 { g'1 } \break \bar ":||" f'1 g'1 }
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
'Save' and 'Compile...'.
Is this a new bug?
No
Have you had any other reports of the Intel package not
working under Leopard?
Yes.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Bernardino Rozada Fernández wrote:
He instalado LilyPond 2.11.31 de todas las maneras posibles y no aranca en
ninguna de ellas.
?En que clase de machina? PC, Mac, Linux?
Ingles por favor.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond
Viviane Baumert wrote:
I want to download LilyPond for Mac OS 10
Just go here and choose between Intel and PowerPC:
http://lilypond.org/web/install/
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman
Paul Scott wrote:
Trevor Bača wrote:
On 3/3/07, Paul Scott <[EMAIL PROTECTED]> wrote:
Graham Percival wrote:
(snip)
>
> As a Canadian, I'm mortified to find myself agreeing with the
Yanks :P
> , but that is the case. I've never heard of a "pause" being us
Trevor Bača wrote:
On 3/3/07, Paul Scott <[EMAIL PROTECTED]> wrote:
Graham Percival wrote:
(snip)
>
> As a Canadian, I'm mortified to find myself agreeing with the Yanks :P
> , but that is the case. I've never heard of a "pause" being used in
> a fo
ans.
Still, the purpose of the glossary is to educate such people (I'm now
including the whole UK and their penal colony as "inexperienced" :),
so I've added "pause" to the glossary. :)
The other American English wo
Graham Percival wrote:
Paul Scott wrote:
Graham Percival wrote:
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=324
The bug you recorded is not the primary bug I was reporting and as I
noted doesn't even happen in a normal part.
The bug is that the "stems&quo
Graham Percival wrote:
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=324
I don't think it's related to 318, since this problem persists if we
use half notes instead of whole notes.
The bug you recorded is not the primary bug I was reporting and as I
noted doesn't even hap
Mats Bengtsson wrote:
This seems to be related to
http://code.google.com/p/lilypond/issues/detail?id=318
I forward it to bug-lilypond.
Thanks. Sorry I didn't have time to do more research on the bug this
morning.
The "line feed" goes away if you use
\new Staff {
\clm \clma << \clm \\ \clma >
With 2.11.17 I get the same segfault with code like the code I sent Joe Neeman
privately on a Mac:
Preprocessing graphical objects...
programming error: tried to space systems on a bad number of pages
continuing, cross fingers
Segmentation fault
Paul Scott
Joe Neeman wrote:
On 2/6/07, Paul Scott <[EMAIL PROTECTED]> wrote:
Paul Scott wrote:
> 2.11.16 gives the following error on code that worked on 2.11.15.2.
> This happens on both x86 and Mac OS X (Mac doesn't segfault but gives
> the same error message. I'm sorry I
Joe Neeman wrote:
On 2/6/07, Paul Scott <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> Issue 277: Bus error with page-break-permission +
line-break-permission +
ragged-right
> http://code.google.com/p/lilypond/issues/detail?id=277
>
> Comment #5 by joeneeman:
&g
Paul Scott wrote:
2.11.16 gives the following error on code that worked on 2.11.15.2.
This happens on both x86 and Mac OS X (Mac doesn't segfault but gives
the same error message. I'm sorry I don't have enough time to give a
short piece of code at the moment. I need to get
Labels: fixed_2_11_17
Does this imply 2.11.17 will be available soon?
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
ssing graphical objects...
warning: Can't fit systems on page -- ignoring between-system-padding
Layout output to `lullaby15r1.ps'...
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Thomas Frank wrote:
This is new in 2.11.15: Barnumbers and marks are put higher than the highest
note in a line...
or higher than any markup on the line! I really makes ugly spacing in
scores.
Paul Scott
\version "2.11.15"
\include "english.ly"
\header {
title
Han-Wen Nienhuys wrote:
Joe Neeman escreveu:
On 12/28/06, Paul Scott <[EMAIL PROTECTED]> wrote:
In 2.11.4 the following code doesn't pad the text over the R1. It works
fine otherwise. It also fails with outside-staff-padding. I see now
that 2.11.5 is out. It also fails
Paul Scott wrote:
Joe Neeman wrote:
On 12/28/06, *Paul Scott* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
In 2.11.4 the following code doesn't pad the text over the R1. It
works
fine otherwise. It also fails with outside-staff-padding. I see
now
Joe Neeman wrote:
On 12/28/06, *Paul Scott* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
In 2.11.4 the following code doesn't pad the text over the R1. It
works
fine otherwise. It also fails with outside-staff-padding. I see now
that 2.11.5 is ou
cript #'padding = #$padding #})))
\relative c'' {
#(textPad 5 #t)
R1^\markup{ rest } %tried w/ both "" and \markup
#(textPad 5 #t)
a4^"note" b c d
#(textPad 2 #t)
c1^"more text"
}
Paul Scott
___
bug-lil
Laura Conrad wrote:
"Paul" == Paul Scott <[EMAIL PROTECTED]> writes:
Paul> When using continuation lines, common figures are always put in the
Paul> same vertical position.
I know this is what the documentation says, but if you actually use
the p
ntinuation lines, common figures are always put in the same
vertical position. When this is unwanted, you can insert a rest with
|r|. The rest will clear any previous alignment. For example, you can write
<4 6>8 r8
instead of
<4 6>4
Paul Scott
Trent
- Original Message
~ }
\alternative { {f2 d} {f\repeatTie f,} }
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Graham Percival wrote:
Paul Scott wrote:
I had been thinking that this bug was combined with another tuplet bug
but looking at the bug listings I see I was wrong.
This code produces a tuplet bracket that slopes the opposite way as it
should and collides with the beam.
\version "2
3 { r16 dis cis] } c4 d e f f e d }
I would consider sponsoring a fix if necessary as this bug keeps me from
delivering an arrangement unless I change the beaming.
Thanks,
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.
Graham Percival wrote:
Thanks, that has (finally) been entered as
http://code.google.com/p/lilypond/issues/detail?id=103
I believe that turned out to be a feature related to continuation lines
and is documented in:
7.7.14 Figured bass
Paul
- Graham
Paul Scott wrote:
The attached
Simon Dahlbacka wrote:
> FWIW, you can still get it from http://lilypond.org/download/binaries/
Thanks! I didn't have that URL handy.
Paul
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
eeing what you saw. I
haven't heard back yet.
Paul Scott
>
> -- Forwarded message --
> From: Han-Wen Nienhuys <[EMAIL PROTECTED]>
> Date: Sep 2, 2006 5:54 PM
> Subject: LilyPond 2.9.17
> To: info-lilypond@gnu.org
>
>
> Hello!
>
> Lily 2.9.1
Yitz Gale wrote:
Paul, thanks for your attention to this issue.
Paul Scott wrote:
If you can carefully describe what you want
different than the current behavior I can
help you get it.
A chord at the beginning of a second or
subsequent repeat alternative should print
unconditionally
Yitz Gale wrote:
Paul Scott wrote:
I don't think it's a bug
in my understanding of how Lilypond works.
It is definitely a bug. See below.
I still don't think so. I have been using LilyPond for at least 4 years
and have produced many lead sheets and music with ch
Yitz Gale wrote:
Paul Scott wrote:
Yitz Gale wrote:
The Chord Name engraver with chordChanges = #t
does not print the chord at the beginning
of a repeat alternative if the chord at the
end of the previous repeat alternative was
the same.
The way I read the 2.6
ead of when
the chord changes.
Is that what you meant?
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Graham Percival wrote:
Trent Johnston wrote:
The simple example below produces the following messages:
Processing `C:/jEdit/instr.ly'
Parsing...
Interpreting music...
warning: can't find property type-check for `instrument'
(translation-type?). perhaps a typing error?
staffViolin = \new Sta
ent class breathing-sign-event
warning: Unknown event class breathing-sign-event[80][88][96][104][112]
P.S. Why does this usenet top-posting warning always appear when I paste some
part of my program? It is quite annoying!
I can't help with that. I'm su
Mats Bengtsson wrote:
I have submitted the following changes (the numerical values
correspond to
the BarNumber object):
|side-axis| (number):
|1|
If the value is #X (or equivalently 1), the object is placed
horizontally next to the other object. If the value is #Y or 0, it is
placed verti
Graham Percival wrote:
Paul Scott wrote:
Then in "7.2.3 Printing chord names" is the example:
...
I suggest that the two relevant chords in the example be shown as
f1:maj7
and c:maj7 to avoid any confusion here.
Thanks, fixed in CVS.
From some online research I may have
Alan Stern wrote:
On Wed, 2 Aug 2006, Mats Bengtsson wrote:
As I have already tried to explain, several different layout objects
have the "direction"
property and for some objects it means UP/DOWN for others it means
LEFT/RIGHT.
Ideally, we should have different documentation text
Mats Bengtsson wrote:
Paul Scott wrote:
If it would lead to as much work as you say then at least a verbal
description of what direction means should be included as it is for
(most?) other properties.
Please go ahead and suggest something, see
http://lilypond.org/web/devel/participating
it's just as confusing for a woodwind player. Let's see if we
get opinions from the other members of the orchestra.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Mats Bengtsson wrote:
Paul Scott wrote:
1. The documentation and/or implementation of BarNumber direction is
incorrect: #RIGHT and #LEFT give the same result as #UP and #LEFT
respectively. The documentation error may have just been the result
of an unfinished cut-and-paste. As far as I
Mats Bengtsson wrote:
Quoting Paul Scott <[EMAIL PROTECTED]>:
Mats Bengtsson wrote:
I'm still a bit confused. Do you want to determine
if the bar number is printed over the beginning or the end of the
measure?
I probably would be happy just being able to have UP and DOWN as
Mats Bengtsson wrote:
I guess you intended to send this to the mailing list, not to me
personally.
Yes. I was having some trouble with Thunderbird and accidently sent it
to you.
I'm still a bit confused. Do you want to determine
if the bar number is printed over the beginning or the end of t
o relevant chords in the example be shown as f1:maj7
and c:maj7 to avoid any confusion here.
Paul Scott
References
Visible links
1.
http://lilypond.org/doc/v2.9/Documentation/user/lilypond/lily-1454637116.ly
Hidden links:
2.
http://lilypond.org/doc/v2.9/Documentation/user/lily
Mats Bengtsson wrote:
Quoting Paul Scott <[EMAIL PROTECTED]>:
At least in the last several versions of the manual (this is from
2.9.12) the following appears implying that you can't have both UP
and RIGHT or DOWN and LEFT:
Yes, that's correct. For some layout object
GHT=1, CENTER=0)
DOWN gives me what I want but so does LEFT which isn't right presuming
UP and LEFT is the default.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
With 2.9.10 (GUB) the triplet bracket in the attached example goes the
wrong way.
Paul Scott
\version "2.9.10"
\relative c' { ees16[ g \times 2/3 { r16 dis cis] } c4 d e f f e d }
___
bug-lilypond mailing list
bug-lilypo
The attached file shows that some figures break figured bass in 2.9.10
and probably 2.8.3 as you have seen on the user list. Once certain
figures appear the vertical order of following figures doesn't work.
Paul Scott
\version "2.9.10"
\book{
\score{
<<
Han-Wen Nienhuys wrote:
Paul Scott schreef:
Mats' message reminded me of a "feature" that disappeared not too
long ago. There used to be some numbers following the message:
Calculating page breaks...
From this number you could easily see the number of pages (number of
bre
vement (which is often a \score) to be more
than one page. Didn't it work this way before \book was introduced?
(I'm not sure when \book was introduced).
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gn
s
that we have probably all seen with Finale! :)
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Mats Bengtsson wrote:
Quoting Paul Scott <[EMAIL PROTECTED]>:
That's right or for clarity I write c5*4:7
I would write that as c4*5:7 (5 times the duration of a quarter note
c: c4).
Thanks, Mats. That's actually what I do. I must have been tired when I
wr
Han-Wen Nienhuys wrote:
Paul Scott schreef:
Mats' message reminded me of a "feature" that disappeared not too
long ago. There used to be some numbers following the message:
Calculating page breaks...
From this number you could easily see the number of pages (number of
bre
sequential nature of the
piece. Is there a way to label sections? Can the rehearal marks be used for
this? Is there another way?
Either rehearsal marks or regular markup.
HTH,
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lis
tell whether my reformatting
attempts had changed the number of pages without having to refresh the
image.
It would seem easy to restore that.
Thank for considering it.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailm
Paul Scott wrote:
This code works as expected:
\version "2.8.1"
\relative c'' {
c8. d16 e8 f
\times 2/3 { c8. d16 e8 }
}
This code places the partial beam for the sixteenth note in the tuplet
on the wrong side of the stem. (It's the correct side for the flag
w
t they are ignored.
Has anyone run into this before?
It happens often when I have rhythmic mistakes in the music and goes
away when I find and correct them.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/li
Mats Bengtsson wrote:
Paul Scott wrote:
I believe I have read about a bug list but I don't find it
documented. I would have researched this but don't want to search
the whole bug list archive.
The newest easily browsable version of the bug list I know of is
available at http://li
sion "2.8.1"
\relative c'' { c8. d16 e8 f \times 2/3 { c8.[ d16 e8] } }
I believe I have read about a bug list but I don't find it documented.
I would have researched this but don't want to search the whole bug list
archive.
Paul Scott
__
in Thunderbird with:
View/Display Attachments Inline
checked.
Look at the original email and see if there is a paper clip icon.
Otherwise check the email source with
View/Message Source
to see if it really was an attachment no matter how you are viewing the
returned
rsalMark #'padding = #1.5
\mark "Bossa Nova"
I have a set of macros I use based on help Nicolas Sceaux gave me some
time ago which I could post if useful to anyone. For the above I can do:
#(markPad 1.5 #t) \mark "Bossa Nova" Note that the rest of the
Mats Bengtsson wrote:
I think this is the intended behaviour. If you want a fermata above
the text, you could use
d''^\markup{\center-align { \musicglyph #"scripts.ufermata" Text }}
Another possibility is to fiddle with the script-priority property,
see Sect. "Articulation", which also explains
cted EVENT_IDENTIFIER
{ \times 2/3 { a'4 b' c'' }
\glissando d''2 }
gliss.ly:1:0: error: errors found, ignoring music expression
{ \times 2/3 { a'4 b' c'' } \glissando d''2 }
error: failed files: "gliss.ly"
The workaround is to put th
T are the same as DOWN and UP, respectively.
I was hoping LEFT might help with the current default position bug.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Number #'direction = #1
d''
\override Score.BarNumber #'direction = #0
e''\fermata
\override Score.BarNumber #'direction = #-1
d''
a''
}
places bar numbers before the relevant bar.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
2.8.1 and 2.8.0 at least on Debian sid: The following results in the
fermata above the text even if I pad the text.
\version "2.8.0"
{ c''2 d''4\fermata^\markup{ Text } e''4\fermata }
Paul Scott
___
bug-li
Han-Wen Nienhuys wrote:
Werner LEMBERG wrote:
In light of this suprising you and the idea that relative means
relative to something I might suggest that there be no default and
that not specifying a starting point be an error.
Yep.
The following responses are not necessary to try to convince
Werner LEMBERG wrote:
I consider this unnatural. Additionally, it isn't documented in
section `Relative octaves' that the default startpitch is c' (and
not c).
Actually isn't middle C (c') as logical as anything as default.
What's special about the octave below middle C?
Conside
as logical as anything as default. What's
special about the octave below middle C?
What sense does \relative if one doesn't say what it's relative to?
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
In the latest development manual in section 10.4.2 "The markup command
|\slashSeparator| is provided as a sensible default, for example" is
followed by an example with no separator.
Paul Scott
___
bug-lilypond mailing list
bug-lilypo
Graham Percival wrote:
On 13-Mar-06, at 2:12 PM, Paul Scott wrote:
Erik Sandberg wrote:
On Monday 13 March 2006 21.39, Tuukka Verho wrote:
It compiles without problems with lilypond 2.6. Unless the syntax has
changed somehow (according to the documentation it doesn't seem to)
th
precede a header in the score block even thought I don't
know why. Even though the manual shows it this way maybe it should be
spelled out more clearly.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Han-Wen Nienhuys wrote:
Werner LEMBERG wrote:
I've just finished lilypond 2.7.38. This is likely to be the last
release candidate before we release 2.8, so report any bugs that you
might find.
Will 2.8 run on AMD K6 or K6-II?
Paul
In my use of 2.7.34 and 2.7.25 at least the bar number has moved just
enough to the left to be at the right of the previous bar. Section
8.2.4 of the latest manual actually shows one example as I describe and
the next example is correct.
Paul Scott
1 - 100 of 209 matches
Mail list logo
