Hi,
With lilypond 2.19.3, applying a music function to a bass figure
causes a syntax error. At least until 2.17.24 (I have not tested
later versions), that was not the case.
Example:
\version 2.19.3
%% Figured bass
%% change a flat or sharp alteration into natural
%% unless 'ancient-style
Le 6 avr. 2014 à 16:48, David Kastrup d...@gnu.org a écrit :
Nicolas Sceaux nicolas.sceaux.l...@gmail.com writes:
Hi,
With lilypond 2.19.3, applying a music function to a bass figure
causes a syntax error. At least until 2.17.24 (I have not tested
later versions), that was not the case
Hi,
When a page label is refered to inside some music, the corresponding page is not
found. The delayed evaluation happens before the label pages are collected.
Compare:
http://lilypond.org/doc/v2.17/input/regression/collated-files.html#page-label.ly
which reads A (page ?), with:
Le 26 sept. 2012 à 01:31, Mark Witmer a écrit :
I can't seem to get quotes/cues working in a score generated with ly:book-
process. This is my code:
% Quoted notes should appear in music created with ly:book-process,
% but they do not
\version 2.16.0
myPaper = \paper {}
myLayout =
Hi,
Using today's git LilyPond, the following snippet gives weird results:
the footnote is printed several times in header and footer, and on
several pages.
\version 2.15.32
\paper {
oddHeaderMarkup = \markup\null
evenHeaderMarkup = \markup\null
oddFooterMarkup = \markup\null
Le 3 mars 2012 à 15:53, James a écrit :
Nicolas,
On 2 March 2012 12:20, Nicolas Sceaux nicolas.sce...@free.fr wrote:
Hi,
Using today's git LilyPond, the following snippet gives weird results:
the footnote is printed several times in header and footer, and on
several pages
Hi,
Using today's git LilyPond, the following snippet gives weird results:
the footnote is printed several times in header and footer, and on
several pages.
\version 2.15.32
\paper {
oddHeaderMarkup = \markup\null
evenHeaderMarkup = \markup\null
oddFooterMarkup = \markup\null
Hi,
LilyPond from today's git.
ReahearsalMarks, with DOWN direction, are placed between the lower staff
and its figured bass, whereas one would expect the mark to appear below
the figured bass.
Example:
\version 2.15.24
\score {
\new Voice {
\clef bass d,1 g
\once \override
Le 1 janv. 2012 à 17:40, Neil Puttock a écrit :
The after-line-breaking callback for RehearsalMark
(ly:side-position-interface::move-to-extremal-staff) ignores axis
groups which have no horizontal extent (such as the VerticalAxisGroup
for the FiguredBass context).
I'm not sure whether
Le 7 juil. 2011 à 12:13, lilyp...@googlecode.com a écrit :
Comment #3 on issue 1747 by brownian.box: parallelmusic problem: q-notation
does not work in \relative
http://code.google.com/p/lilypond/issues/detail?id=1747
Probably, this is the issue of chord repetition in relative mode:
Le 27 mai 2011 à 15:15, Joe Neeman a écrit :
It turns out that BassFigureAlignment was paying attention to
alignment-distances... I'm testing a patch now.
Cool! thanks for the fix, Joe. It works.
Nicolas
___
bug-lilypond mailing list
:
De : Nicolas Sceaux nicolas.sce...@free.fr
Date : 7 mai 2011 17:55:23 HAEC
À : LilyPond User lilypond-u...@gnu.org
Objet : undesired figured bass stretching
Hi,
When forcing the staves spacing using
\overrideProperty #Score.NonMusicalPaperColumn
#'line-break-system-details
Hi Mike,
First of all, thank you very much for your precious work on footnotes.
The following example demonstrates a strange behavior wrt footnotes:
%% For each empty \fill-line in header and footer markups,
%% footnotes together with separation line are added.
\version 2.13.54
Le 6 juin 2010 à 00:59, Boris Shingarov a écrit :
Is it not the same issue as this one?
http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/18619
This bug has been poisoning my life since January -- I have had different
fixes in my repo, but hopefully that last patch is the Real Fix. We
Hi,
Page spacing algorithm seems to over estimate the height of markup lines.
Example:
===
\version 2.13.23
\header { tagline = ##f }
\paper {
annotate-spacing = ##t
#(define page-breaking ly:minimal-breaking)
}
#(set-default-paper-size a6 'portrait)
#(define-markup-list-command
Le 5 juin 2010 à 15:42, Xavier Scheuer a écrit :
2010/6/5 Nicolas Sceaux nicolas.sce...@gmail.com:
Hi,
Page spacing algorithm seems to over estimate the height of markup
lines.
With ly:minimal-breaking only?
No. Height estimation is orthogonal of the chosen page breaking algorithm
Le 12 févr. 2010 à 22:05, Neil Puttock a écrit :
On 12 February 2010 04:50, Boris Shingarov b...@shingarov.com wrote:
Of course, combine-score-stencils needs a real implementation, not just
(reverse stencils). But unfortunately, I do not understand what you mean by
space-lines. Could you
Le 6 janv. 2010 à 10:29, Bernard Hurley a écrit :
Hi,
Inside a bookpart only the last header block is seen. In the following
snippet, title and composer appear but _not_ poet.
Bernard
\header { title = Test }
\bookpart {
\header { poet = Someone }
\header { composer = Me }
{
Le 9 nov. 2009 à 19:43, Chris Snyder a écrit :
Nicolas Sceaux wrote:
Hi,
As was reported on http://code.google.com/p/lilypond/issues/detail?id=800
a regression was introduced by patch
7531ea6b3bb254f4d82aabde347a91671533b45a:
Fix lyric extenders to end properly when
Le 29 oct. 09 à 10:32, Valentin Villenave a écrit :
On Sun, Sep 13, 2009 at 6:30 PM, Nicolas Sceaux nicolas.sce...@free.fr
wrote:
%%% in the first page, text spread on the page footer (and beyond)
%%% before breaking to the next one.
Hi Nicolas,
it took me a while, but it's finally been
Le 2 oct. 09 à 14:02, Valentin Villenave a écrit :
On Wed, Sep 30, 2009 at 9:41 PM, Xavier Scheuer
x.sche...@gmail.com wrote:
%% Docs: A staff is considered empty when it contains only multi-
measure
%% rests, skips, spacer rests, or a combination of these elements.
%%
%% But because a
Hi,
It seems that the last example in NR 1.2.4 Beams: Setting automatic
beam behavior,
is broken. (I'm looking at lilypond.org 2.13.4 doc). This example
shows three bars
of 16th note, grouped by 4, despite the beam settings override on the
2nd bar.
Maybe the example should be changed to
Le 27 sept. 09 à 10:40, Nicolas Sceaux a écrit :
Perhaps it would be nice to show in this section how to override the
default
beaming settings globally, in a \layout block; stating that instead
of repeating
in each score a beam setting override like:
\overrideBeamSettings #'Score #'(4
Le 27 sept. 09 à 18:25, Carl Sorensen a écrit :
\time 4/4
\repeat unfold 8 a8
%% group 8th notes by 2
\overrideBeamSettings #'Score #'(4 . 4) #'end #'(((1 . 8) . (2 2 2
2)))
This is a feasible beamSettings override, but it's probably not
desirable.
The new autobeaming code requires
Hi,
[git from Sat Sep 12 21:00:03 2009]
%% In the following snippet, the Mark_engraver being in the Score
context,
%% the rehearsal mark shall be placed at the bottom of the system, not
at
%% the bottom of first staff.
\version 2.13.4
\new StaffGroup
\new Staff { g'1 g' }
\new Staff
%%% in the first page, text spread on the page footer (and beyond)
%%% before breaking to the next one.
\version 2.13.4
#(set-default-paper-size a6)
\markuplines \huge {
00 01 02 03 04 05 06 07 08 09
10 11 12 13 14 15 16 17 18 19
20 21 22 23 24 25 26 27 28 29
30 31 32 33 34 35 36 37 38 39
Le 25 juil. 09 à 11:39, Dénes Harmath a écrit :
On 2009.07.23., at 21:58, Mark Polesky wrote:
This suggests that the command is derived from hideNotes:
un + hideNotes = unHideNotes
That logic isn't applied in the case of \set and \unset. That's why
I am (and
maybe also others are) always
Le 15 juil. 09 à 16:22, Valentin Villenave a écrit :
2009/5/22 Nicolas Sceaux nicolas.sce...@free.fr:
In case of multiple vocal staves, __ extender lines in melisma may be
broken,
Master Nicolas Sceaux,
Your humble servant is deeply confused for unforgettably having let
Your bug report
Hi,
Extent estimate computation seems not to take account of not
displayed staves.
In the following example, the second system has
(-17.00, -0.19) Y-extent
(-41.30, -0.19) extent-estimate
\version 2.13.2
\paper { annotate-spacing = ##t }
\score {
\new StaffGroup
\new Staff { c'1
Hi,
%{
In case of multiple vocal staves, __ extender lines in melisma may be
broken,
as is shown in the following example:
%}
\version 2.13.1
staffA=\new Staff
\new Voice = A \with { autoBeaming = ##f } {
g'4. \melisma g'8 g'2 g' \melismaEnd g'
}
\lyricsto A \new Lyrics \lyricmode
Le 9 mai 09 à 20:32, Neil Tiffin a écrit :
I am using the following in a shell script to start lilypond
export LYEDITOR='bbedit +%(line)s %(file)s'
echo $LYEDITOR
cd '/Users/Shared/MainMusicFolder/lilypond files'
/Applications/LilyPond.app/Contents/Resources/bin/lilypond --verbose
-fpdf
[Joe, sorry for the duplicate mail]
Hi,
It seems that system extent estimation does not take into account
(de)crescendi, as is shown on the following example:
\version 2.12.2
\paper {
annotate-spacing = ##t
}
\new Staff { c'4\ c' c' c'\! \break c'4\ c' c' c'\! }
For both systems:
Y-extent =
Le 28 déc. 08 à 23:43, codesite-nore...@google.com a écrit :
Updates:
Cc: nicolas.sceaux
Comment #1 on issue 716 by hanwenn: --disable-optimisation causes
`Parsed object should be dead'
http://code.google.com/p/lilypond/issues/detail?id=716
this was introduced between .64 and .65,
Le 23 déc. 08 à 00:18, Mats Bengtsson a écrit :
Works well over here (Linux).
/Mats
Thank you all for testing it.
nicolas
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Le 18 déc. 08 à 21:02, Patrick McCarty a écrit :
Hello,
See the comments in the LY file below. The backtrace ends at the same
place as this one:
http://lists.gnu.org/archive/html/bug-lilypond/2008-12/msg00043.html
i.e. in get_column_description at simple-spacer.cc:345
Ahhh, thanks, I get
Le 17 déc. 08 à 12:25, Trevor Daniels a écrit :
Trevor Daniels wrote Tuesday, December 16, 2008 10:09 AM
Using \midi without \layout in 2.11.64-1 causes an exception in
Windows Vista:
Sorry, this should read 2.11.65-1
ah, I was wondering how that would happen in 2.11.64 :)
This bug has
Le 11 déc. 08 à 01:09, Dan Eble a écrit :
I am trying to use 2.11.65 on Mac OS X 10.5.5 on PowerPC G4.
This input causes a bus error. If I remove the midi, it does not.
\version 2.11.1
\score
{
\relative c' { c }
\midi { }
}
This one is fixed in git. Thanks for reporting it, and sorry
Le 10 déc. 08 à 05:48, Han-Wen Nienhuys a écrit :
Can you verify that valgrind does not complain of your code? You'll
need to silence GUILE GC related warnings.
Still not able to reproduce on GNU/Linux, I'm trying to run valgrind.
Do you have a valgrind suppression file for guile gc ready?
Le 11 déc. 08 à 06:42, Patrick McCarty a écrit :
On Thu, Dec 11, 2008 at 12:09:28AM +, Dan Eble wrote:
I am trying to use 2.11.65 on Mac OS X 10.5.5 on PowerPC G4.
This input causes a bus error. If I remove the midi, it does not.
\version 2.11.1
\score
{
\relative c' { c }
\midi { }
Le 10 déc. 08 à 05:48, Han-Wen Nienhuys a écrit :
Can you verify that valgrind does not complain of your code? You'll
need to silence GUILE GC related warnings.
I don't have Linux installed, valgrind seems linux only.
... I'm downloading a distro.
Le 9 déc. 08 à 19:01, Neil Puttock a écrit :
2008/12/9 John Mandereau [EMAIL PROTECTED]:
Here's what I get on a Fedora 9 x86_64 box with all recent updates,
compiling scores 1+...+5 (I get no segfault with 1+...+4, and I
also get
a segfault with all 8 scores enabled):
I get exactly the
Le 8 déc. 08 à 10:37, Graham Percival a écrit :
I've attached a very non-minimal example of a bus error crash with
\bookpart. Each \bookpart{} (8 violin duets) works perfectly when
compiled on their own, but combining them all together leads to
problems.
Graham, I cannot reproduce the bus
Le 7 mars 08 à 09:24, Thomas Scharkowski a écrit :
Windows XPSP2
This code produces the error message below:
--
\version 2.11.41
\header {
title = \markup \smallCaps {Peter´s Song}
subtitle = \markup {correct: Peter´s Song}
}
{c'1}
--
--
Processing
Hi,
The following snippet causes an error with LilyPond 2.11.36:
{
\stemUp r8
\override Voice.Stem #'details #'lengths = #'(3.0)
c'8 ~
\revert Voice.Stem #'details #'lengths
c'4
}
==
ERROR: In procedure ly:stem::pure-height:
ERROR: Wrong type (expecting real number): (beamed-lengths
Valentin Villenave [EMAIL PROTECTED] writes:
%{
Greetings,
The \smallCaps command, as described in the Manual (12.3.4),
uses a fixed \translate argument. Generally it's fine, but in some
cases it produces an ugly result.
%}
\markup \fill-line { \concat { Foo Foo bar }}
\markup
Nicolas Sceaux [EMAIL PROTECTED] writes:
Valentin Villenave [EMAIL PROTECTED] writes:
%{
Greetings,
The \smallCaps command, as described in the Manual (12.3.4),
uses a fixed \translate argument. Generally it's fine, but in some
cases it produces an ugly result.
%}
\markup \fill
Valentin Villenave [EMAIL PROTECTED] writes:
Hello everybody (well, Hello Graham, mostly :)
this discussion was never added to the tracker; however it is, if not
a major bug, a major annoyance when writing piano music (for example).
I'm refering to
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Joe Neeman escreveu:
On Saturday 01 September 2007 09:00, Trevor Bača wrote:
On 8/31/07, Joe Neeman [EMAIL PROTECTED] wrote:
On Friday 31 August 2007 23:17, Trevor Bača wrote:
Should I send the inputfile to either Joe or Han-Wen for testing
against
Hi,
Should volta brackets always be vertically aligned? Currently they are
not.
\version 2.11.27
\header { texidoc = Volta brackets shall be vertically aligned. }
\repeat volta 2 { c''1 } \alternative { c'''^\trill c'' }
___
bug-lilypond mailing list
Joe Neeman [EMAIL PROTECTED] writes:
On Sunday 08 July 2007 20:32, Nicolas Sceaux wrote:
Hi,
Should volta brackets always be vertically aligned? Currently they are
not.
It's funny you mention it: I just added support in the jneeman branch for
this
feature. Hopefully I will merge
Hi
Using lilypond from git HEAD, with the following snippet, volta brackets
are displayed above every staves:
\version 2.11.27
\new StaffGroup
\new Staff { \repeat volta 2 { g'1 g' g' } \alternative { g' g' } }
\new Staff { c'1 c' c' c' d' }
nicolas
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Nicolas Sceaux escreveu:
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
But I would be grateful for a short look at
http://code.google.com/p/lilypond/issues/detail?id=162
Ok, I'll look at it soon.
Hmm,
I think this introduces another problem
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Nicolas Sceaux escreveu:
Yes, but this introduces a new problem. Putting stuff into lily module
from a .ly file means that definitions from one .ly file will leak
into another, which is also a problem.
I don't understand: what leaks into what
Kevin [EMAIL PROTECTED] writes:
Invoking:
lilypond --pdf -o /tmp/output /tmp/someinput
results in the ps files, etc in /tmp, but the final output file ends
up in the current directory, not in/tmp like it seemingly should.
Using which version of LilyPond?
This look like a bug fixed ages
Erik Sandberg [EMAIL PROTECTED] writes:
On Saturday 23 September 2006 17:49, Nicolas Sceaux wrote:
Hi,
Using LilyPond from CVS, the following snippet causes a syntax error,
which 2.9.18 did not:
/**
testFunction =
#(define-music-function (parser location
Erik Sandberg [EMAIL PROTECTED] writes:
On Saturday 23 September 2006 17:49, Nicolas Sceaux wrote:
Hi,
Using LilyPond from CVS, the following snippet causes a syntax error,
which 2.9.18 did not:
I think the problem is my fix for music function arity: The extra tokens
inserted
Hi,
Using LilyPond from CVS, the required page break between 1st and 2nd
pieces does not show:
\version 2.9.19
\score {
{ c'1 }
\header { piece = First piece }
}
\score {
{ d'1 }
\header { piece = Second piece
breakbefore = ##t }
}
nicolas
Hi,
The following snippet makes lily to crash:
\score {
\new StaffGroup
\new Staff
{
\break
\overrideProperty #Score.NonMusicalPaperColumn
#'line-break-system-details
#'((alignment-extra-space . 20))
}
{ \clef french c''1 c''1 }
Hi,
Using LilyPond from CVS, the following snippet causes a syntax error,
which 2.9.18 did not:
/**
testFunction =
#(define-music-function (parser location) ()
;; test-data.ly contains music variable definitions
(ly:parser-parse-string parser \\include
Joe Neeman [EMAIL PROTECTED] writes:
On Tue, 2006-09-19 at 22:19 +0200, Nicolas Sceaux wrote:
Hi,
The following snippet causes lilypond to crash:
{
\pageBreak
c''1
\break
c''1
}
I think the correct behaviour is just to ignore breaks like this at the
start of the score, yes
Hi,
The following snippet causes lilypond to crash:
{
\pageBreak
c''1
\break
c''1
}
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x
0x000e4b10 in Page_breaking::break_into_pieces (this=0xbfffc528,
From: John Mandereau [mailto:[EMAIL PROTECTED]
That is not a bug: AFAIK '(score part) is not a list of symbols, it is a
constant list whose elements are the variables score and part.
No, it is a literal list which elements are symbols. That is, a symbol
list.
To be more on topic, \tag used
Fairchild [EMAIL PROTECTED] writes:
In v. 2.8.5 it seems \caps has been replaced with \smallCaps but both
are documented.
Or am I missing something?
\caps changes the font shape to caps, but if the font does not have such
a shape, this has no effect. \smallCaps is a work around: it changes
Trent Johnston [EMAIL PROTECTED] writes:
Hello everyone,
I'm having trouble with the alignment-vertical-manual-setting
I'm using the correct syntax below is an example
\overrideProperty
#Score.NonMusicalPaperColumn
#'line-break-system-details
#'((alignment-offsets . (55 44 33 22 11 5
Paul Scott [EMAIL PROTECTED] writes:
Nicolas Sceaux wrote:
Graham Percival [EMAIL PROTECTED] writes:
Could ragged-last-bottom be changed to affect all scores in a book?
Currently it only applies to the last one. (even better: could this
be alterable in separate scores?)
ragged
Graham Percival [EMAIL PROTECTED] writes:
Could ragged-last-bottom be changed to affect all scores in a book?
Currently it only applies to the last one. (even better: could this
be alterable in separate scores?)
ragged-last-bottom affects the last *page* of a book (be it made of a
single
Hello,
Since LilyPond 2.9.6, \overrideProperty is broken: see reg test
input/regression/page-spacing.ly
page-spacing.ly:27:8: warning: junking event: `ApplyOutputEvent'
\overrideProperty
An empty new staff is created each time \overrideProperty is used.
nicolas
Nicolas Sceaux [EMAIL PROTECTED] writes:
Hello,
Since LilyPond 2.9.6, \overrideProperty is broken: see reg test
input/regression/page-spacing.ly
page-spacing.ly:27:8: warning: junking event: `ApplyOutputEvent'
\overrideProperty
An empty new staff is created each time
Trent Johnston [EMAIL PROTECTED] writes:
This is what I get with running with verbose.
I think that has something to do with Nicolas's book-page-layout.ily. I took
this out and re-ran the file. Fine no problems. I finished inputting all the
lyrics and put the reference back to using
Rick Hansen (aka RickH) [EMAIL PROTECTED] writes:
Thanks,
Nobody in the USA uses Old Roman or even learns it in grade school. I think
the future releases should use New Roman as the default or switch to Arabic
for no confusion.
I have so many patches and work-araounds applied to my .scm
Rick Hansen (aka RickH) [EMAIL PROTECTED] writes:
I'm using 2.8.0
This is a minor bug, probably easy to fix...
For guitar fret board markup, the position marker
When the 4th fretting postion is called for, it prints instead of
iv, there is no such thing as roman numeral .
Hi,
The command 'mftrace --version' gives a different result with mftrace
1.2.0:
robert:~ nicolas$ ~/src/lilypond/mftrace-1.1.11/mftrace --version
mftrace 1.1.11
robert:~ nicolas$ ~/src/lilypond/mftrace-1.2.0/mftrace --version
mftrace 1.2.0
This program is free software. It is
Graham Percival [EMAIL PROTECTED] writes:
Toward the bottom of the section (p. 196 of the PDF), right above
See Also, it
says: The argument of the \tag command should be a symbol. I just
successfully
used \tag with \override commands, and I read symbol as referring
to something
that
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Nicolas Sceaux wrote:
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Mats Bengtsson wrote:
Looks like a bug! I forward it to bug-lilypond.
I fixed it on the Lily side, by adding 'caps shape to font.scm, but
you also have to have a Small-caps font
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Mats Bengtsson wrote:
Looks like a bug! I forward it to bug-lilypond.
I fixed it on the Lily side, by adding 'caps shape to font.scm, but
you also have to have a Small-caps font available to Pango.
Probably the best option is to remove the
Erik Sandberg [EMAIL PROTECTED] writes:
Hi,
The following code:
\version 2.7.36
\displayLilyMusic {
c \applyContext #(lambda (c) '()) d
}
gives the following error:
GNU LilyPond 2.7.36
Processing `foo.ly'
Jan Nieuwenhuizen [EMAIL PROTECTED] writes:
Herman Grootaers writes:
It seems that the file ./include/string.icc is broken just for this
release.
As I am not a programmer, I dont have a clue of what went wrong but
maybe the dev-team can come up with a quich fix of this problem.
The
When compiling LilyPond from current CVS, I get the following the
message on Mac OS 10.4.4. Maybe it's my OS's fault?
rm -f ./out/file-name.dep; DEPENDENCIES_OUTPUT=./out/file-name.dep
./out/file-name.o g++ -c -I/sw/lib/flex/include -DHAVE_CONFIG_H -DNDEBUG
-DSTRING_UTILS_INLINED -I./include
Gilles Quesne [EMAIL PROTECTED] writes:
Bonjour à toute l'équipe de Lilypond.
Retraité depuis peu de l'enseignement, j'enseignais les mathématiques au
collège,musicien amateur, flûte traversière, violon, je suis vivement
interessé
par votre éditeur de partition Lilypond.
Je travaille avec
Hi,
Just a reminder, as I have not found this bug reported in the bug
database: removing emtpy staves does not work properly, as removed
staves still take place.
nicolas
\version 2.7.23
\paper {
raggedright = ##t
}
\score {
\new StaffGroup
\new Staff {
\override
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
thanks. Fixed.
Nicolas Sceaux wrote:
Using LilyPond from CVS (2.7.26), \RemoveEmptyStaffContext does not seem
to work properly. See the example from
http://lilypond.org/doc/v2.7/Documentation/user/out-www/lilypond/Hiding-staves.html
The staves
Hi,
Using LilyPond from CVS (2.7.16), it seems that InnerStaffGroup brackets
are not translated to the left from the StaffGroup brackets, and thus
not really visible:
\version 2.7.16
\layout { raggedright = ##t }
\new StaffGroup
\new Staff { c' }
\new InnerStaffGroup
\new Staff { c' }
Using LilyPond from CVS (2.7.16), a strange artefact can be seen on
repeat bars, with PianoStaff:
\version 2.7.16
\layout { raggedright = ##t }
\new PianoStaff
\new Staff { c'1 \bar :|: \break c'1 }
\new Staff { c'1 c'1 }
___
bug-lilypond
Using LilyPond from CVS (2.7.26), \RemoveEmptyStaffContext does not seem
to work properly. See the example from
http://lilypond.org/doc/v2.7/Documentation/user/out-www/lilypond/Hiding-staves.html
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
fixed. Thanks!
How quick. Thank you.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Nicolas Sceaux wrote:
Using LilyPond from CVS, I cannot get score-level titles to be
displayed. Is it just me?
LilyPond CVS is in brain-surgery mode. Be thankful that you anything
sensible at all :-)
Yes, the last announce is impressive!
I've
Erik Sandberg [EMAIL PROTECTED] writes:
To me, those property lists look like major bottlenecks (though I
haven't done any real profiling). Especially the grob property alists:
While I was debugging some time ago, I saw that
Grob::internal_set_property was called over 1000 times in a trivial
While tweaking vertical space in a score, I faced the following problem:
\version 2.7.12
\paper {
raggedlastbottom = ##t
annotatespacing = ##t
betweensystemspace = 1.0
}
\new Staff
{
\overrideProperty
#Score.NonMusicalPaperColumn
#'line-break-system-details
Sven Axelsson [EMAIL PROTECTED] writes:
The InnerStaffGroup and InnerChoirStaff produces exactly the same
result.
You can define custom staff groups:
\version 2.7.12
\layout {
\context {
\Score
\accepts OrchestraStaffGroup
}
\context {
\StaffGroup
\name
Wiz Aus [EMAIL PROTECTED] writes:
lilypond uses an interpretive language (Scheme)
No. LilyPond uses an *implementation* of Scheme, namely guile, which
only provides an interpreter, but no compiler, unlike many other Scheme
implementations. Please do not widespread wrong clichés.
nicolas
Wiz Aus [EMAIL PROTECTED] writes:
From: Nicolas Sceaux [EMAIL PROTECTED]
Wiz Aus [EMAIL PROTECTED] writes:
lilypond uses an interpretive language (Scheme)
No. LilyPond uses an *implementation* of Scheme, namely guile, which
only provides an interpreter, but no compiler, unlike many other
Hi,
With the following snippet, using LilyPond from CVS, I get all the
staves in reversed order, ie Bassi in the top of the system and Corno in
the bottom.
nicolas
\version 2.7.8
theNotes = {
r2 r4 b |
d'2 fis' |
g'4 d' c' g' |
fis'2 fis'4 a' |
d'2 fis' |
g'4 fis'8[ e'] d'4 c' |
}
Hi,
I'm not sure if that's a bug or if I'm just doing something badly. In
the following snippet, the lyrics are not placed below the newly added
staff.
\version 2.7.5
\layout { raggedright = ##t }
\context Staff = low { c'1 \break c'1 }
{
\skip 1 \new Staff
\set Staff .
Using LilyPond from CVS.
In the following example, the two pieces get wrong titling:
piece 1 opus 2
===
piece 1 opus 2
===
instead of:
piece 1 opus 1
===
opus 2
===
If
Graham Percival [EMAIL PROTECTED] writes:
On 12-Aug-05, at 3:03 AM, Nicolas Sceaux wrote:
Using LilyPond from CVS.
In the following example, the two pieces get wrong titling:
There's a header patch that's waiting for Han-Wen to look at it. I
don't
know if it fixes this, but you could try
Peter Teeson [EMAIL PROTECTED] writes:
In file .../stepmake/stepmake/compile-vars.make
SHARED_FLAGS = -shared
is replaced by
SHARED_FLAGS = -bundle -flat_namespace -undefined suppress
Whether the other patches are required time will tell.
But at least this allowed me to run make.
You can
Ronán Conroy [EMAIL PROTECTED] writes:
Congratulations on Lilypond! I've just started with 2.6.0 on OS X, and
am now the proud possessor of some music for my young son, who is just
starting piano and wants to play Star Wars themes!
Two suggestions
1. Autosave on typeset
The editor should
Peter Teeson [EMAIL PROTECTED] writes:
So is there an XCode 1.5 project available for downloading?
Doesn't make sense to do it all over again if there is already one
available.
Han-Wen is using Emacs, not XCode, so I guess the answer is no.
___
Mats Bengtsson [EMAIL PROTECTED] writes:
Both problems pointed out in this thread show a limitation in
the handling of volta brackets. A volta bracket is only printed
over contexts where the property voltaOnThisStaff is set to true.
At the beginning of a score, this property is automatically
Selon Erik Sandberg [EMAIL PROTECTED]:
On Saturday 19 February 2005 16.24, Nicolas Sceaux wrote:
Lily used to move markups so that they do not collide with music. This
example is from Lily 2.5.2:
http://nicolas.sceaux.free.fr/lilypond/markup-offset-2.5.2.png
With current LilyPond
1 - 100 of 104 matches
Mail list logo
