On Sat, Oct 2, 2010 at 9:01 AM, percival.music...@gmail.com wrote:
Has this patch been pushed, or definitely rejected, or is it waiting for
when Joe has some spare time (probably 2011 :) ?
http://codereview.appspot.com/1817045/
I was just waiting to see if the memory problems are still
On Wed, Sep 29, 2010 at 11:32 PM, Mark Polesky markpole...@yahoo.comwrote:
I must not be understanding this correctly, because it seems
to me that 'minimum-distance is redundant. If
'minimum-distance is less than 'space, it has no effect,
since IIUC 'space is only ever *stretched*, and never
On Thu, Sep 30, 2010 at 5:13 AM, David Kastrup d...@gnu.org wrote:
Wilbert Berendsen lily...@xs4all.nl writes:
Op donderdag 30 september 2010 schreef David:
With the current code, a score that used to take 5 pages now takes 8,
really really spaced out.
I don't see that we can
On Tue, Sep 28, 2010 at 9:37 AM, Mark Polesky markpole...@yahoo.com wrote:
NR 4.1.2 Page formatting defines stretchability as the
ease with which the stretchable space increases when a page
is stretched. Can anyone provide a more technical
quantified explanation?
We space systems by
On Tue, Aug 31, 2010 at 12:34 PM, Mike Solomon mike...@ufl.edu wrote:
Hey all,
I recently tried to programmatically add a pure-print function to the
list of pure-print functions using the setter method I proposed, which sent
lilypond into a 13+h spiral of compilation in functions having to
On Fri, Aug 27, 2010 at 1:09 AM, Phil Holmes m...@philholmes.net wrote:
Neil Puttock n.putt...@gmail.com wrote in message
news:aanlktin5woctsrz66d7g8m1py99sogdfgdc1h+cc7...@mail.gmail.com...
page-breaking-min-systems-per-page2.ly:
Addition of: warning: couldn't fit music on page in
On Thu, Aug 19, 2010 at 11:50 AM, Xavier Scheuer x.sche...@gmail.comwrote:
Hi Joe!
A recent message from 胡海鹏 - Hu Haipeng pointed out that the Dynamics
context do not seem to be well handled by the page breaking system.
It causes the couldn't fit music on page warning and the systems are
2010/8/19 Mike Solomon mike...@ufl.edu
This makes me wonder...if one creates a grob from the scheme-end, is
there a way that it can get in on the pure-print-callback action?
Currently, the list is not defined publicly. A simple define-public should
do the trick, but I’m not
On Mon, 2010-08-09 at 07:39 -0500, Jonathan Kulp wrote:
On Mon, Aug 9, 2010 at 6:24 AM, David Currie curri...@iinet.net.au wrote:
I am a musician and a programmer.
How does one redirect/direct (lilypond) compile output to a file and not
stdout
using command line options(or otherwise).
On Sun, 2010-08-08 at 13:27 -0700, -Eluze wrote:
with the code
\version 2.13.29
\relative c' { \repeat unfold 5 { c8 d e f g a b c} }
\paper {
ragged-last = ##t
ragged-last-bottom = ##f
}
i get the attached http://old.nabble.com/file/p29382522/test.png output
which is not what
On Sun, 2010-08-08 at 17:33 +0200, Reinhold Kainhofer wrote:
I'm having problems with page-turn breaking in one of my instrumental scores.
As the score is 3 pages (with optimal breaking) and has a long rest about 2/3
into the piece (with enough wiggle room to move the page break to the rest),
Hi Mike,
On Thu, Jul 22, 2010 at 7:24 AM, Mike Solomon mike...@ufl.edu wrote:
Hey all,
I'm almost finished w/ a vector-graphic-spanner project I've been
working on in Lilypond (that I'm planning on using during the International
Composers Pyramid in Kent tomorrow...crosses fingers...),
On Wed, Jul 21, 2010 at 3:09 PM, n.putt...@gmail.com wrote:
On 2010/07/21 21:04:38, Neil Puttock wrote:
Ah, don't worry, I think I see what's going on. It's creating a new
hash table
whenever the method's called:
+ if (!to_boolean (scm_hash_table_p (pure_height_cache)))
This is
On Wed, Jul 14, 2010 at 7:09 AM, Carl Sorensen c_soren...@byu.edu wrote:
On 7/14/10 4:21 AM, David Kastrup d...@gnu.org wrote:
Reinhold Kainhofer reinh...@kainhofer.com writes:
Am Mittwoch, 14. Juli 2010, um 08:47:17 schrieb David Kastrup:
Graham Percival gra...@percival-music.ca
On Wed, Jul 14, 2010 at 9:49 AM, Arno Waschk hamama...@gmx.de wrote:
On Wed, 14 Jul 2010 13:27:53 +0200, Arno Waschk hamama...@gmx.de wrote:
On Wed, 14 Jul 2010 01:53:21 +0200, Joe Neeman joenee...@gmail.com
wrote:
On Tue, Jul 13, 2010 at 2:55 PM, Neil Puttock n.putt...@gmail.com
wrote
On Wed, Jul 14, 2010 at 3:34 PM, Arno Waschk hamama...@gmx.de wrote:
On Wed, 14 Jul 2010 21:21:28 +0200, Joe Neeman joenee...@gmail.com
wrote:
On Wed, Jul 14, 2010 at 9:49 AM, Arno Waschk hamama...@gmx.de wrote:
seems this is something which is new (i tried as well 2.13.26).
it just
On Tue, Jul 13, 2010 at 2:55 PM, Neil Puttock n.putt...@gmail.com wrote:
Hi Joe,
On 13 July 2010 02:18, Joe Neeman joenee...@gmail.com wrote:
Does the attached patch help? For me, it reduces dramatically the
number of times that combine_pure_heights (and also ly_scm2interval)
is called
On Monday, July 12, 2010 06:51:15 am Arno Waschk wrote:
On Mon, 12 Jul 2010 15:02:26 +0200, Carl Sorensen c_soren...@byu.edu
wrote:
On 7/12/10 4:48 AM, Arno Waschk hamama...@gmx.de wrote:
Just finished a profile run with a larger score- ly_scm2interval is
reported to have consumd 16% of
dramatically the
number of times that combine_pure_heights (and also ly_scm2interval)
is called, but it has very little effect on lilypond's overall running
time (for the optimized build, at least).
Cheers,
Joe
From bd562d3d3e83a2545209bad8f6e97e2e263e8fe4 Mon Sep 17 00:00:00 2001
From: Joe Neeman
On Wed, 2010-06-30 at 07:04 +0200, David Kastrup wrote:
Joe Neeman joenee...@gmail.com writes:
On Tue, 2010-06-29 at 20:23 +0200, Arno Waschk wrote:
can't we have correct heights say for every bar (which must be computed
later anyway) with clever caching so we have them ready when
On Mon, 2010-06-28 at 06:34 -0400, Boris Shingarov wrote:
On 06/27/2010 01:25 PM, Joe Neeman wrote:
On Sun, 2010-06-27 at 06:56 -0400, Boris Shingarov wrote:
This was discussed on this list only a few weeks ago. I think we
are on
our way to get rid of global page*line breaking
On Wed, 2010-06-30 at 13:41 +0200, David Kastrup wrote:
Joe Neeman joenee...@gmail.com writes:
On Wed, 2010-06-30 at 07:04 +0200, David Kastrup wrote:
Joe Neeman joenee...@gmail.com writes:
On Tue, 2010-06-29 at 20:23 +0200, Arno Waschk wrote:
can't we have correct heights say
On Tue, 2010-06-29 at 20:23 +0200, Arno Waschk wrote:
can't we have correct heights say for every bar (which must be computed
later anyway) with clever caching so we have them ready when the final
layout is made?
No. For example, we don't know if a bar will have its clef displayed
until after
On Sun, 2010-06-27 at 06:56 -0400, Boris Shingarov wrote:
Hi Arno,
Here are some design remarks about what I understood from my work on the
breaker. Hopefully a sum of a few [dozen?] of mails like this will
together constitute something to transform into a chapter in the CG...
Thanks,
correct to begin with).
Cheers,
Joe
On Sat, 2010-06-26 at 13:49 +0200, Arno Waschk wrote:
git bisect says:
891840d4b25b71e9caac50174077d6461bb5cc7f is the first bad commit
commit 891840d4b25b71e9caac50174077d6461bb5cc7f
Author: Joe Neeman joenee...@gmail.com
Date: Mon Jun 21 23:11:42 2010
On Thu, 2010-06-24 at 14:05 +0200, Arno Waschk wrote:
On Sun, 20 Jun 2010 18:41:47 +0200, Joe Neeman joenee...@gmail.com wrote:
On Sun, 2010-06-20 at 16:19 +0200, Arno Waschk wrote:
dear list,
the following:
\version 2.13.23
\include deutsch.ly
TempoMark={ \time 4/4 \repeat
On Fri, 2010-06-25 at 17:17 +0200, Arno Waschk wrote:
oops, with lilypond from git i am getting compiling times higher by a
factor 10, and huge distances between staves! Bug of feature?
It doesn't sound like a feature. Can you figure out when it was
introduced?
Cheers,
Joe
On Tue, 2010-06-15 at 04:09 -0400, Boris Shingarov wrote:
Hi Joe,
Could you send me a list of the unreviewed patches that you have on
rietveld? I should have time in the next week or so to review them.
This issue is not so much the patches being unreviewed but rather
sitting
On Sun, 2010-06-13 at 02:02 -0400, Boris Shingarov wrote:
BTW, have you fixes for the vertical alignment been pushed yet?
You mean, the vertical space estimation? There were several bugs
screwing height-estimation. Some of those fixes are pushed, and some
are still sitting on Rietveld.
On Wed, 2010-05-12 at 22:14 +0200, Karl Hammar wrote:
Issue 1080: Regression: bar lines in double bar are positioned too
close together
pnorcks mentions commit 27a4d9354effb09c696925881ec4df007da8a0db
as a possible cause. Reverting part of that commit:
gives me the attached grace-start
On Sat, 2010-05-08 at 07:20 -0400, Boris Shingarov wrote:
On Fri, 07 May 2010 21:53:54 0200, David Kastrup wrote:
If we had something like that, one would not need to meddle with
paddings and the resulting spurious spacings.
Like in the old joke of a composition student being given
On Tue, 2010-05-04 at 12:43 +0200, Reinhold Kainhofer wrote:
For fixing the figured bass alignment (i.e. the 4 6 4 case with extenders
turned onn), I have a problem with the vertical alignment:
8 6 4 8 5 3
Should appear as
8
6 5
4 3
I'm adding the elements to the
On Wed, 2010-04-21 at 20:37 -0400, Boris Shingarov wrote:
What makes me really depressed about the situation with pure-height, is
that we have fixed a number of reasonable bugs in this area
(intersystem begin/rest, overridden stem length, deprecated space,
padding of markup -- these are the
On Sun, 2010-04-04 at 11:46 +0200, Nicolas Sceaux wrote:
+LY_DEFINE (ly_note_column__accidentals,
ly:note-column::accidentals,
+ 1, 0, 0, (SCM note_column),
+ Return the first accidentals found in @var{note_column},
or #f.)
Why not use DECLARE_SCHEME_CALLBACK and
On Sun, 2010-04-04 at 13:55 -0600, Carl Sorensen wrote:
On 4/4/10 12:20 PM, Joe Neeman joenee...@gmail.com wrote:
On Sun, 2010-04-04 at 11:46 +0200, Nicolas Sceaux wrote:
+LY_DEFINE (ly_note_column__accidentals,
ly:note-column::accidentals,
+ 1, 0, 0, (SCM note_column
On Thu, 2010-03-18 at 16:08 +0100, Valentin Villenave wrote:
Hi Joe, greetings everybody,
While working on the regtests I've been wondering if we'd need a
regtest for the (awesome) behavior that Joe implemented in December
2008 (commit 644008f18ec6780a812eee09ca549cf6b929037c requested by
On Tue, 2010-03-16 at 15:46 +0100, Reinhold Kainhofer wrote:
In the Figured_bass_engraver, I have a BassFigureAlignment spanner, where
Align_interface::add_element is used to append new figures. However, with
extenders turned on, it happens frequently that a new figure needs to be
inserted
On Mon, 2010-02-22 at 22:12 +, n.putt...@gmail.com wrote:
On 2010/02/22 21:10:25, joeneeman wrote:
For vertical positioning to work, it's important that
after-line-breaking be
called before Page_layout_problem does its work. Can you check that
this is
still the case?
The
On Thu, 2010-02-18 at 10:56 -0700, Carl Sorensen wrote:
On 2/17/10 4:53 PM, Joe Neeman joenee...@gmail.com wrote:
I don't really make use of it anymore, since I've become familiar enough
with the source that it isn't really useful. But it should still work
(there is a regression
On Thu, 2010-02-18 at 13:46 -0700, Carl Sorensen wrote:
On 2/18/10 11:58 AM, Joe Neeman joenee...@gmail.com wrote:
On Thu, 2010-02-18 at 10:56 -0700, Carl Sorensen wrote:
You need to be running a lilypond binary that was compiled with
--enable-debugging for it to work.
I've been
On Wed, 2010-02-17 at 15:21 -0700, Carl Sorensen wrote:
Joe,
I stumbled across your Life of a Grob feature while I was looking up stuff
on Figured Bass.
http://lists.gnu.org/archive/html/lilypond-devel/2006-09/msg00069.html
I think this would be really good to add to either the CG or
On Thu, 2010-02-04 at 15:33 -0500, Boris Shingarov wrote:
I am experimenting with some modifications to the line breaking code,
and I am stuck trying to understand how some of it works. So far my
understanding is that Simple_spacer operates on a vector of Grobs, and
it is a well-known
On Sat, 2010-01-30 at 16:08 -0500, Trevor Bača wrote:
On Sat, Jan 30, 2010 at 12:59 PM, Graham Percival
gra...@percival-music.ca wrote:
Since then, we've had
- skyline vertical placement (you don't need to manually
increase the
padding on text scripts!)
On Thu, 2010-01-21 at 13:51 -0500, Boris Shingarov wrote:
Quoting Joe Neeman joenee...@gmail.com:
Again, I'd suggest uploading patches to codereview.appspot.com, which
provides nice formatting and makes it easy to have multiple reviewers.
Ok, I've created Issue 190102 for this.
One
Thanks, pushed.
On Thu, 2010-01-21 at 23:02 +, shinga...@gmail.com wrote:
http://codereview.appspot.com/190102/diff/1/2
File lily/constrained-breaking.cc (right):
http://codereview.appspot.com/190102/diff/1/2#newcode529
lily/constrained-breaking.cc:529: last_markup_line_ =
On Wed, 2010-01-20 at 10:36 -0500, Boris Shingarov wrote:
Quoting Joe Neeman joenee...@gmail.com:
Again, I'd suggest uploading patches to codereview.appspot.com, which
provides nice formatting and makes it easy to have multiple reviewers.
Are there lilypond patches discussed
On Tue, 2010-01-19 at 22:25 +0100, David Kastrup wrote:
---
.../extending/programming-interface.itely |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/extending/programming-interface.itely
b/Documentation/extending/programming-interface.itely
On Wed, 2010-01-20 at 20:28 +0100, David Kastrup wrote:
Joe Neeman joenee...@gmail.com writes:
On Tue, 2010-01-19 at 22:25 +0100, David Kastrup wrote:
---
.../extending/programming-interface.itely |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
On Thu, 2010-01-14 at 23:34 +0100, Reinhold Kainhofer wrote:
Hi again,
The attached file contains two almost identical scores (just the
lenght of
them varies) without any special settings. However, the vertical
layout of
both scores with identical settings is radically different:
-) The
On Fri, 2010-01-15 at 09:06 +0100, David Kastrup wrote:
From the reports so far I get the impression that the new vertical
layout code is fundamentally broken, and the last fixes to it have
mostly been skirting the issue, in the class of I don't know why this
would happen, but we can fix it
On Thu, 2010-01-14 at 06:18 +0100, Wilbert Berendsen wrote:
Op donderdag 14 januari 2010 schreef Joe:
So it should just be a matter of finding the
right default for minimum-distance.
From my experimentation, 3.2 is a fine default value I think. 3 is a little
tight, 3.5 a little white
On Fri, 2010-01-15 at 18:08 +0100, Reinhold Kainhofer wrote:
Am Freitag, 15. Januar 2010 17:55:46 schrieb Joe Neeman:
On Thu, 2010-01-14 at 06:18 +0100, Wilbert Berendsen wrote:
Op donderdag 14 januari 2010 schreef Joe:
So it should just be a matter of finding the
right default
On Tue, 2010-01-12 at 11:58 -0500, b...@shingarov.com wrote:
Here is a proposed patch to add functionality to the Page Spacer.
When typesetting large quantities of markup lines, Lilypond currently does not
try to avoid widowed/orphaned lines. Some publishers will consider this an
On Wed, 2010-01-13 at 09:11 -0500, Boris Shingarov wrote:
Joe,
Paper_book::get_system_specs then you wouldn't even need the
markup-list-id property: you could add an avoid-orphan property that
only gets set for the last line of a multi-line markup list if it is
short. That might also
On Wed, 2010-01-13 at 17:21 +0100, Reinhold Kainhofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 13. Januar 2010 17:02:18 schrieb David Kastrup:
Alexander Kobel n...@a-kobel.de writes:
Wilbert Berendsen wrote:
LilyPond 2.12.2 and 2.13.1 display the Lyrics lines
On Wed, 2010-01-13 at 23:12 +0100, Alexander Kobel wrote:
Joe Neeman wrote:
Am Mittwoch, 13. Januar 2010 17:02:18 schrieb David Kastrup:
That's basically the approach taken by Joe for spacing staves: Place the
center lines minimum-spacing apart, except if the skylines would (almost
Here is the new code -- implementing all that's been discussed. (Ok,
not quite all -- the line length functionality is not implemented,
but
all the style remarks have been taken into account, the
markup-list-id
has been replaced with is-last-line, penalty made configurable, and
also,
On Sun, 2010-01-03 at 07:49 +, joenee...@gmail.com wrote:
Reviewers: hanwenn,
http://codereview.appspot.com/182042/diff/1004/6
File lily/lily-lexer.cc (right):
http://codereview.appspot.com/182042/diff/1004/6#newcode274
lily/lily-lexer.cc:274: Lily_lexer::set_identifier (SCM path,
On Mon, 2010-01-04 at 12:22 -0500, Chris Snyder wrote:
Yes, I am top-posting
I notice that issue 786 was just marked as critical. I sent the
following message to -devel four weeks ago but never received a
response. I'd appreciate advice on how to write messages that are more
Any objections/comments? If not, I'll push in the next few days.
Cheers,
Joe
On Tue, 2009-12-22 at 21:52 -0800, Joe Neeman wrote:
http://codereview.appspot.com/182042/show
This patch implements nested property setting for \paper block (and
\header block, etc) variables, similar to how
On Tue, 2009-12-29 at 15:48 -0700, Carl Sorensen wrote:
On 12/29/09 2:14 PM, Joe Neeman joenee...@gmail.com wrote:
I much prefer leaving it as a context property. Grob properties of the
TimeSignature grob should be things that affect the appearance of the
TimeSignature grob
On Wed, 2009-12-30 at 06:35 +0100, Werner LEMBERG wrote:
Folks,
why can I say
\new PianoStaff \with {
\override StaffGrouper
#'between-staff-spacing #'minimum-distance = #20
} ...
but not
\new Staff \with {
\override VerticalAxisGroup
On Tue, 2009-12-29 at 11:27 -0700, Carl Sorensen wrote:
On 12/29/09 8:41 AM, Carl Sorensen c_soren...@byu.edu wrote:
On 12/29/09 4:48 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Hi Carl
This looks like a much better approach. It means the
special
From a clean git clone (43a2f7a609ed14a1), I do
$ ./autogen.sh --enable-debugging --disable-optimising
$ make
and I find the following:
$ file out/share/lilypond/current/scm
out/share/lilypond/current/scm: broken symbolic link to
`/home/jneeman/src/lilypond//scm'
The problem is that my lilypond
On Sun, 2009-12-20 at 18:42 +0100, James Bailey wrote:
In checking the regressions, I've come across some issues. And, sorry
for posting these all in one go, but I've just been saving them up
until one day I could post a massive email and have the bug tracker
explode with new regression
On Thu, 2009-12-24 at 23:24 +, Graham Percival wrote:
On Thu, Dec 24, 2009 at 02:57:07PM -0800, Joe Neeman wrote:
On Sun, 2009-12-20 at 18:42 +0100, James Bailey wrote:
profile-property-access.ly errors and fails when I try to compile it.
Additionally, the properties shown
http://codereview.appspot.com/182042/show
This patch implements nested property setting for \paper block (and
\header block, etc) variables, similar to how \override works for nested
properties. In particular, you can do something like
\paper {
between-system-spacing #'space = #10
}
to
On Mon, 2009-12-21 at 16:34 +, Graham Percival wrote:
On Mon, Dec 21, 2009 at 4:26 PM, Graham Percival
gra...@percival-music.ca wrote:
On Mon, Dec 21, 2009 at 4:18 PM, Trevor Daniels t.dani...@treda.co.uk
wrote:
I'm trying a full rebuild now; I'm getting some errors, but I'm not
If you have a look at commit 06b6383aca113, you'll see a commented out
paragraph that looks like this:
@c FIXME: is it possible to have @example inside @warning?
@c @warning{ Adjacent non-staff lines should have non-increasing
@c @var{staff-affinity} from top-to-bottom. For example, the behavior
On Wed, 2009-12-16 at 20:06 +0100, Werner LEMBERG wrote:
Do you actually expect the vertical formatting of the snippet below as
shown in the attached PDF?
I wouldn't say I expected it, but I can certainly explain it: it's an
inconsistent handling of two related corner cases. When a loose line
On Sun, 2009-12-13 at 16:42 +, Neil Puttock wrote:
2009/10/13 Neil Puttock n.putt...@gmail.com:
2009/10/12 Joe Neeman joenee...@gmail.com:
Thanks for testing. Do you have an example to show the problem? It was
certainly my intention to have Dynamics work with alignment-distances
On Sat, 2009-12-12 at 22:27 -0700, Carl Sorensen wrote:
Here's part of the backtrace:
#4 0x000387f2 in Beaming_pattern::beamlet_count (this=0xa026a9c4,
i=-1608078908, d=DOWN) at beaming-pattern.cc:245
#5 0x0002f565 in Beam::set_beaming (me=0x3615ce0, beaming=0x3616cd0) at
beam.cc:1341
On Sat, 2009-12-12 at 17:22 +0100, Reinhold Kainhofer wrote:
Am Samstag, 12. Dezember 2009 15:43:37 schrieb 胡海鹏 - Hu Haipeng:
Sorry, Since the bad frustrating Midi tie problem persists, I have to roll
back to 2.13.7, and wait for a version with fixed tie playback.
I've tried to fix the
On Sat, 2009-12-12 at 14:15 -0700, Carl Sorensen wrote:
So I've finally gotten to a point where I think I know what to do with the
autobeaming code to make it work properly in 4/4 time with a 1/16 note in
the second beat.
I've written code to try to fix it. The code seems to execute
On Sat, 2009-12-12 at 07:00 +, Graham Percival wrote:
Just so that people know what's planned...
- another beta for 2.12.3 will happen as soon as I can build the tests
and docs. Jan and I will continue to work on this; hopefully it'll be
out in a few days. This will be the last 2.12
On Tue, 2009-11-24 at 01:03 +0100, David Kastrup wrote:
Carl Sorensen c_soren...@byu.edu writes:
IIUC, our policy is that *every* patch that is applied should result
in a buildable LilyPond. If not, it's a bad patch.
I don't consider this policy prudent in the particular situation API
On Fri, 2009-11-20 at 18:35 +0100, Reinhold Kainhofer wrote:
While fixing bug 676, I ran into a very strange memory corruption situation:
Like in the tie-engraver.cc, I used vectors in tie-performer.cc to store the
moment together with the Audio_element_info.
Now, this always led to memory
proposal for a solution was ok, but it would require Chris to throw away
all the work he had done on my _first_ proposal.
Over the past couple of days, I've been working on fixing a couple of
bugs that were caused by an earlier bug fix I submitted (that was
accepted). Joe Neeman has given
On Wed, 2009-11-11 at 10:33 -0500, Chris Snyder wrote:
I've done some work towards fixing issue 800, and at least now
understand what's happening:
The patch that introduced the bug added a check in
Extender_engraver::stop_translation_timestep() to check if the current
voice was in the
On Wed, 2009-11-11 at 14:41 -0500, Chris Snyder wrote:
1) Change melisma_busy() to return true if in the middle of a note
2) Alternatively, add the check in
Extender_engraver::stop_translation_timestep instead
I'm confused: isn't the current check in
On Tue, 2009-11-10 at 21:57 +, csny...@mvpsoft.com wrote:
On 2009/11/10 20:00:00, joeneeman wrote:
http://codereview.appspot.com/150067/diff/2003/3005#newcode113
lily/extender-engraver.cc:113: if (!melisma_busy (voice)
!current_lyric_is_skip_ lyric_acknowledged_)
Could you please
On Thu, 2009-10-29 at 17:40 +0200, Reinhold Kainhofer wrote:
In the LSR there are two examples for incipits:
http://lsr.dsi.unimi.it/LSR/Item?id=582
http://lsr.dsi.unimi.it/LSR/Item?id=348
The first one was written by Nicolas Sceaux, who generalized it to his clef-
keys.ily package to
On Wed, 2009-10-28 at 21:54 +0100, Nicolas Sceaux wrote:
Le 28 oct. 09 à 08:37, David Kastrup a écrit :
Carl Sorensen c_soren...@byu.edu writes:
Isn't the problem that beams create melismata in vocal music, and you
don't want to have a line break in the middle of a melisma?
Baroque
On Tue, 2009-10-27 at 01:54 -0700, Patrick McCarty wrote:
On 2009-09-27, Werner LEMBERG wrote:
What's the reason that line breaks are by default forbidden if
there is a broken beam crossing the bar line, and that you have to
set the `breakable' flag manually to override it?
BTW,
On Sat, 2009-10-24 at 14:01 -0600, Andrew Hawryluk wrote:
On Sun, Oct 11, 2009 at 8:58 PM, Joe Neeman joenee...@gmail.com wrote:
On Wed, 2009-10-07 at 22:18 -0600, Andrew Hawryluk wrote:
- LilyPond 2.13.5 currently has a vertical spacing problem (no padding
between staves).
how about
On Tue, 2009-10-27 at 12:06 -0700, Patrick McCarty wrote:
On 2009-10-27, Joe Neeman wrote:
On Tue, 2009-10-27 at 01:54 -0700, Patrick McCarty wrote:
On 2009-09-27, Werner LEMBERG wrote:
What's the reason that line breaks are by default forbidden if
there is a broken beam
On Sun, 2009-10-18 at 18:34 +0200, Nicolas Sceaux wrote:
Hi,
What is the new way of setting the next padding and spacing of an
individual line
(a markup line in that case)?
I am asking because there is a regression regarding markup lines: they
used to be
densely spaced, with no
On Mon, 2009-10-12 at 06:55 -0400, Kieren MacMillan wrote:
Hi Joe,
1. I used to define custom contexts FirstLyric and MoreLyrics, in
which [only] the #'minimum-Y-extent was set differently, in order to
control inter-multiple-Lyric spacing — am I right in inferring that
On Mon, 2009-10-12 at 21:00 +0100, Neil Puttock wrote:
Hi Joe,
I've been testing the new Dynamics context in various situations, and
it's a struggle to get consistently centred dynamics without
trial-and-error tweaks for inter-staff-spacing. It also seems to be
incompatible with
On Wed, 2009-10-07 at 22:18 -0600, Andrew Hawryluk wrote:
- LilyPond 2.13.5 currently has a vertical spacing problem (no padding
between staves).
how about this:
\layout {
\context {
\PianoStaff
\override StaffGrouper #'between-staff-spacing #'padding = #0.5
}
}
If you find a good
On Tue, 2009-10-06 at 10:30 -0400, Kieren MacMillan wrote:
Hello all,
Is there a fix yet for the problem [2.13.4-1] that between-system-
padding etc. doesn't work with Lyrics (because they're nonspaceable)?
It's killing me with the lead sheets I'm trying to put out. =(
On Mon, 2009-09-28 at 18:04 +0100, Neil Puttock wrote:
2009/9/27 Ian Hulin i...@hulin.org.uk:
Declared in context_property.cc only are:
general_pushpop_property (which calls sloppy_general_pushpop_property)
execute_override_property
This looks like an oversight, since they should also be
On Fri, 2009-09-18 at 18:06 -0600, Carl Sorensen wrote:
It would be convenient if the output-prefix could be defined in the /score
or /layout block that causes the creation of a Score context. I think
that's why Ian was wanting to make it a context property of Score. But I
suspect (although
On Wed, 2009-09-02 at 09:34 +0200, Michael Käppler wrote:
Hi Neil,
1. Setting system-count = 1 causes a segfault (try running the file
Documentation/general/examples/granados.ly)
I've checked out a fresh master and it seems that it also crashes
without my patches. Can you reproduce
On Tue, 2009-09-08 at 01:05 +0100, Graham Percival wrote:
On Mon, Sep 07, 2009 at 04:42:07PM -0700, Patrick McCarty wrote:
In light of recent suggestions to change LilyPond's copyright to GPLv2
or later, I am reminded of the Ghostscript 8.70 announcement to
gs-devel back in July.
On Wed, 2009-09-02 at 09:34 +0200, Michael Käppler wrote:
Hi Neil,
1. Setting system-count = 1 causes a segfault (try running the file
Documentation/general/examples/granados.ly)
I've checked out a fresh master and it seems that it also crashes
without my patches. Can you reproduce
On Sat, 2009-08-22 at 07:22 +0200, Werner LEMBERG wrote:
[git dd442f49]
This simple input
\relative {
\repeat unfold 31 { c'1 r r r r r r r }
}
makes the vertical layout overflow instead of properly filling two
pages. If you slightly increase the repeat factor, the lowest
On Mon, 2009-08-17 at 14:44 +0200, Michael Käppler wrote:
There's no top-level paper block, so default-paper will only contain
what's stored in paper-defaults-init.ly.
The ps output engine in framework-ps.scm:92, however, looks for a
global line-width. Currently, this line-width is just the
On Sat, 2009-08-22 at 13:01 +0200, Reinhold Kainhofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 22. August 2009 02:28:39 schrieb joenee...@gmail.com:
On 2009/08/22 00:11:34, Reinhold wrote:
http://codereview.appspot.com/109070/diff/1/2
File
On Thu, 2009-08-20 at 23:38 +0100, Trevor Daniels wrote:
I'm trying to complete the 'prob' entry in the Technical glossary.
From a position of ignorance I've come up with this:
PRoperty OBjects, or @strong{probs} for short, are instances of
the @code{Prob} class, a simple base class for
101 - 200 of 596 matches
Mail list logo
