Kieren MacMillan kieren_macmillan at sympatico.ca writes:
There are times I would like to offset something by a duration
(e.g., a quarter note) without using spacers
— for example, I have a ChordName that collides with a markup,
and I want the ChordName to move
horizontally to the right
Trevor Bača trevorbaca at gmail.com writes:
Did VerticalAxisGroup's default-staff-staff-spacing property stop
respecting the 'padding' attribute between 2.17.9 and 2.17.10?
I ask because I use a custom time signature context in my scores.
No, padding still works. The latest LilyPond
On Thu, 07 Feb 2013 20:56:06 -0800, Trevor Bača trevorb...@gmail.com wrote:
On Thu, Feb 7, 2013 at 2:02 PM, Keith OHara k-ohara5...@oco.net wrote:
Trevor Bača trevorbaca at gmail.com writes:
Did VerticalAxisGroup's default-staff-staff-spacing property stop
respecting the 'padding
David Kastrup dak at gnu.org writes:
Shouldn't we have a command
\transposing f { ... }
(better naming suggestions welcome) that does transposition and Midi
correction in lockstep?
I assume the command would produce the music that we currently get from
{\transposition f \transpose f
On Wed, 30 Jan 2013 02:41:50 -0800, d...@gnu.org wrote:
For you, a triplet consists of three notes. For me, a triplet consists
of a single note, three of which make up a triplet group.
The Wikipedia entry http://en.wikipedia.org/wiki/Tuplet oscillates
between both uses, mathematically of
On Sun, 27 Jan 2013 01:45:16 -0800, m...@mikesolomon.org m...@mikesolomon.org
wrote:
On 26 janv. 2013, at 23:21, k-ohara5...@oco.net wrote:
The tracker says the overall goal is to remove a call to the function
translate_axis. In the example
{ g4\ g'_pico g' g\! }
when we decide to move the
mike at mikesolomon.org writes:
The regtest outside-staff-placement-directive.ly is currently not doing what
it's supposed to because
of \textLengthOn, which masks the effects of the placement algorithm.
I must have inadvertently added that during a moment of sleeplessness...
I'll
Benkő Pál benko.pal at gmail.com writes:
2013/1/15 k-ohara5a5a at oco.net:
https://codereview.appspot.com/7108043/diff/1/lily/include/audio-
item.hh#newcode90
lily/include/audio-item.hh:90: virtual string to_string () const;
It seems fine to have the debug-output helper to_string(), but
On Mon, 14 Jan 2013 10:25:24 -0800, d...@gnu.org wrote:
If you can access the value with
staffline_ to_boolean(staffline_ - get_property(remove-empty))
at this point, that would seem to be simpler.
It would also mean that we can just leave keepAliveInterfaces alone when
switching between
David Kastrup dak at gnu.org writes:
I have a hard time considering the output of
Attachment (xxx.ly): text/x-lilypond, 226 bytes
useful:
\relative c' {
\set tupletSpannerDuration = #(ly:make-moment 1 2)
\times 2/3 { c8 d e f g a g f e d c d }
%
% The tuplet brackets last a
On Sun, 23 Dec 2012 06:29:30 -0800, d...@gnu.org wrote:
On 2012/12/23 14:24:31, Carl wrote:
I think the whole issue on this bug is incorrect.
The problem we have is that by using restrain open strings, we are
telling
lilypond Don't use open strings. Then by setting minimum-fret to 0,
we
On Sat, 22 Dec 2012 00:46:21 -0800, d...@gnu.org wrote:
In this particular case, however, the problem is adding an axis group to
an axis group. _Any_ old axis group to _any_ old axis group.
No no. The reported problem
\new StaffGroup \RemoveEmptyStaves b1 b
causes a StaffGrouper to be
Colin Hall colinghall at gmail.com writes:
You might have seen the bug report from Paul Morris entitled:
NoteHead X-offset, conflict with ly:grob-relative-coordinate
http://lists.gnu.org/archive/html/bug-lilypond/2012-12/msg00013.html
If one of the devs could have a quick look and give me a
On Fri, 30 Nov 2012 01:37:48 -0800, m...@mikesolomon.org wrote:
Ugh...this is a really nasty cyclic dependency.
There is sometimes a cyclic dependency message, but that is not the problem.
I'm pretty sure I used \stemUp to determine the stem directions and break this
dependency chain.
1)
On Sun, 18 Nov 2012 08:10:49 -0800, m...@mikesolomon.org m...@mikesolomon.org
wrote:
On 18 nov. 2012, at 00:55, k-ohara5...@oco.net wrote:
http://codereview.appspot.com/6827072/diff/11002/lily/box-quarantine.cc#newcode70
lily/box-quarantine.cc:70: return fabs (ii0.index_ - mid) fabs
On Sun, 18 Nov 2012 12:21:51 -0800, m...@mikesolomon.org m...@mikesolomon.org
wrote:
if (to_boolean (me-get_property (add-stem-support))
Stem::has_interface (e))
skyline.set_min_height (e-extent (common_y, _Y_AXIS)[dir]);
That's pseudo-code, but do you get the idea? Does that seem
Joram Berger joram.noeck at gmx.de writes:
http://lilypond.org/doc/v2.16/Documentation/notation/writing-rhythms#scaling-
durations
It is:
% Scale music by *2
Should it be?
[ ... ] % Divide durations by 2
The notes are typed printed as eighth-notes, but take up the time of
On Mon, 05 Nov 2012 21:52:15 -0800, m...@mikesolomon.org m...@mikesolomon.org
wrote:
On 6 nov. 2012, at 04:51, Keith OHara k-ohara5...@oco.net wrote:
Just to be clear, rest-collision.cc breaks the circular dependency by setting
positioning-done := true,
I'm still not sure how this breaks
mike at mikesolomon.org mike at mikesolomon.org writes:
On 5 nov. 2012, at 11:15, Werner LEMBERG wl at gnu.org wrote:
So the answer is yes: The height (resp. the depth) is larger for
outside-staff glyphs.
So we officially have a circular dependency: in order to know the height
mike at mikesolomon.org mike at mikesolomon.org writes:
If a Rest being managed by a RestCollision, a call to Grob::extent with any
common refpoint other than the Rest itself will trigger at some point
Rest_collision:calc_positioning_done ...
Not more than once.
On Mon, 29 Oct 2012 22:43:34 -0700, d...@gnu.org wrote:
if that is a real concern to you and not just a mock complaint,
Of course these are mock complaints; you gave me so much to mock.
This should be fine, after adding the start-condition in the scanner.
David Kastrup dak at gnu.org writes:
Keith OHara k-ohara5a5a at oco.net writes:
I timed LilyPond setting the percussion parts of a symphony,
Huh, I'd not have expected a net slowdown. Were you using the version
_after_ running convert-ly, or are we talking about compatibility mode
where
Trevor Daniels t.daniels at treda.co.uk writes:
David Kastrup wrote Sunday, October 28, 2012 4:34 PM
URL:http://code.google.com/p/lilypond/issues/detail?id=2934.
If we are going through with this one, it means that the
override/revert/overrideProperty syntax presented to users is
Werner LEMBERG wl at gnu.org writes:
Instead of having an optional argument
Remember that David's previous approach used no optional arguments,
the optional components were attached with dots to the core arguments
\override [Context.]Grob property[.subproperty] = #value
\tweak
David Kastrup dak at gnu.org writes:
Trevor Daniels t.daniels at treda.co.uk writes:
I don't understand. Are you suggesting we should not document
these new functions? If so, what is the set of commands which
should be documented?
I am not suggesting that. But there is public
Phil Holmes email at philholmes.net writes:
The one I don't understand is markup-special-characters.ly. I've
attached the difference image, but the summary is that with 17.2 there's a
visible hyphen in in-nocent, and this disappears with 17.4.
That changed with the first commit (1 of 2) in
Martin Tarenskeen m.tarenskeen at zonnet.nl writes:
I am not in favour of allowing different commands \times 2/3 and \tuplet3/2 to
do the same job. My voice would go to: just keep \times x/y the wayit is. I
can't see what makes 3/2 easier than 2/3. And having the choiceof two commands
doing
Werner LEMBERG wl at gnu.org writes:
I lean towards letting numbers in function arguments just evaluate
to themselves, never mind units.
Sensible.
+1. However, it should be documented, together with the work-around.
It was only a couple months ago that David allowed 3\cm to be used as
Ian Hulin ian at hulin.org.uk writes:
Questions:
1. Should the new \tuplet [...]
\tuplet 3/2 {c8 c c} because that reflects better the
three notes in the time of two definition of a triplet.
It is easier to keep the order straight if you write a 5:4 tuplet
as \tuplet 5/4 {}
We have to
On Tue, 02 Oct 2012 23:15:23 -0700, d...@gnu.org wrote:
\hide and \no are for different purposes
Oops, I forgot we were talking about the name 'no' for the function '\omit'.
The command to restore the stencil could be \unOmit or \restore.
I had to look up \remit in the dictionary, and
On Wed, 03 Oct 2012 01:25:30 -0700, d...@gnu.org wrote:
2. To restore. [Obs.]
[1913 Webster]
The archbishop was . . . remitted to his liberty.
--Hayward.
Don't believe everything you read.
Both 'remit' and
On Tue, 02 Oct 2012 04:42:59 -0700, d...@gnu.org wrote:
On 2012/10/02 11:01:52, Keith wrote:
Still looks good.
What does still look good?
The code, with either choice of naming.
URL:http://codereview.appspot.com/6575048/#msg4, so I'd like to see
the points made in comment #4 countered
Han-Wen Nienhuys hanwenn at gmail.com writes:
I think it is a much clearer abstraction to decide that each property
can only be evaluated once, and that everything should be driven by
callbacks. In fact, one thing I would suggest looking at is removing
{before,after}_line_breaking which
On Sat, 29 Sep 2012 10:30:32 -0700, m...@mikesolomon.org m...@mikesolomon.org
wrote:
The way you're using tentative is almost exactly how pure properties are used
in LilyPond.
Specifically, 'pure-height being the estimated vertical extent before
line-breaking, while 'height is its extent
Thomas Morley thomasmorley65 at googlemail.com writes:
I wanted to test Marc's bar-line-patch somewhat closer, but I have a
problem, not knowing what to do.
git apply --index 0001-bar-line.patch
error: patch failed:
Documentation/snippets/adding-orchestral-cues-to-a-vocal-score.ly:4
On Mon, 24 Sep 2012 15:51:43 -0700, Francisco Vila paconet@gmail.com
wrote:
2012/9/24 Janek Warchoł janek.lilyp...@gmail.com:
Seriously though, i think this syntax would be very useful for
algorithmic composers and computer programs manipulating Lily code.
Another advantage is code
On Mon, 24 Sep 2012 08:40:50 -0700, Janek Warchoł janek.lilyp...@gmail.com
wrote:
I imagine that we could have arbitrary integer durations intended for
use with straightforward tuplets, while continue using explicit \times
command for complicated (for example nested) ones.
Try it out. Enter
Graham Percival graham at percival-music.ca writes:
Currently, durations are limited to powers of 2 (plus dots).
Making a triplet involves the wordy \times x/y { ... } or a *x/y
scaling factor. We could avoid this (in common cases) by allowing
arbitrary integer durations.
c4 e \times
Graham Percival graham at percival-music.ca writes:
Although mathematicians and programmers are quite
comfortable with contains with 0 items inside them, this is not a
particularly intuitive concept (just look at the concept of zero
in the history of mathematics!)
Well, the concept and
On Sat, 22 Sep 2012 01:34:57 -0700, mts...@gmail.com wrote:
LGTM - looking forward to the skyline version, as that'll more
accurately reflect where columns are overhanging.
Well, long term I would like to use extent() to determine which columns have
overlapping extents, but need to find and
Marc Hohl marc at hohlart.de writes:
The testing process works fine on my local
machine, but 'make doc' fails due to some
syntax changes in the snippets. For example,
defaultBarType = empty will not work once
the patch is applied.
and I wonder if these changes should be included
*in*
mike at apollinemike.com mike at apollinemike.com writes:
On 2012/06/12 12:49:45, dak wrote:
http://codereview.appspot.com/6303065/diff/10003/lily/grob.cc
File lily/grob.cc (right):
http://codereview.appspot.com/6303065/diff/10003/lily/grob.cc#newcode472
lily/grob.cc:472:
Graham Percival graham at percival-music.ca writes:
On Sat, Sep 15, 2012 at 07:56:52PM +0200, Werner LEMBERG wrote:
Distinguishing \f and \F while ignoring case is going to be a rather
difficult operation.
I agree that distinguishing \f and \F is difficult. However, if
the
Werner LEMBERG wl at gnu.org writes:
I did not hear any serious desire to allow both \f and \F as
distinct.
Ugh, it seems that you haven't read my strong objections a few hours
ago.
You mostly objected to LilyPond /ignoring/ case, for reasons that made sense.
I guess you did say:
the
David Kastrup dak at gnu.org writes:
Phil Holmes email at philholmes.net writes:
What does get me more concerned is how hard
it is to find some of the correct ways of tweaking output. Using
voice.SomeValue (or is it Voice.someValue) when it should be
staff.Somevalue (or was it
Phil Holmes email at philholmes.net writes:
Results from my pixel comparator. Some good, some in need of consideration:
http://philholmes.net/lilypond/regtestresults/2.17.2/
These changes are expected and explained in tracker issues
2493
2611
2783
2493
728
2727
2493
1290
2493
On Wed, 12 Sep 2012 12:59:25 -0700, Phil Holmes m...@philholmes.net wrote:
From: Keith OHara k-ohara5...@oco.net
These changes are expected and explained in tracker issues
2493
Not convinced. Would we not expect the new time sig to be shown at the end
of the previous line? It's gone
On Sun, 09 Sep 2012 00:22:43 -0700, Benkő Pál benko@gmail.com wrote:
On Sat, 08 Sep 2012 15:26:21 -0700, benko@gmail.com wrote:
do we want to support
- NR 2.5.1 style 2-line percussion staves (setting both line-count and
staff-space to 2 instead of setting just line-positions to (-2
On Fri, 07 Sep 2012 09:23:08 -0700, m...@mikesolomon.org m...@mikesolomon.org
wrote:
On 7 sept. 2012, at 09:34, k-ohara5...@oco.net wrote:
Having the invisible Grobs taking up space will confuse the innocent.
I tried to add comments about this in the source - perhaps the CG needs an
David Kastrup dak at gnu.org writes:
Werner LEMBERG wl at gnu.org writes:
Actually, it's been in the back of my head for a while that those
pieces could be a great demo for Lilypond, particularly in respect
of being able to generate both written and sounding-pitched parts
for violin
I guess you are thinking we bring the dots inside the staff if there is at
least one staff-postion of space for each dot (as in 2-line percussion staves)
and continue to move them closer to the center if we find locations with at
least two-staff-positions of space for each dot, or more space
On Sat, 08 Sep 2012 15:26:21 -0700, benko@gmail.com wrote:
do we want to support
- NR 2.5.1 style 2-line percussion staves (setting both line-count and
staff-space to 2 instead of setting just line-positions to (-2 2))?
- default TabStaff's (even line-count, 1.5 staff-space)?
if we want to
Trevor Daniels t.daniels at treda.co.uk writes:
So what problems do the users have, exactly? We should address this
question first. Janek apparently has his list, which would be a good start.
But we should not invent problems where they don't exist. I've probably
read every email on the
On Wed, 05 Sep 2012 00:50:27 -0700, d...@gnu.org wrote:
On 2012/09/05 06:59:16, Keith wrote:
It costs a lot of programmer time to make the extra rules to save that
0.2%,
Not really.
But, but... flex documentation is pretty clear about [getting rid of] backing
up being very expensive :
Janek Warchoł janek.lilypond at gmail.com writes:
I think that for the next several weeks we should focus on gathering
information about the /problems/ people have. Not the ideas for
solutions. Problems.
For example,
in { a \parenthesize b \mf c d } it's confusing what gets
On Wed, 05 Sep 2012 02:54:38 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
Keith OHara wrote Wednesday, September 05, 2012 9:59 AM
The broad question is: Require delimiters to clarify context (for users,
LilyPond, and software importing LilyPond) -- more or less?
There are many places
On Wed, 05 Sep 2012 15:47:18 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
On Wed, 05 Sep 2012 02:54:38 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
There are many places in LilyPond now where delimiters are necessary
to resolve certain situations but are not generally mandatory.
Francisco Vila paconet.org at gmail.com writes:
For newcomers, the whole paradigm is a challenge. However, once they
have the basics, musicians can learn the rules.
\offtopic {
[...]
} % off-topic.
I found your \offtopic section, Francisco, to be quite relevant to the topic in
fact.
David Kastrup dak at gnu.org writes:
I proposed already at one point of time to require writing 4.0 rather
than 4. for the floating point number. This will not cure a lot of use
cases, and we still have the ambiguity between 4 the duration and 4 the
integer, and -4 the fingering and -4 the
David Kastrup dak at gnu.org writes:
David Kastrup dak at gnu.org writes:
Han-Wen Nienhuys hanwenn at gmail.com writes:
On Mon, Sep 3, 2012 at 11:46 AM, David Kastrup dak at gnu.org wrote:
I actually remembered one thing that remains worth doing: integrating
\chordmode into
David Kastrup dak at gnu.org writes:
Keith OHara k-ohara5a5a at oco.net writes:
Graham Percival graham at percival-music.ca writes:
Let's have a look at verbifying music functions.
[and special-cases that look just like music functions to the user]
balloonText
Daniel E. Moctezuma democtezuma at gmail.com writes:
I was wondering if there is plan to support Julian Carrillo's
notation on LilyPond.
It seems the answer is no.
It is a tablature notation, as opposed to staff-position notation, so maybe
the support for tablature could handle it. It is
Janek Warchoł janek.lilypond at gmail.com writes:
On Sat, Sep 1, 2012 at 5:41 PM, David Kastrup dak at gnu.org wrote:
Graham Percival graham at percival-music.ca writes:
So far I don't feel that the discussion has been very fruitful.
And it will not be fruitful in the near future. One
Graham Percival graham at percival-music.ca writes:
Let's have a look at verbifying music functions.
[and special-cases that look just like music functions to the user]
Most pre-fix functions do seem to be verbs expressing what we want LilyPond
to do to the following music. The exceptions
Han-Wen Nienhuys hanwenn at gmail.com writes:
I am actually supportive of allowing digits in identifiers, it has
irked me for years that we could not get it to work. I vaguely recall
you implemented this in 2.16 already, but I guess I am mistaken?
If we abuse the syntax, we can write
On Wed, 29 Aug 2012 11:23:42 -0700, mts...@gmail.com wrote:
http://codereview.appspot.com/6490043/diff/7001/lily/ledger-line-spanner.cc#newcode50
lily/ledger-line-spanner.cc:50: Paper_column::get_rank
(previous_column)))
It seems that previous_column should have a rank falling before current
mike at mikesolomon.org mike at mikesolomon.org writes:
On 30 août 2012, at 00:44, David Kastrup dak at gnu.org wrote:
Much more worrying
in my opinion is that the staffs in the first third of the page are
crammed into each other so tightly that it becomes quite hard to guess
which of
Phil Holmes email at philholmes.net writes:
Anyway, I found a number that concern me. See them at
http://www.philholmes.net/lilypond/regtestresults/2.17.1/.
I think all the concerns are covered by your tracker items, or otherwise
covered, or not concerns.
completion-heads-polyphony-2.png
On Tue, 28 Aug 2012 01:00:39 -0700, m...@mikesolomon.org m...@mikesolomon.org
wrote:
On 28 août 2012, at 06:08, k-ohara5...@oco.net wrote:
\override Accidental #'vertical-skylines = #'()
...
(you should set them to ly:grob::simple-vertical-skylines-from-stencil instead
of '()).
Xavier Scheuer x.scheuer at gmail.com writes:
Dear LilyPond developers and users,
dear bug squad, could you add this feature request on the tracker?
Here is a feature request made on the French users mailing list.
It can be seen as a mix of PartCombine and RemoveEmptyStaves.
This
On Tue, 21 Aug 2012 20:43:03 -0700, joenee...@gmail.com wrote:
Have you tried setting TupletNumber's priority to be smaller than
TupletBracket? It results TupletNumber moving twice as far as it should
That is a problem with the simple code.
What is the desired output, though, if someone
On Fri, 17 Aug 2012 10:16:25 -0700, mts...@gmail.com wrote:
http://codereview.appspot.com/5626052/diff/106004/lily/axis-group-interface.cc#newcode780
lily/axis-group-interface.cc:780: while (dirty);
On 2012/08/17 08:12:56, Keith wrote:
I am beginning to understand the new code. Would you
Joe Neeman joeneeman at gmail.com writes:
We need not let the distance function between A[UP] and B[DOWN] dictate,
because having positive distance between A[DOWN] and B[UP] is another
solution.
If you check out the dev/jneem-skylines (which is a simplified but not (yet)
On Mon, 13 Aug 2012 13:32:15 -0700, Benkő Pál benko@gmail.com wrote:
Keith, I hope I fixed lyrics-bar.ly.
Yes, it comes out nicely.
1. in repeat-sign.ly the thick-lined staff has now the dots
outside of staff, while the c++ version had it inside -
there may be a difference how
On Thu, 16 Aug 2012 01:39:15 -0700, d...@gnu.org wrote:
Will the added generality be enough?
Probably:
The remaining restriction is that Key signatures applying to all octaves will
have sharps on a compact range of positions lines, and similarly flats. If the
composer asks for accidentals
On Thu, 16 Aug 2012 11:09:51 -0700, d...@gnu.org wrote:
http://codereview.appspot.com/6461085/diff/2001/scm/define-grob-properties.scm#newcode481
indexed by the staff-position of the first C above centerline
This kind of indexing looks like it would only work for reasonably
standard staffs
Karol Majewski karol.majewsky at gmail.com writes:
Dear LilyPond friends!I have to say something that keeps me awake at night:
Current LilyPond flags look bad!
Yours look, ever so slightly, worse.
More like a computer drew them,
and the short-note stems look as if they might fall over.
Graham Percival graham at percival-music.ca writes:
On Thu, Aug 09, 2012 at 12:21:06PM +0200, Jan Nieuwenhuizen wrote:
Do we explain that we're a GNU project and as
such use GNU coding style? Together with a pointer to the info
node *(standards)Formatting, that could help.
Given that
Phil Holmes email at philholmes.net writes:
The texidoc for key-signature-cancellation.ly says Key cancellation signs
consists of naturals for pitches that are not in the new key signature.
Naturals get a little padding so the stems don't collide. The contributors
to the regtest
Marc Hohl marc at hohlart.de writes:
See the attached patch. It seems to work – I checked with
and the output looks as I would expect it.
Pál,
Could you adjust the algorithm to give normal space between repeat dots
in cases with no staff lines at all, like 'lyrics-bar.ly' ?
People will
Phil Holmes email at philholmes.net writes:
There are a number of significant changes, and 2 or 3 possible regressions.
Please look and check.
Almost all of these are from the revert of Pál's first attempt at issue 2553.
'arpeggio-no-staff' and other moving time-signatures
all the minor slur
On Sat, 04 Aug 2012 00:37:21 -0700, d...@gnu.org wrote:
On 2012/08/04 07:28:29, Keith wrote:
On 2012/08/01 06:45:22, MikeSol wrote:
Avoid measuring extents when engraving is happening because they
could be
dependent on other callbacks which could trigger many layout
decisions before
David Kastrup dak at gnu.org writes:
Keith OHara k-ohara5a5a at oco.net writes:
The pre-defined \cm is acted only in limited contexts -- the same
contexts where we are allowed to type decimal numbers without a leading #.
We would like those contexts to be even more narrow, immediately
On Thu, 26 Jul 2012 00:51:56 -0700, benko@gmail.com wrote:
Marc, please don't throw the whole 2533 issue stuff out; look at the
latest version at
http://codereview.appspot.com/6431044
in particular bar-line.cc and repeat-sign.ly.
I really don't mind if your patch goes before mine (it would
David Kastrup dak at gnu.org writes:
One problem I currently struggle with is supporting something like
\tempo 4. = 200
Your patch to re-allow \tempo in midi blocks will also need to restore
mention of the extra-space-trick \tempo 4 . = 90 in the docs, and in
your convert-ly rule.
David Kastrup dak at gnu.org writes:
\midi{\tempo 4. = 90}
\tempo can just switch lexing modes.
Oh. That would be nice.
Then we could continue to let 4. and .4 be valid where LilyPond
can accept a decimal number.
___
lilypond-devel mailing
Graham Percival graham at percival-music.ca writes:
This is a
problem for projects such as mutopia – a large fraction of their
.ly files don’t compile with current lilypond. That means that
they can’t benefit from recent bugfixes; users wanting the sheet
music in a different size (say,
David Kastrup dak at gnu.org writes:
One really ugly problem is interpreting things like 4.. Looks like a
duration, but then we have
input/regression/dynamics-broken-hairpin.ly: line-width = 4.\cm
The parser chooses among (too) many different modes (start conditions)
telling the lexer
On Fri, 20 Jul 2012 11:38:34 -0700, Marc Hohl m...@hohlart.de wrote:
I think that my current redefinition already includes the sorting
(see lines 578/579 of
http://codereview.appspot.com/6305115/diff/30001/scm/bar-line.scm)
I don't read Scheme, but it does seem to function properly.
so
I wasn't very clear with fragmented codereview comments below.
There is one new problem, with slurs silently dropped in
\partcombine {c''2^( d'')} {c'2( d')}
The problem is avoided if get_property(direction) is replaced with get_pure_property(),
but I don't like the idea of having even more
On Mon, 16 Jul 2012 22:42:55 -0700, gra...@percival-music.ca wrote:
regtest
I'm expanding `alignment-order.ly` after the patchy test.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Heikki Tauriainen g034737 at welho.com writes:
Here are some notes on a few minor defects that I have observed regarding
LilyPond's MIDI output together with links to patches with my attempts to
fix them.
Looks good. We will review and test just like we did last September.
Be patient. I've
Patch pushed.
On Tue, 10 Jul 2012 22:40:49 -0700, Frédéric Bron frederic.b...@m4x.org wrote:
patch proposed.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sat, 14 Jul 2012 19:14:41 -0700, d...@gnu.org wrote:
Do we have evidence of people using 2/ 3 anywhere?
I don't know of any scores with spaces alongside the / .
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Phil Holmes email at philholmes.net writes:
Please look at it and see if these are intended changes.
The changes to slurs across line-breaks are intended.
I don't know what caused the changes to slurs, probably the Stem/Flag work, but
I've updated issue 1327.
The stem failing to meet the
Frédéric Bron frederic.bron at m4x.org writes:
The following snippet does not give 1/32 notes grouped together as
expected with 2.15.39:
2.15.42 works as expected.
This was an un-related side effect to fixing the problems with the rules
for ending beams mid-measure in 3/4. Any
On Tue, 03 Jul 2012 10:51:05 -0700, m...@apollinemike.com
m...@apollinemike.com wrote:
Could you tell me the page and the document where the system overlay happens?
Second page of the bassoon part.
http://k-ohara.oco.net/Lilypond/TightSkylines/woods-Bassoon1.pdf
The source is one directory
Graham Percival graham at percival-music.ca writes:
Could we get a clear note about which commit(s) were reverted and
are presumably in limbo? If the remaining commits fixed 2604 and
2524 (which at a first glance appear to be resolved), then could
we get those marked as fixed so that I can
Graham Percival graham at percival-music.ca writes:
Let’s drop the “any unintended change” thing, and go totally with
the regression tests. Tests pass? We can make a stable release.
I don't know. Maybe that would be alright. I'm not sure.
The 'Regression' label would be come more important,
David Kastrup dak at gnu.org writes:
It is a reasonably safe bet that we won't have a stable release 2.16 in
the next two months given our current release policies and policy change
policies and their past effects on release candidates.
I'll take the other side of that bet.
LilyPond seems
201 - 300 of 552 matches
Mail list logo
