Sorry, forgot to reply all
On 19 Sep 2014 12:13, Neil Puttock n.putt...@gmail.com wrote:
On 19 Sep 2014 11:52, Jakob Schöttl jscho...@gmail.com wrote:
The documentation of TextSpanner.bound-details
http://lilypond.org/doc/v2.18/Documentation/internals/textspanner
seems to miss
On 23 January 2012 12:06, James pkx1...@gmail.com wrote:
Yes that is what I have but the first bar seems to have nothing to do
with anything - at least as far as I can see.
It looks like the first bar's shortest-duration-space carries over
into the first beat of the second, messing up the
On 16 January 2012 21:04, -Eluze elu...@gmail.com wrote:
Ralph Palmer-3 wrote:
On Sun, Jan 15, 2012 at 10:29 AM, -Eluze elu...@gmail.com wrote:
Is -dverbose a legitimate option? I would have thought the form would be
-d
--verbose. When I try that (lilypond -d --verbose FILENAME), I get
On 11 January 2012 21:03, Robin Bannister r...@dataway.ch wrote:
It is still incorrect despite the update reported today on lilypond-user.
http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00196.html
It's correct now.
Cheers,
Neil
___
On 9 January 2012 11:55, Thomas Morley thomasmorle...@googlemail.com wrote:
With 2.14.2 and 2.15.2 the BreathingSign isn't positioned correct,
while using changed staff-size or (default) TabStaff.
2.12.3-behaviour was accurate.
%\version 2.12.3
\version 2.14.2
%\version 2.15.20
mel = {
On 9 January 2012 12:27, Neil Puttock n.putt...@gmail.com wrote:
Hmm, I guess this is my fault. We had a bug with Y-offset positioning
when using custom staves, so I revised the offset-callback.
Will try to check it out later.
Oops, really bad thinko in Breathing_sign::offset_callback
On 9 January 2012 12:35, m...@apollinemike.com m...@apollinemike.com wrote:
Will do.
Thanks mate.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 1 January 2012 14:08, Phil Holmes m...@philholmes.net wrote:
OK - I'm just about to try a snippet import. I'll fix that as part of the
import.
Beethoven spells it `ligato', and every edition of the Waldstein I've
seen respects that.
Cheers,
Neil
On 1 January 2012 14:47, Phil Holmes m...@philholmes.net wrote:
If the headword explained this, it would be fine, but it doesn't and
therefore makes it look wrong. We don't use other archaic words unless
there's a clear reason?
It's a real music example (of a particularly famous piece), so
On 1 January 2012 16:08, Xavier Scheuer x.sche...@gmail.com wrote:
On 1 January 2012 16:19, Nicolas Sceaux nicolas.sce...@gmail.com wrote:
Hi,
LilyPond from today's git.
ReahearsalMarks, with DOWN direction, are placed between the lower staff
and its figured bass, whereas one would expect
On 25 Dec 2011 22:27, Thomas Morley thomasmorle...@googlemail.com wrote:
1. IR 3.2.109 stem-interface states: flag (graphical (layout) object)
A pointer to a Flag object.
I would have expected: () (there is no flag!)
The unused flag is suicided. A pointer to the suicided grob still
On 25 Dec 2011 23:01, Thomas Morley thomasmorle...@googlemail.com wrote:
I think there could be some difficulties to find the correct
condition, when I create my own definitions/functions:
\version 2.15.20
displayGrob =
\once\override Stem #'after-line-breaking =
#(lambda
On 21 October 2011 15:48, pls p.l.schm...@gmx.de wrote:
the command \eyeglasses is neither part of the command index nor of the
general index.
It's documented automatically as a slashed command in both indices:
http://lilypond.org/doc/v2.15/Documentation/notation/other#index-_005ceyeglasses
On 21 October 2011 16:24, pls p.l.schm...@gmx.de wrote:
It's not that it isn't documented. I found it eventually but it's neither
included here
http://lilypond.org/doc/v2.15/Documentation/notation/lilypond-command-index#lilypond-command-index_ky_letter-E
nor here
On 21 October 2011 16:51, David Kastrup d...@gnu.org wrote:
Wouldn't it make more sense to have the index entries escaped, but
sorted under the respective first letter instead of \ ?
Sounds eminently sensible to me. :)
Cheers,
Neil
___
bug-lilypond
On 20 October 2011 11:23, Nick Payne nick.pa...@internode.on.net wrote:
I don't get this error with any of the other scores I have built with
2.15.14, and this score built without error on 2.14 and hasn't been modified
since except by running convert-ly against it.
Can you recompile the code
On 17 Oct 2011 07:56, Peekay Ex pkx1...@gmail.com wrote:
However, and this is for Phil: could we not simply 'deprecate' the
snippet(s) like we do with any that won't work (properly) in later
versions, and actually I think it was Mike that a week or so ago
pointed one out to me that was
On 17 October 2011 11:41, Graham Percival gra...@percival-music.ca wrote:
On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
On 17 Oct 2011 07:56, Peekay Ex pkx1...@gmail.com wrote:
However, and this is for Phil: could we not simply 'deprecate' the
snippet(s) like we do with any
On 19 September 2011 13:05, m...@apollinemike.com m...@apollinemike.com wrote:
Perhaps create two new make options:
make unsafe-test-baseline
and
make unsafe-check
These would not have the fail-if-unoptimized check.
Then, one would need to make a change to GUB such that, when it runs
On 19 September 2011 15:10, m...@apollinemike.com m...@apollinemike.com wrote:
Also, it may be worth it to consider scrapping optimized binary altogether -
it'd be good to test how much overhead the unoptimized version introduces
with respect to the optimized version.
Eek, you don't want to
On 19 September 2011 16:16, David Kastrup d...@gnu.org wrote:
The debug symbols should not affect code speed, and they are present in
the unoptimized build, anyway, unless you are talking about something
completely different from what I think you do. I find it disturbing,
however, that our
On 17 September 2011 19:35, Reinhold Kainhofer reinh...@kainhofer.com wrote:
The attached minimal example (taken from an LSR snippet) cause the volta
engraver to print a warning, although the file is perfectly fine and should
work without a warning:
Issue 1476.
Cheers,
Neil
On 17 September 2011 19:45, Reinhold Kainhofer reinh...@kainhofer.com wrote:
The attached minimal testcase (stripped down from an example in our docs)
prints a type-check warning for a nested property:
This has popped up several times. Keith added a clarification to the
NR for it back in
On 1 September 2011 13:06, Valentin Villenave valen...@villenave.net wrote:
Dear all,
let's make it official: I am going insane.
Not yet. ;)
Unless *anyone* can explain what's going on therebelow, that is.
I think this is to do with the way barlines are treated by the
engraver. We have a
2011/8/4 Xavier Scheuer x.sche...@gmail.com:
That has been registered as issue #1774, isn't it?
http://code.google.com/p/lilypond/issues/detail?id=1774
Not quite. Gould makes an exception for semibreves with adjacent
notes; in this case, they should be aligned as if they had stems:
\version
2011/7/24 Janek Warchoł lemniskata.bernoull...@gmail.com:
Hmm, does this work or is this just a proof-of-concept? I wasn't able
to determine it after reading
http://www.gnu.org/software/guile/manual/html_node/Exactness.html
I suppose it might break if users try to make pitches with really
On 26 July 2011 21:33, Graham Percival gra...@percival-music.ca wrote:
I think this is the best solution as well. It might be nice to
add a bit more documentation about how somebody who really
disliked the new font could go about replacing it, but we've never
viewed documentation as holding
2011/7/24 Janek Warchoł lemniskata.bernoull...@gmail.com:
Oops, sorry for the late answer!
2011/7/18 Mario Moles mario-mo...@libero.it
even if I correct the syntax (without = c, = d, = f) the error remains.
I'm surprised too.
I've discovered that when you use words for alteration (i.e.
On 20 July 2011 15:26, Neil Puttock n.putt...@gmail.com wrote:
Let me think about it for a bit. I have an idea using a scheme
engraver which might work.
Here's the scheme engraver if you want to try it out. It's obviously
not as sophisticated as Mike's proposed fix, but it does have
On 19 June 2011 16:36, Reinhold Kainhofer reinh...@kainhofer.com wrote:
Is there any current way to switch on/off expansion of the repeats in both
scores for the midi output, other than manually prepending \unfoldRepeats in
BOTH scores?
I had a look at this when issue #769 was created. There
2011/7/21 m...@apollinemike.com m...@apollinemike.com:
\new Voice
\with { \remove Rest_engraver \consists Completion_rest_engraver }
{ r1*6/4 r2 }
This gets me the attached output.
The Completion_heads_engraver has the same problem:
% bad
\new Voice
\with { \remove Note_heads_engraver
On 20 July 2011 13:27, Xavier Scheuer x.sche...@gmail.com wrote:
I was wondering if you (or someone else) would have maybe a workaround
I could use in order to have a fairly good output for the code attached
to #1724 ?
http://code.google.com/p/lilypond/issues/detail?id=1724
Let me think
On 14 July 2011 22:25, -Eluze elu...@gmail.com wrote:
there is another question (may be i should start a new post for that?):
{ b - \tweak #'direction #-1 -5 }
does not have any effect: the fingering is still above the note?! what am i
missing?
It works like this:
1)
On 12 July 2011 21:08, BognárBálint bobq...@inf.elte.hu wrote:
When autoBeam is off and I manually place a beam on two different 1/8 notes
(eg. a 'c' and a 'd'), only one syllable of lyrics is positioned under these
two notes (eg. if the lyrics is ly -- rics (or ly rics), ly is
positioned
2011/7/12 Janek Warchoł lemniskata.bernoull...@gmail.com:
I don't see this reported yet, so i add it to the tracker as issue
1759 http://code.google.com/p/lilypond/issues/detail?id=1759
It was posted as issue 1738 which got merged as a duplicate
(ulitmately of issue 620).
Cheers,
Neil
On 7 July 2011 06:54, Dmytro O. Redchuk brownian@gmail.com wrote:
NR says:
% -8--
This function is called as follows:
\new Staff
#(set-accidental-style 'voice)
{ … }
The accidental style applies to the current Staff by default
On 4 July 2011 14:17, Dmytro O. Redchuk brownian@gmail.com wrote:
I've not tested! I have no any windows (with lilypond and ImageMagick) about.
You don't need ImageMagick. The eps backend will produce a trimmed
png (assuming the tagline's been removed):
echo \\header { tagline = ##f } |
On 4 July 2011 15:16, Neil Puttock n.putt...@gmail.com wrote:
Ah, I didn't notice that (though it only applies to single-system
snippets where you'd usually use -dpreview).
Silly me. Of course, with ragged-right = ##t the same applies to
multi-system snippets. :)
Cheers,
Neil
On 14 June 2011 17:35, Friedrich Fischer fried.fisc...@gmail.com wrote:
Mr. Carl Sorensen wrote to me:
This may be a bug. If I had to guess, I'd say that the bug should read
something like \voiceX outside of \relative mode doesn't apply within
\relative block
Can you make a tiny example and
On 9 June 2011 15:37, Mark Polesky markpole...@yahoo.com wrote:
using GNOME on 64-bit Ubuntu 9.10 (Karmic Koala)
Both pdf viewers on my machine give the same output:
* Document Viewer 2.28.1 (evince)
* Okular Version 0.9.2
$ uname -a
Linux localhost 2.6.31-23-generic #75-Ubuntu SMP Fri
On 29 April 2011 12:49, Helge Hafting helge.haft...@hist.no wrote:
The Tie_engraver is already capable of not tieing all notes in a chord, so I
hope this is fixable.
The Tie_engraver isn't designed to work at the Staff level, so there's
no guarantee you'll get workable results. There is
On 17 April 2011 22:46, Xavier Scheuer x.sche...@gmail.com wrote:
Basically if a user could give me a clue how to disable the fact that
when a note is far from the staff, its stem goes to the middle line of
the staff, I would be grateful. :)
\override Stem #'no-stem-extend = ##t
Cheers,
On 14 March 2011 11:23, James Lowe james.l...@datacore.com wrote:
if you can suggest something for the documentation - I don't think this is a
bug but may catch some users out - so it could be an @knownissue
candidate/snippet etc.?
Definitely a bug. The Tie_engraver acknowledges objects
On 10 March 2011 17:26, Trevor Daniels t.dani...@treda.co.uk wrote:
I seem to remember this being pointed out by Valentin
a year or more ago. The line appears for 'staff-space
settings greater than some number around 1.22. I don't
recall ever seeing an explanation for it.
It due to the
On 9 March 2011 16:02, Laura Conrad lcon...@laymusic.org wrote:
Unfortunately, it creates a new one. In some cases, such as the
attached small example, when I use this BarType I get a lot of errors:
programming error: Loose column does not have right side to attach to.
I was hoping these
On 8 March 2011 09:34, Zoltan Selyem s...@elte.hu wrote:
%% Changes in volume affect all the staves in the MIDI output
%% instead of affecting only the one they are written in.
%%
%% This went wrong between 2.13.52 and 2.13.53
From 2.13.53, voices are mapped to MIDI channels instead of being
On 6 March 2011 16:34, Zoltan Selyem s...@elte.hu wrote:
% Hello,
%
% Accidentals on tied notes are printed at the beginning of a new
% system. But I think that in these cases there should be no second
% accidental in that measure.
%
% So I think measure 5, 9, and 13 are wrong in the
On 5 March 2011 13:38, Joe Neeman joenee...@gmail.com wrote:
This seems like a bad idea: ossia staves should be spaced like staves, not
like loose lines, right? If so, I have a patch ready...
Yep, that's a much better idea (I wish I'd thought of it when I added
those staff-affinity settings.
On 5 March 2011 12:23, Phil Holmes m...@philholmes.net wrote:
I did give the full detail in a previous mail, but a skeleton looks like
this:
\new Staff = MainStaff
\new Voice = MainVoice { SomeMusic
{
OtherMusic
}
\new Staff = Ossia \with {
\remove
On 5 March 2011 15:01, Phil Holmes m...@philholmes.net wrote:
Ah. Didn't realise you meant for them to be outside all staff definitions.
I've now changed this to read:
\relative c''{
\context Staff = MainStaff
\new Voice = MainVoice {
which is the only way I can see to put the lyrics
On 4 March 2011 18:25, Phil Holmes m...@philholmes.net wrote:
I reported on .user some problems I had with trying to get Ossia staves
properly spaced.
(http://www.mail-archive.com/lilypond-user@gnu.org/msg62140.html) Didn't get
a response, except from another user on .bugs who reported a
On 2 March 2011 09:52, Robin Bannister r...@dataway.ch wrote:
I can't get this to work. I would be interested in a simple
workaround to get from new to old as illustrated in the original bug report.
http://lists.gnu.org/archive/html/bug-lilypond/2011-02/msg00541.html I
want this for
2011/2/14 Janek Warchoł lemniskata.bernoull...@gmail.com:
The amount of whitespace after the barline is fixed, while it should depend
on whether the first note in the measure has an accidental or not. This
results in notes being too far from the barline, especially when there is
only one note
2011/2/9 Xavier Scheuer x.sche...@gmail.com:
%% Reported by 胡海鹏 - Hu Haipeng
%% http://lists.gnu.org/archive/html/lilypond-user/2011-02/msg00179.html
%%
%% [empty] Dynamics context prevents \RemoveEmptyStaves to work
%%
%% We should have a way to remove empty Dynamics contexts as well
%%
On 9 February 2011 14:56, Xavier Scheuer x.sche...@gmail.com wrote:
Is this the same issue as #631?
http://code.google.com/p/lilypond/issues/detail?id=631
AFAICS #631 does not have a Dynamics context but the problem seems to
be the same (misalignment of dynamic attached to a skip).
I do
On 7 February 2011 10:43, Trevor Daniels t.dani...@treda.co.uk wrote:
Perhaps this should be documented. Apart from noting
that it must be set in the Lyrics context it seems
straightforward to use. Does anyone know of any
difficulty with it?
It doesn't work with manual melismata (using
On 4 February 2011 23:18, Xavier Scheuer x.sche...@gmail.com wrote:
I'd suggest to add ly:stencil-scale , erm, somewhere, maybe as a
snippet and the \scale command to be added to
NR A.8 Text markup commands A.8.2 Align
near \translate and \rotate .
On 1 February 2011 09:15, -Eluze elu...@gmail.com wrote:
1) with the code below the accidental is misplaced:
\relative c' {
\hideCurvesFrom #'Voice.NoteHead #'(0.3 . 0.3) #'(0 . 0)
f2 ( gis4)
}
I don't think there's any workaround for this short of manually
shifting the accidental since
2011/1/19 Janek Warchoł lemniskata.bernoull...@gmail.com:
% the following scheme-made custom extender line from snippet 643
% prints the additional character not only at the ent of the extender line,
% but also when the extender line is interrupted by line break.
% i suppose it should be
On 2 February 2011 15:36, Reinhold Kainhofer reinh...@kainhofer.com wrote:
That's indeed a bug, and a nasty one in particular. I don't know of any
straightforward way to fix it.
Currently, I change the staff's middle C position (like \clef does) to get the
cue notes show up in their correct
On 31 January 2011 15:37, Reinhold Kainhofer reinh...@kainhofer.com wrote:
Unfortunately, I can't reproduce the problem with current master... I tried
running valgrind, but I only get some uninitialized variable warnings for the
usual *mark* functions (I sent a mail to lilypond-devel about
On 19 January 2011 06:53, Keith OHara k-ohara5...@oco.net wrote:
% Note spacing should allow for accidentals and articulations
% Usually it does, but slurs and ties can cause errors
\version 2.12.3 % same in 2.13.46
{ g''8( c''\espressivo geses'' b''') }
Hmm, tricky. The espressivo script
2011/1/23 Janek Warchoł lemniskata.bernoull...@gmail.com:
Quite what i was thinking about at the moment.
Yeah, i didn't realize that there is a problem where line breaks
should be forbidden...
Still i'm concerned about end users. I mean, in my opinion it would
be nice if even a temporary
On 13 January 2011 09:35, Keith OHara k-ohara5...@oco.net wrote:
Setting extra-spacing-height for KeySigs (or KeyCancels, or both) gives a
clean make check.
I checked that issue 1120 remains fixed; and experimented a bit looking for
other trouble, found none.
This is as I expected.
One
On 10 January 2011 20:29, Keith OHara k-ohara5...@oco.net wrote:
It looks like all other items that needed it got an extra-spacing-height.
I'm unclear on the zero-height-skyline concept, though,
and worry that typically end-of-line items like KeyCancellation might need
an
On 7 January 2011 02:34, Keith E OHara k-oh...@oco.net wrote:
Clearly it doesn't always happen. If we notice what prevents it, that might
be a valuable clue for the fix.
It only happens when there's an explicit key signature.
If you remove the default 'extra-spacing-height from
On 6 January 2011 15:08, Phil Holmes m...@philholmes.net wrote:
Bug?
Missing convert-ly rule.
interval-translate - coord-translate
http://repo.or.cz/w/lilypond/mirror.git/blobdiff/0cafb00c0023523503bc57644ac334eda127eaad..040fcffaf3d2a7e95dc08c4162d32fa5bc37a32d:/scm/lily-library.scm
Cheers,
On 27 December 2010 17:58, Jean-Charles Malahieude lily...@orange.fr wrote:
May I guess that it is due to \mark falling before the first note event
is generated?
No. It's a consequence of the way label-page-table is generated;
since 2.13.5 the order is consistently reversed, leading to
On 4 December 2010 17:56, Phil Holmes m...@philholmes.net wrote:
It compiles fine on my system on both 2.12 and 2.13.41 - albeit with, to my
eyes, strange but the same output on both.
You need to uncomment this line to see the error:
%\override Rest #'Y-offset = #0
This appears to be a
On 26 November 2010 01:47, Valentin Villenave valen...@villenave.net wrote:
Are you implying that an AbsoluteDynamicEvent, even when not preceded
with a CrescendoEvent, still creates a DynamicLineSpanner?
Yes. If an alignment spanner doesn't exist, it's created immediately
the
On 25 November 2010 17:45, Phil Holmes m...@philholmes.net wrote:
It wouldn't take me long to write a C# program (less than a day, I'd guess)
that reproduced quite a lot of the regtest checker functionality and did a
pixel-by-pixel check for image changes. I've done the latter bit in about
On 26 November 2010 00:00, Graham Percival gra...@percival-music.ca wrote:
Hmm. It shouldn't take a huge amount of time to compare each pair
of regtest images -- they're named, so you'd be comparing
something like 500 pairs of .png images. (Neil: were you thinking
of something else?)
I
On 24 November 2010 15:47, Phil Holmes m...@philholmes.net wrote:
So if a completely new bit of graphics appears, the regtest checker wouldn't
spot it? Not sure that's too good.
It might not, depending on whether the new grob influences bounding
boxes for other grobs.
What's the checker
On 24 November 2010 15:44, Valentin Villenave valen...@villenave.net wrote:
% Changing the stencil expression through the
% 'tweaks alist causes a grob to be printed twice.
It's not really the Tweak_engraver's fault (it's about as rudimentary
it's possible for an engraver to be): it simply
significant change (probably since the weighting between `time' and
`cells' for distance calculation is heavily biased towards the
latter).
Cheers,
Neil
From 51c5d78c57a252183f954f39f6397118711a8389 Mon Sep 17 00:00:00 2001
From: Neil Puttock n.putt...@gmail.com
Date: Sat, 20 Nov 2010 22:11:45 +
On 21 November 2010 23:16, Graham Percival gra...@percival-music.ca wrote:
Huh. So evidently there's some other reason behind the fix for
this break not being detected? It might be related to the
imagemagick's syntax change:
http://code.google.com/p/lilypond/issues/detail?id=908
I don't
On 22 November 2010 21:00, Reinhold Kainhofer reinh...@kainhofer.com wrote:
However, if the \bookpart contains a \markup, then LilyPond will crash. Simple
sample file is attached.
The same happens for page-markers (i.e., \break, \pageBreak, \label, etc.):
mypart = \bookpart {
\label #'foo
}
On 23 November 2010 21:52, Neil Puttock n.putt...@gmail.com wrote:
The same happens for page-markers (i.e., \break, \pageBreak, \label, etc.):
Not \break, of course. :)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman
On 19 November 2010 23:17, Valentin Villenave valen...@villenave.net wrote:
That's annoying. Should I reopen #1240? (Or possibly open a new issue
about it; we should also consider making it a High-prio, since I doubt
we want to release a new stable version with that much of a
performance
On 20 November 2010 00:22, Graham Percival gra...@percival-music.ca wrote:
That *is* the big picture. If the time field is fixed, and
the time+cells are documented, and if the bug squad followed the
printed checklist in the CG, then we would never need Nick to go
through and do benchmarks
On 18 November 2010 22:15, Keith E OHara k-ohara5...@oco.net wrote:
But I *like* being naive, Neil.
:)
The ugly truth is the units for vertical spacing changed from mm to staff
spaces. The current convert-ly rule also fails to convert to the new units,
in cases where units are not
On 19 November 2010 02:24, Keith E OHara k-ohara5...@oco.net wrote:
Now I see the value in a non-naive conversion that would produce something
like :
between-system-padding = 5\mm
system-system-spacing #'padding = #(/ between-system-padding staff-space)
I like this. :)
I was thinking of
On 9 November 2010 17:01, Mark Polesky markpole...@yahoo.com wrote:
See the post regarding this here:
http://lists.gnu.org/archive/html/lilypond-devel/2009-07/msg6.html
Can anyone confirm what Patrick wrote?
I'm afraid it's incorrect.
See my comment at the bottom of this post:
2010/10/29 Janek Warchoł lemniskata.bernoull...@gmail.com:
LilyPond 2.13.37, Windows 7.
system-system-spacing #'padding = #1
works like
system-system-spacing = #'((padding . 1))
(it resets other values to 0)
I think this will turn out to be issue 1338:
On 25 October 2010 21:37, Patrick McCarty pnor...@gmail.com wrote:
Yes, there is definitely a bug here. A large penalty of 50 is added
to some of the betting-looking slurs to avoid extra encompass
objects, but I can't see what object these particular slurs are trying
to avoid in this case;
On 25 October 2010 22:13, Werner LEMBERG w...@gnu.org wrote:
Yes, maybe – does it fix the problem?
It looks much better: the slur drops below the number.
Cheers,
Neil
___
bug-lilypond mailing list
bug-lilypond@gnu.org
On 23 October 2010 15:05, Carl Sorensen c_soren...@byu.edu wrote:
On 10/23/10 7:46 AM, Nikolaus Grill niki-gr...@hotmail.com wrote:
Oops, sorry,
looks like the message did get sent prematurely :-)
The version is 2.12.2
On version 2.13.36 the key signature has the flat before the sharp.
On 10 October 2010 10:01, Valentin Villenave valen...@villenave.net wrote:
Wow.
http://lsr.dsi.unimi.it/LSR/Item?id=692
http://lsr.dsi.unimi.it/LSR/Item?id=693
I was hoping whoever added them would fill in the descriptions, but
since that hasn't happened, I think we should just delete them.
On 26 September 2010 12:09, Xavier Scheuer x.sche...@gmail.com wrote:
MetronomeMark #'break-align-symbols seems to fail with everything
(clef, left-edge, staff-bar, ...) except key-signature and
time-signature
I'm afraid this is partly due to the way I fixed the bad alignment
when key
On 22 September 2010 11:18, Jeff Epstein
aliteralmind-lilyp...@yahoo.com wrote:
Note that
(box-padding . 0.5)
should be
'(box-padding . 0.5)
I believe this is a bug.
Thanks for the report. This will be fixed in 2.13.35.
Cheers,
Neil
___
On 11 September 2010 06:47, Jay Anderson horndud...@gmail.com wrote:
This is definitely a hack, but it works for me:
diff --git a/lily/spanner.cc b/lily/spanner.cc
index 32e0d21..827f5d6 100644
--- a/lily/spanner.cc
+++ b/lily/spanner.cc
@@ -112,6 +112,8 @@ Spanner::do_break_processing ()
On 8 September 2010 18:50, Alexander Kobel n...@a-kobel.de wrote:
Okay, this spares the manual counting of the length of the notes. But note
that this is NOT a cadenza in the sense of \cadenzaOn / \cadenzaOff, since
it amounts to _metered_ music, while \cadenzaOn introduces an _unmetered_
On 5 September 2010 00:07, Nick Payne nick.pa...@internode.on.net wrote:
I haven't been able to reproduce this behaviour with a small example, but
I'm getting some staves in a score where lilypond tries to fit too many bars
and the stave goes past the margin and off the right-hand edge of the
On 5 September 2010 00:22, Paul Scott waterho...@ultrasw.com wrote:
I have reduced the problem to the presence of a \tempo command:
Thanks for the report, Paul.
The segfault is triggered by the presence of the full-bar rest in the
lower stave: it prevents the setting of a horizontal parent for
On 2 September 2010 09:20, Phil Holmes m...@philholmes.net wrote:
I've had this sort of behaviour in the dim-and-distant with a compiler bug
on VMS. I was using 2 pointers pointing to the same memory location, and
changing the value with pointer 1 then reading it with pointer 2. The
On 28 August 2010 14:46, Marc Hohl m...@hohlart.de wrote:
Just a little ping - is the patch ok, or should I load it to Rietveld?
Looks OK apart from this:
+ %% NOTE: in lily/stem-tremolo.cc, we have length-fraction = 1,
+ %% and the tablature staff space is scaled by 1.5, so we use
On 28 August 2010 16:17, Carl Sorensen c_soren...@byu.edu wrote:
Why not use 1/staff-space? This would adjust things regardless of how
staff-space was tweaked, wouldn't it?
Yes. A simple helper function using ly:staff-symbol-staff-space would
suffice (apart from 'beam-width, which needs a
On 17 August 2010 21:57, Alexander Kobel n...@a-kobel.de wrote:
Oops, sorry, I see now the difference between those options for a
MultiMeasureRest and the PercentRepeat. For the former, there already is
the grob, and it just lacks the number. In the second case, the number is
not suppressed;
On 17 August 2010 14:22, Ian Hulin i...@hulin.org.uk wrote:
If a staff is included in a group like a GrandStaff or StaffGroup, the
grouping bracket graphic pushes the shortinstumentName string off the
left hand edge of the output PDF document. I've attached a demonstration.
This isn't a bug.
On 17 August 2010 21:20, Xavier Scheuer x.sche...@gmail.com wrote:
Is it possible to tweak countPercentRepeats in order to print the
number 1 above the first normal (i.e. with the notes instead of the
percent symbol) measure of a percent repeated measure?
No. In the first bar, there's no
1 - 100 of 281 matches
Mail list logo
