: Saturday, January 12, 2013 10:50 AM
Subject: Re: Book title showing up on every score in a songbook (2.14.2)
Le 12 janv. 2013 à 11:10, Christopher R. Maden cr...@maden.org a écrit :
I expect \bookpart{} to start a new page; and
if the bookpart has a title or any other header info, I expect
Trevor Daniels writes:
@bug squad
Could you please raise an issue to enhance the documentation to include
the information in Nicolas's reply below. Thanks.
Trevor
Sure, see new tracker here:
http://code.google.com/p/lilypond/issues/detail?id=3103
Feel free to change the title of the
Trevor Daniels wrote
Le 12 janv. 2013 à 11:10, Christopher R. Maden lt;
crism@
gt; a écrit :
I expect \bookpart{} to start a new page; and
if the bookpart has a title or any other header info, I expect that to
be printed at the top of that new page.
Indeed, \bookpart starts a new
Eluze suggested:
what about using a simple \pageBreak after the book's header?
\book {
\header {title = …}
\pageBreak
\bookpart {
I feel this is clearer than relying on the following construct (from NR):
Use the breakbefore variable inside a \header block that is itself in a
Trevor Daniels wrote
I've added this suggestion to the tracker.
and maybe a note about when header items are displayed could clear a few of
the misunderstandings, e.g.
header items like /title, subtitle,composer/, …, /piece/ and /opus/ are only
displayed if a corresponding page or score is
Regarding
http://lilypond.org/doc/v2.16/Documentation/learning/command_002dline
1) The example there says \version 2.14.2.
I don't doubt that it works in 2.14.2 (I certainly hope so :). But it
presumably also works in many earlier versions. So it would seem more
logical either to have the first
Karl Berry wrote Friday, September 07, 2012 11:45 PM
Regarding
http://lilypond.org/doc/v2.16/Documentation/learning/command_002dline
1) The example there says \version 2.14.2.
2) The output in Step 2 starts with GNU LilyPond 2.14.2. Ok, granted
Thanks. These have already been reported
David Monniaux david.monni...@free.fr writes:
lilypond 2.14.2 crashes randomly (once it may run successfully, the next
time it may crash, etc.) on the following file. The error message is:
Preprocessing graphical objects...throw from within critical section.
Aborted
What compiler did you
David Monniaux david.monni...@free.fr writes:
On 08/02/2012 06:00 PM, bug-lilypond-requ...@gnu.org wrote:
How did you install LilyPond? Did you install a precompiled binary from
lilypond.org, a package from your distribution, or did you compile
yourself?
Self-compiled with gcc version 4.6.1
On Sat, Aug 4, 2012 at 1:17 PM, David Monniaux david.monni...@free.fr wrote:
On 08/02/2012 06:00 PM, bug-lilypond-requ...@gnu.org wrote:
How did you install LilyPond? Did you install a precompiled binary from
lilypond.org, a package from your distribution, or did you compile
yourself?
David Monniaux David.Monniaux at free.fr writes:
On 08/02/2012 06:00 PM, bug-lilypond-request at gnu.org wrote:
How did you install LilyPond?
Self-compiled with gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
Which GNU/Linux
distribution release do you use exactly?
x86
Ubuntu 11.10
Il giorno mar, 07/08/2012 alle 22.40 +, Colin Hall ha scritto:
Thanks for letting us know about this David.
One of the developers may be able to make some suggestions.
I'm not going to create an issue tracker for this. I'm very
sorry but we only accept bug reports for official builds
On 08/02/2012 06:00 PM, bug-lilypond-requ...@gnu.org wrote:
How did you install LilyPond? Did you install a precompiled binary from
lilypond.org, a package from your distribution, or did you compile
yourself?
Self-compiled with gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
Of even more
Il giorno dom, 29/07/2012 alle 22.23 +0200, David Monniaux ha scritto:
lilypond 2.14.2 crashes randomly (once it may run successfully, the next
time it may crash, etc.) on the following file. The error message is:
How did you install LilyPond? Did you install a precompiled binary from
lilypond 2.14.2 crashes randomly (once it may run successfully, the next
time it may crash, etc.) on the following file. The error message is:
Preprocessing graphical objects...throw from within critical section.
Aborted
Since the message talks of critical section, which usually alludes
} }
Is there a new option which I dit not realize?
Well, as a workaround I can apply a variant of \chordRepeats to get the
benefit back I had when editing using 2.14.2:
-#(define-public (expand-repeat-chords! event-types music)
+#(define-public (expand-repeat-chords-loc! event-types music)
Walks
On Mon, Jul 16, 2012 at 01:53:51AM -0700, ArnoldTheresius wrote:
The pointAndClick location of chord repeats is now pointing to the orignial
chords.
Is 2.14.x it was pointing to your 'q' entry in the input file.
Especially with a lot of rhythmic repeats the old pointAndClick is much more
In 2.14.2, the output for the second bar beams all five eighth notes
together, as I would expect. In 2.15.39, the first eighth note is not
beamed with the others:
\relative c'' {
\time 3/4
c8 c c c c c
r c c c c c
}
attachment: 2.15.39.pngattachment: 2.14.2
On Thu, May 24, 2012 at 05:13:55PM +1000, Nick Payne wrote:
In 2.14.2, the output for the second bar beams all five eighth notes
together, as I would expect. In 2.15.39, the first eighth note is not
beamed with the others:
\relative c'' {
\time 3/4
c8 c c c c c
r c c c c c
On Thu, May 24, 2012 at 05:13:55PM +1000, Nick Payne wrote:
In 2.14.2, the output for the second bar beams all five eighth notes
together, as I would expect. In 2.15.39, the first eighth note is
not beamed with the others:
\relative c'' {
\time 3/4
c8 c c c c c
r c c c c c
I'm not top posting.
\version 2.14.2-1
% Changing the stacking-dir for BassFigureAlignment seems
% to be broken when adding the figures to the staff rather
% than creating a separate FiguredBass staff.
% Here it works fine...
\new FiguredBass {
\figuremode {
\override BassFigureAlignment
2012/5/9 TorbjörnBjörkman torbjo...@gmail.com:
I'm not top posting.
\version 2.14.2-1
% Changing the stacking-dir for BassFigureAlignment seems
% to be broken when adding the figures to the staff rather
% than creating a separate FiguredBass staff.
% Here it works fine...
\new
2012/5/9 Torbjörn Björkman torbjo...@gmail.com:
Thanks a heap! You just saved me the trouble to write a script that swaps
the order of the bass figures in my whole library (which is a lot...)
Cheers,
Torbjörn
Glad I could help.
Please don't fotget to cc the list.
-Harm
On Wed, May 09, 2012 at 10:30:57PM +0200, Thomas Morley wrote:
2012/5/9 Torbjörn Björkman torbjo...@gmail.com:
Thanks a heap! You just saved me the trouble to write a script that swaps
the order of the bass figures in my whole library (which is a lot...)
Cheers,
Torbjörn
Glad I
2012/5/9 Colin Hall colingh...@gmail.com:
Can I add my thanks too, Thomas? This sort of support from the more
experienced members of the team is very helpful indeed.
Cheers,
Colin.
--
Colin Hall
You're welcome.
-Harm
___
bug-lilypond mailing
Comment #8 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
The trunk (2.15.x) was fixed long ago. The problem only exists in 2.14.x
and the fix would be to apply my patch to the stable
Comment #9 on issue 2030 by d...@gnu.org: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
If we chose to do 2.14.3, the fix for Issue 1997 would likely have to go in
as well, or we would be hearing from
Comment #10 on issue 2030 by gra...@percival-music.ca: 2.14.2, dynamic cast
crash introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
Yes, anything is reasonable and simple when it's somebody else doing the
work.
I am not certain that GUB can still build
Updates:
Status: Verified
Comment #7 on issue 2030 by colingh...@gmail.com: 2.14.2, dynamic cast
crash introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
To verify this I used the sample code submitted by plroskin in Comment #2
\version 2.14.2
Comment #6 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
This ticket is misnamed. The crash is not in dynamic_cast. It was in
dynamic_cast because I miscompiled lilypond. Once I
Comment #4 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
The fix is to backport 9ff88d12 from master. The patch is attached.
Considering that it's a crash in the latest stable release
Updates:
Status: Fixed
Labels: fixed_2_15_9 backport
Comment #5 on issue 2030 by k-ohara5...@oco.net: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
Let's point this to issue 1800, then, and mark the fixed
Comment #3 on issue 2030 by gra...@percival-music.ca: 2.14.2, dynamic cast
crash introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
hmm, interesting. BTW, make clean is not reliable either. In my mind,
the only reliable thing is:
- completely remove
Comment #2 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
The bug as it's entered is bogus. It turns out lilypond has an issue with
the build system. The incremental make
Comment #1 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
I can reproduce the issue on a Fedora 16 system, but not on a Fedora 15
system. On the later, I get:
GNU LilyPond 2.14.2
Hello,
On Mon, Nov 7, 2011 at 11:27 PM, Pavel Roskin pro...@gnu.org wrote:
Hello!
Lilypond 2.14.2 and the current revision from stable/2.14 crash on this
file:
Added as http://code.google.com/p/lilypond/issues/detail?id=2030
--
--
James
Status: Accepted
Owner:
Labels: Type-Crash
New issue 2030 by pkx1...@gmail.com: 2.14.2, dynamic cast crash introduced
in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
Hello!
Lilypond 2.14.2 and the current revision from stable/2.14 crash on this
file
Hello!
Lilypond 2.14.2 and the current revision from stable/2.14 crash on this
file:
\version 2.14.2
\score {
\new PianoStaff
\new Staff = right { \change Staff=left }
\new Staff = left { s1 }
\layout { }
}
Bisection finds that the regression was introduced on the stable branch
Status: Accepted
Owner:
Labels: Type-Scripts OpSys-FreeBSD
New issue 2009 by pkx1...@gmail.com: Lilypond shell script instaler for
2.14.2-1 install fails on FreeBSD 8.2 virgin system
http://code.google.com/p/lilypond/issues/detail?id=2009
Mike Andrews mi...@mikea.ath.cx via gnu.org
Nov
Colin Campbell cpkc at shaw.ca writes:
definitions.ly:16:50: error: GUILE signaled an error for the expression
beginning here
\override VerticalAlignment #'max-stretch = #
ly:align-interface::calc-max-stretch
Would you post a short snippet which produces this, please?
It was in
Processing `score.ly'
Parsing...
definitions.ly:16:50: error: GUILE signaled an error for the expression
beginning here
\override VerticalAlignment #'max-stretch = #
ly:align-interface::calc-max-stretch
Unbound variable:
On 11-10-28 12:46 PM, Thomas Spuhler wrote:
Processing `score.ly'
Parsing...
definitions.ly:16:50: error: GUILE signaled an error for the expression
beginning here
\override VerticalAlignment #'max-stretch = #
ly:align-interface::calc-max-stretch
Unbound variable:
Hi,
LilyPond 2.14.2 logs warnings when presented with simultaneous slurs.
$ cat partcombine.ly
\version 2.14.2
\partcombine { g'( a') } { e'( f') }
$ lilypond partcombine.ly
GNU LilyPond 2.14.2
Processing `partcombine.ly'
[...]
partcombine.ly:2:17: warning: already
On 11-09-13 03:30 PM, Jean-Baptiste Mazon wrote:
Hi,
LilyPond 2.14.2 logs warnings when presented with simultaneous slurs.
$ cat partcombine.ly
\version 2.14.2
\partcombine { g'( a') } { e'( f') }
$ lilypond partcombine.ly
GNU LilyPond 2.14.2
Processing
2011/8/3 Frédéric Bron frederic.b...@m4x.org:
In the following code, no word is placed below the second eight note.
Commenting \cadenzaOn or removing manual beaming [] works fine.
Manual beaming [ ] behaves like slur ( ).
This worked in previous versions.
This is normal behaviour.
\cadenzaOn
This is normal behaviour.
\cadenzaOn contains \set Timing.autoBeaming = ##f (which was maybe not
the case in 2.12).
Yes, I have seen this in the Changes.
Manual beaming [ ] behaves like slur ( ) because of the melisma rules
(which are based on common engraving practices), see NR 2.1.1
In the following code, no word is placed below the second eight note.
Commenting \cadenzaOn or removing manual beaming [] works fine.
Manual beaming [ ] behaves like slur ( ).
This worked in previous versions.
\version 2.14.0
\score {
\context Voice = notes \relative {
From: ehzone ehz...@gmail.com Sunday, July 31, 2011 6:48 AM
The section has 2 examples meant to show how to place lyrics
between
the staves of a piano staff. The image accompanying the first
example
isn't correct; the lyrics should appear under the bass clef and
not
between the treble and
Trevor Daniels t.dani...@treda.co.uk wrote in message
news:62EC5FA4701E4CA3BB7653F5392A1AD4@TrevorLaptop...
From: ehzone ehz...@gmail.com Sunday, July 31, 2011 6:48 AM
The section has 2 examples meant to show how to place lyrics between
the staves of a piano staff. The image accompanying
The section has 2 examples meant to show how to place lyrics between
the staves of a piano staff. The image accompanying the first example
isn't correct; the lyrics should appear under the bass clef and not
between the treble and bass.
my $0.02 worth. I hope this helps.
regards,
eh.
!
I think I have to apologize that I faded out of my Bug Squad duty
silently half a year ago.
Apology accepted.
This as a general remark, now to my current question:
When do you expect 2.14.2 to be released?
I think it's ready when Graham gets to it. I expect it soon.
ATM there are many
have the time.
I think any extra minute spent by someone like me is useful, even if I
can't promise any continuity.
This as a general remark, now to my current question:
When do you expect 2.14.2 to be released?
ATM there are many issues to verify that are marked as fixed_2_14_2. So
before
remark, now to my current question:
When do you expect 2.14.2 to be released?
I think it's ready when Graham gets to it. I expect it soon.
ATM there are many issues to verify that are marked as fixed_2_14_2. So
before this version is released the issues can't be verified.
I think
.
Apology accepted.
This as a general remark, now to my current question:
When do you expect 2.14.2 to be released?
I think it's ready when Graham gets to it. I expect it soon.
ATM there are many issues to verify that are marked as fixed_2_14_2. So
before this version is released the issues
On Thu, Jul 14, 2011 at 06:53:45AM -0600, Carl Sorensen wrote:
On 7/14/11 6:23 AM, Urs Liska lilyli...@googlemail.com wrote:
ATM there are many issues to verify that are marked as fixed_2_14_2. So
before this version is released the issues can't be verified.
I think that in the past we
Am 14.07.2011 16:18, schrieb Graham Percival:
On Thu, Jul 14, 2011 at 06:53:45AM -0600, Carl Sorensen wrote:
On 7/14/11 6:23 AM, Urs Liskalilyli...@googlemail.com wrote:
ATM there are many issues to verify that are marked as fixed_2_14_2. So
before this version is released the issues can't
which
doesn't matter. The first 2.16 release candidate will be out in
2.5 weeks (if there's 0 critical issues).
It will probably take 1-2 weeks to fix those issues, unless we
make a stable release with known Critical Issues, we're looking
at releasing 2.14.2 approximately 7 days before the first 2.16
exactly that
(waiting for 2.14.2) :-)
(Particularly, today is my day, and I've already verified all issues which
were -- as for me -- ready for verifying).
Thank you for your effort, anyway!-)
ps. We will have some GOP discussion regarding issues, won't we?
So, I think, we should save some energy
=On 6/28/11 12:30 PM, Federico Bruni fedel...@gmail.com wrote:
Il giorno lun, 27/06/2011 alle 13.13 -0600, Carl Sorensen ha scritto:
I'm trying to get ready for release 2.14.2. In general, I'd like
bugfixes
from 2.15.x to show up in 2.14.2.
Carl,
when v2.14.2 will be released? (more
59 matches
Mail list logo
