On 1/26/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
There are certainly places where that code can be simplified -- I've
even made some changes already in my working copy. There's a bunch of
(tried to check the jneeman branch on sv.gnu.org, but I couldn't see
anything
On 1/26/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
After running output-distance.py, none of the pngs are displayed. The
links in index.html point to, for example,
reference-lilypond/input/mutopia/W.A.Mozart/out-www/mozart-
hrn-3-page1.png
while the png image
On 1/26/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
I have all the page-breaking files with coverage around 90% now, but
I'll try to improve it a bit more (btw, the reason
page-turn-page-breaking.cc was so low is that I forgot to put a \book
around the regression
On 1/25/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Hello Joe,
2 questions
1. do you see any reason to use
ly:side-position-interface::y-aligned-side
for Y-offset callbacks on stuff that uses outside-staff-priority?
It makes certain user-overrides a little easier. Since
After running output-distance.py, none of the pngs are displayed. The
links in index.html point to, for example,
reference-lilypond/input/mutopia/W.A.Mozart/out-www/mozart-hrn-3-page1.png
while the png image is in
On 1/24/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
+ if (chunks.size () != div.size () + 1)
+{
+ programming_error (did not find a valid page breaking
configuration);
+ ignore_div = true;
+ assert (0);
this is better, but can we skip the assert()?
If this assert fails,
On 1/24/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
On 1/24/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
+ if (chunks.size () != div.size () + 1)
+{
+ programming_error (did not find a valid page breaking
configuration);
+ ignore_div = true
make web fails (latest git) on input/bach-schenker.ly with a guile
error. I've attached the log file.
Processing `/home/joe/oldhome/joe/programming/reference-lilypond/input/bach-schenker.ly'
Parsing...
Interpreting music...
On 1/21/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
This last one is giving me some problems: I have removed forced-distance
and collapsed everything into one VerticalAlignment. So now there is no
way to say something like the staves of a piano staff should
On 1/21/07, Graham Percival [EMAIL PROTECTED] wrote:
Does anybody know how to turn on (or turn off) various settings? I'm
trying to populate:
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Avoiding-tweaks-with-slower-processing
Although those docs are aimed at optimizing for
On 1/19/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Bertalan Fodor escreveu:
In that case, I recommend to use GrandStaff instead. The only reason
to use PianoStaff
is to get the fixed spacing to be able to handle cross-staff beams.
This fixed spacing is a very strict limitation, which
On 1/19/07, Rune Zedeler [EMAIL PROTECTED] wrote:
Mats Bengtsson wrote:
Wasn't the issue if it worked without the fixed spacing,
No, the issue was whether it worked with setting the fixed spacing
manually for each system - as illustrated in the example.
No, Mats is right. If you supply a
On 1/19/07, Rune Zedeler [EMAIL PROTECTED] wrote:
Joe Neeman wrote:
No, Mats is right. If you supply a fixed spacing, everything is easy.
Yeah, easy, I don't know.
But I do know that it does not work today even if you supply a fixed
spacing for each system.
Sorry, you're right
I've just committed one-pass vertical stretching to branch jneeman. I
haven't pushed to make web because I haven't yet checked regressions and
there is a change in behaviour -- it now stretches systems by default.
Stretching can be tuned by tweaking VerticalAlignment #'max-stretch. If you
want to
On 1/15/07, Rune Zedeler [EMAIL PROTECTED] wrote:
somebody forgot to attach include/object-key.hh to git.
I think the object key stuff was recently removed. Due to some dependency
caching (disclaimer: I don't understand the build system at all), the build
system thinks its still needed. Try
On 1/15/07, Anthony W. Youngman [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Joe Neeman
[EMAIL PROTECTED] writes
This is sort of a bug fix, but I thought I'd post it instead of
committing because it changes behaviour. In current lily CVS, it's
assumed that the first page of a book
On 1/11/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Rune Zedeler escreveu:
(moving to devel)
Han-Wen Nienhuys wrote:
I can't remember fixing anything that could cause this.
Weird.
This was fixed by Joe in 2.11, who triggered it with his skyline fixes.
Joe, can you try to backport
With latest git, make web fails on mozart-hrn-3.ly:
$ ./out/bin/lilypond input/mutopia/W.A.Mozart/mozart-hrn-3.ly
GNU LilyPond 2.11.10
Processing `input/mutopia/W.A.Mozart/mozart-hrn-3.ly'
Parsing...
Interpreting music... [8][16][24][32][40][48][56][64][72][80][88][96]
warning: cannot find start
On 1/2/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Hi,
I've been running coverage tests of the input/regression/ suite, to
see which parts of the code are not excercised. This has already
turned up some bugs.
You can get a full overview by running buildscripts/build-coverage.sh,
but here
On 1/6/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
Hi,
I have added scripts for profiling, see buildscripts/build-
profile.sh.
It turns out that the skyline related routines have replaced
Grob::get_property() as the top-contender in the profile
On 1/2/07, Joe Neeman [EMAIL PROTECTED] wrote:
On 1/2/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
diff --git a/lily/grob.cc b/lily/grob.cc
index 139a387..91f8ce5 100644
--- a/lily/grob.cc
+++ b/lily/grob.cc
@@ -420,11 +420,21 @@ Grob::extent (Grob *refp
On 1/7/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
One other solution would be to handle the accidental case explicitly
in pure-stencil-height but if there are other grobs that require
exceptional handling like this then it will get messy.
Any final
This is with latest git:
$ ./out/bin/lilypond input/regression/lyric-extender-no-heads.ly
GNU LilyPond 2.11.10
Processing `input/regression/lyric-extender-no-heads.ly'
Parsing...
Interpreting music... [1]
Preprocessing graphical objects...Segmentation fault (core dumped)
On 1/2/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
diff --git a/lily/grob.cc b/lily/grob.cc
index 139a387..91f8ce5 100644
--- a/lily/grob.cc
+++ b/lily/grob.cc
@@ -420,11 +420,21 @@ Grob::extent (Grob *refp, Axis a) const
Interval
Grob::pure_height (Grob *refp
On 1/3/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Just a quick idea: how about adapting the skyline procedures to
also put crude outlines of beams and slurs in the staff outline?
With a bit of luck, we could use that to scrap the
outside_slur_callback.
If we did a bezier - bunch of
On 1/2/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Hi,
I've been running coverage tests of the input/regression/ suite, to
see which parts of the code are not excercised. This has already
turned up some bugs.
You can get a full overview by running buildscripts/build-coverage.sh,
but here
On 12/29/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
OK, but accidental pure-height is important, so we can't just remove it
from the list, we need a pure-height callback. The actual print callback
is safe, right? So I can make a callback that checks whether
On 12/28/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Hi,
(define pure-print-callbacks
(list
ly:bar-line::print
ly:note-head::print
ly:accidental-interface::print
ly:dots::print
ly:clef::print
ly:text-interface::print
ly:script-interface::print))
I'm not sure if
On 12/27/06, Graham Percival [EMAIL PROTECTED] wrote:
Thomas Scharkowski wrote:
There is a space between clef and number in LilyPond 2.11.5 and
2.11.4.
It was o.k. until version 2.11.2 (I did not try 2.11.3)
Thanks for the exact bug report!
Fixed in git.
Now that I have my git woes sorted out, I have some new changes in the
jneeman branch. The main changes:
1) use skylines for vertical spacing in VerticalAlignment (ie. use in within
the system as well as between systems)
- as part of this change, I've removed support for
On 12/18/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
2) use skylines for horizontal spacing even when one of the columns is
non-musical.
- as part of this change, items in the spacing problem read the
'padding property (should I create a new property
I have a jneeman branch on savannah that has some old changes I don't
particularly want to keep. I have some new experimental changes on my local
copy that I want to push to savannah. Basically, I want to overwrite the
jneeman branch on savannah with my current working copy.
I created a
On 12/16/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
[git 2006-12-15, 20:40]
Look at this example:
\relative {
c2 c^This is a test |
\mark \default
c2 c |
}
\paper {
ragged-right = ##t
}
The rehearsal mark clashes with the markup. Additionally, it seems
that there are problems
On 12/12/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
... when you convert a vector of boxes into a skyline,
`vector'? You mean a bunch of boxes, right :-)
yep
you can pass a horizon-padding parameter x. This causes
- each box to be expanded by x in both directions
- on each side of
On 12/12/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
This was more of an internal-code comment than something that you can
directly do in a .ly file. One application, though, is that you can
decide that TextScripts should have a horizontal-padding of 2 while
When I make web with today's git, all the urls in the generated web pages
are missing the .html extensions (I did a full make clean and autogen.sh and
the problem was still there). For example, from [1], the User manual link
goes to [2] instead of [3].
[1]
Hi Graham and list,
Could you have a look at the section on skyline vertical placement that I
wrote? I think, btw, that skyline vertical placement isn't a good name for
this node. The only reason I call it skyline in the first place is that it
uses a skyline algorithm but that isn't really
OK, it might help if I attach the patch...
On 12/12/06, Joe Neeman [EMAIL PROTECTED] wrote:
Hi Graham and list,
Could you have a look at the section on skyline vertical placement that I
wrote? I think, btw, that skyline vertical placement isn't a good name for
this node. The only reason I
On 12/7/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
If a user wants the symbol to be positioned at an absolute
offset from its Y-parent, they can just set
outside-staff-position to () in addition to setting Y-offset.
Sorry, outside-staff-priority, not outside-staff-position.
This
On 12/7/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
well, it is using a priority field, which can have multiple values
for a single grob type.
Aah, if I understand you correctly, I can write
\override foo #'outside-staff-priority = #1
\override bar #'outside-staff-priority
On 12/7/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
That's right -- you need to override DynamicLineSpanner instead of
DynamicText (see the following example).
Well, it still doesn't work: I want to change Y-offset!
{
\override DynamicText #'Y-offset = #5.0
\once \override
On 12/5/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
If a user wants the symbol to be positioned at an absolute offset
from its Y-parent, they can just set outside-staff-position to () in
addition to setting Y-offset.
Unfortunately, I can't `just set outside-staff-position' because this
On 12/3/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
[git 2006-12-02 23:35]
Consider this:
\relative c {
#(set-octavation -1)
c1\p( | f1) |
}
\paper {
ragged-right = ##t
}
As shown in the attached image, the octavation is below the piano
sign. IMHO the opposite should
On 11/26/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
- on a random sample (mozart horn concerto), the skyline stuff looks
working. However, should we increase the default
padding/skyline-padding to improve appearance (see mozart concerto,
page 1, bar 68, forte and beam being close)?
On 11/28/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
On 11/28/06, *Werner LEMBERG* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Joe,
here's a quite important problem regarding skyline positioning and
outside-staff-priority. Hopefully, you can
On 11/28/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
Joe,
here's a quite important problem regarding skyline positioning and
outside-staff-priority. Hopefully, you can fix that easily since this
feature rocks!
What happens if you make the c'' higher? I should mention that the skyline
On 11/20/06, Erik Sandberg [EMAIL PROTECTED] wrote:
Hi,
I just got another idea of how to improve max-slope skylines. The
motivation
is mathematical rather than scientific, so there's no guarantee it's a
good
idea. But anyways:
The problem that max-slope tries to solve, is to separate objects
On 11/18/06, Graham Percival [EMAIL PROTECTED] wrote:
Sorry, could somebody else do this? I'm between laptops right now, and
I don't expect to have the new laptop completely working until sometime
next week.
OK, I've fixed this in master and stable/2.10
I don't think we need to make a new
Bah, my attachments were to big. Trying again...On 11/15/06, Joe Neeman [EMAIL PROTECTED] wrote:
The jneeman git branch now has 2 new features: max-sloped skylines (currently hard-coded at slope 2) and skyline debugging. I've attached a couple screenshots with the debugging turned on.
If anyone
On 11/14/06, Erik Sandberg [EMAIL PROTECTED] wrote:
Just a question: I have been thinking about skyline spacing in music for awhile (trying to figure out cases where skyline spacing can give badresults), and I have one idea: In some cases, objects could come too close
together with skyline
On 11/14/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu: If there are any references aboutskylines around, I'd be interested in seeing them; I just made things up as I went. Your suggestion (whichThere is one thing: you base the structure on lists, which makes for
easy merging
and funcbs.
+ skyline.hh -- declare Skyline class.
source file of the GNU LilyPond music typesetter
- (c) 2002--2006 Han-Wen Nienhuys [EMAIL PROTECTED]
+ (c) 2006 Joe Neeman [EMAIL PROTECTED]
*/
#ifndef SKYLINE_HH
#define SKYLINE_HH
-#include std-vector.hh
+#include list
+#include axis.hh
On 11/14/06, Werner LEMBERG [EMAIL PROTECTED] wrote:
Can Fontforge generate such outline information?No.This should be entered `manually' within the MF code.I don't know if this helps, but I made an algorithm to approximate bezier curves with straight lines (and I have a prototype in Haskell). If
When I build with --enable-debug --disable-optimising, make web fails (with latest git master). I've narrowed it down to the following command:./out/bin/lilypond -dgs-load-fonts --verbose -b eps input/regression/utf-
8.lyWhich causes gs (8.50) to barf with:Invoking `gs -dNOSAFER -dEPSCrop
On 11/7/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Or shall we start using git right now?I prefer this option.So it is now possible to commit directly to the git repo? If so, how can we get access?
___
lilypond-devel mailing list
On 10/31/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Hi guys,a draft of the 2.10 release announcement is at http://lilypond.org/web/announce-v2.10.htmlplease comment.
On the long term - In the long termandthis will enable other programss - ... programsOther than that, looks good.
On Sat, 2006-10-21 at 17:29 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
On Sat, 2006-10-21 at 12:15 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Mostly because at the time that I wrote it, I couldn't figure out how to
handle arbitrary length argument lists in scheme
+dtbMusic streams thess available/b - emOctober 21, 2006/em
thess? ^^
+
+dd
+The last months, Erik Sandberg has been overhauling the internals of
+Lily. This change introduces a new intermediate format, Music Streams,
+which will make it easier get music data out of
On Sat, 2006-10-21 at 00:02 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Here is an attempt at making simple-closures pure-evaluatable. A
summary:
1) move the conversion of non-pure-to-pure callbacks into C++ where it
is a bit easier to access and generalise it to support
On Sat, 2006-10-21 at 12:15 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Mostly because at the time that I wrote it, I couldn't figure out how to
handle arbitrary length argument lists in scheme (the only way I
currently know is to build the list of arguments, cons
I could have sworn I sent this last night, but it isn't in my sent
folder. Apologies if people get this twice.
It seems that every time a TextScript is created, it is sent to
Side_position_interface::set_axis (Y_AXIS). Is there a reason that we
don't just set Y-offset and side-axis in
On Fri, 2006-10-20 at 12:08 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
As far as I can tell, whenever a TextScript object is created, it is
immediately sent to Side_position_interface::set_axis(Y_AXIS). It seems
that it is better to just set Y-offset and side-axis in
define
a pure_avoid_slur_callback before 2.10. I
should point out, though, that the main problem in issue #113 has been
mitigated somewhat by the fact that TextScripts usually use normal
procedures now for Y-offset.
Thu Oct 19 14:32:16 IST 2006 Joe Neeman [EMAIL PROTECTED]
* Refactor the conversion into pure
As far as I can tell, whenever a TextScript object is created, it is
immediately sent to Side_position_interface::set_axis(Y_AXIS). It seems
that it is better to just set Y-offset and side-axis in
define-grobs.scm. Is there a reason this is not done? Same thing applies
to Script.
FWIW, this
On Sun, 2006-10-08 at 09:33 -0700, Graham Percival wrote:
Thanks, this should be helpful. Joe, I'll just leave this bug with you,
instead of filing it on the issue tracker. That ok?
Sure. I'll try to look at this soonish but I'm about to start traveling
so I can't promise anything...
-
On Wed, 2006-10-04 at 18:10 -0700, Matthias Neeracher wrote:
On Oct 4, 2006, at 6:51 AM, Han-Wen Nienhuys wrote:
.21 is out, with still more bugfixes. Happy testing!
Question: 2.9.21 changed some pagebreaks in my tests, i.e., songs
which fit on one page in .20 were broken into two
===
RCS file: /sources/lilypond/lilypond/ChangeLog,v
retrieving revision 1.5344
diff -u -r1.5344 ChangeLog
--- ChangeLog 30 Sep 2006 20:59:53 - 1.5344
+++ ChangeLog 1 Oct 2006 09:10:27 -
@@ -1,5 +1,8 @@
2006-10-01 Joe Neeman [EMAIL PROTECTED]
+ * Documentation/user
On Sun, 2006-10-01 at 11:17 +0200, Nicolas Sceaux wrote:
Joe Neeman [EMAIL PROTECTED] writes:
Just some random thoughts: it seems that you need the exact extent and
staff-extent for determining if a system is stretchable. If it were
possible to do it another way (say by setting a property
On Sat, 2006-09-30 at 14:51 +0200, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] lilypond]$ lilypond input/manual/font-table.ly
GNU LilyPond 2.9.20
Processing `input/manual/font-table.ly'
Parsing...
programming error: tried to space systems on a bad number of pages
continuing, cross fingers
On Sat, 2006-09-30 at 16:25 +0200, Nicolas Sceaux wrote:
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Nicolas Sceaux schreef:
Here is a patch defining a few functions for using the two-pass vertical
spacing scheme. Example:
given that Joe is now the Page breaking guru, I invite him to
is allowed
to increase the first page number by one if it will improve page
spacing.
2006-09-30 Joe Neeman [EMAIL PROTECTED]
* lily/page-turn-page-breaking.cc (calc_demerits): now that we allow
put_systems_on_pages to return an empty result, we need to assign
demerits properly
On Sat, 2006-09-23 at 13:47 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
Understanding the LilyPond source often boils down to figuring out what
is happening to the Grobs. Where (and why) are they being
On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
Understanding the LilyPond source often boils down to figuring out what
is happening to the Grobs. Where (and why) are they being created,
modified and destroyed? I've spent many hours tracing Lily through
On Wed, 2006-09-20 at 14:32 +0200, Erik Sandberg wrote:
On Monday 18 September 2006 16:09, Han-Wen Nienhuys wrote:
Erik Sandberg wrote:
I tried some days ago. A problem is that I still couldn't make web
completely, even without the patch.
That's strange. Did you try under GUB or a
On Wed, 2006-09-20 at 16:01 +0200, Erik Sandberg wrote:
On Wednesday 20 September 2006 15:01, Joe Neeman wrote:
On Wed, 2006-09-20 at 14:32 +0200, Erik Sandberg wrote:
On Monday 18 September 2006 16:09, Han-Wen Nienhuys wrote:
Erik Sandberg wrote:
I tried some days ago. A problem
-17 Joe Neeman [EMAIL PROTECTED]
* scm/define-music-types.scm (music-descriptions): remove
BreakEvent and fix {Page,Line}{Break,Turn}Event so
Music::to_event doesn't complain.
* lily/accidental-placement.cc (ape_compare):
* lily/semi-tie.cc (compare
On Sun, 2006-09-17 at 20:35 +0200, Ruud van Silfhout wrote:
I don't suppose you'd know how to do this in graphviz? I'm quite new to
it.
Hi,
Adding a label to a node is done by adding an extra line in the dot-file
containing the name of the node followed by [label=1:
Understanding the LilyPond source often boils down to figuring out what
is happening to the Grobs. Where (and why) are they being created,
modified and destroyed? I've spent many hours tracing Lily through a
debugger and it is mind-blowingly tedious.
So I quickly hacked a few things together and
On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
Some comments:
* can you add another macro layer, so __LINE__ and __FILE__ aren't
sprinkled around in the code? For good measure, you could also add
__FUNCTION__ .
How about something like the attached patch? I overload
On Sat, 2006-09-16 at 20:47 +0200, Werner LEMBERG wrote:
The file test.ly produces a
graphviz output file, graph.dot, that lets you visualise the changes
in Grobs throughout LilyPond execution. For now, you'll need to add a
closing brace to the end of graph.dot.
Very nice! A minor
On Sun, 2006-09-17 at 01:20 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
Some comments:
* can you add another macro layer, so __LINE__ and __FILE__ aren't
sprinkled around in the code? For good measure, you could also add
On Thu, 2006-09-07 at 15:57 +0100, Anthony Youngman wrote:
One thing I'd jump on with negative == no compression. It's been
commented elsewhere that the stuff I normally set (band parts) tends to
be very loosely spaced. If you've got a configurable compression
parameter, might it be an idea to
will remember the patch...
2006-09-09 Joe Neeman [EMAIL PROTECTED]
* scm/define-context-properties.scm
(all-internal-translation-properties): remove properties that
were used to communicate page-turn stuff to the paper-column
engraver.
* lily/lily-guile.cc
On Thu, 2006-09-07 at 08:10 +0200, Erik Sandberg wrote:
On Thursday 07 September 2006 02:25, Joe Neeman wrote:
On Wed, 2006-09-06 at 15:08 -0700, Graham Percival wrote:
Joe Neeman wrote:
By the absence of notes, do you mean {r | R | s} in all parts, or do
you mean {s} in all parts
isn't ready yet.
If this patch is OK, I want to do the same thing for vector_sort next.
2006-09-07 Joe Neeman [EMAIL PROTECTED]
* lily/spanner.cc (find_broken_piece):
* lily/spacing-spanner.cc (get_columns):
* lily/source-file.cc (get_line):
* lily/simple
On Thu, 2006-09-07 at 21:58 +0200, Ruud van Silfhout wrote:
it uses malloc to allocate memory for each item. This can also be done
using alloca, which allocates memory on the stack and, as a consequence,
does not have to be freed. but for alloca the same holds as for memrev,
it is not
I figured the new page breaking stuff might be more useful if people had
some idea of how to use it. Writing documentation is not something I've
had much practice with, so please point out any problems
2006-09-05 Joe Neeman [EMAIL PROTECTED]
* lily/page-turn-engraver.cc (penalty
On Mon, 2006-09-04 at 01:07 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
And of course I forgot to attach the patch...
On Sun, 2006-09-03 at 20:05 +1000, Joe Neeman wrote:
This patch gets rid of the old line breaker. It keeps the old page
breaker for now, but it is no longer
On Sat, 2006-09-02 at 11:54 +0200, Nicolas Sceaux wrote:
Joe Neeman [EMAIL PROTECTED] writes:
On Thu, 2006-08-31 at 22:11 +0200, Nicolas Sceaux wrote:
Joe Neeman [EMAIL PROTECTED] writes:
I want to replace the old page breaker and line breaker with the new
ones.
But please do
penalty is a bit arbitrary and I don't really like
adding un-configurable, arbitrary constants.
The patch also fixes a number of bugs that I discovered when I tried to
make web with the new page-breaker as default. The ChangeLog is long,
but most of the changes are small.
2006-09-02 Joe Neeman
On Thu, 2006-08-31 at 22:11 +0200, Nicolas Sceaux wrote:
Joe Neeman [EMAIL PROTECTED] writes:
I want to replace the old page breaker and line breaker with the new
ones.
But please do not delete the old line breaker and its interface, so that
it should still be called by user code
I want to replace the old page breaker and line breaker with the new
ones. The new algorithms are now (I hope) sufficiently powerful that the
old ones are simply special cases of the new ones, so this should be
do-able. But there is a problem.
With the new page breaking stuff introducing more
On Sat, 2006-08-19 at 20:00 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
+vectorSCM
+Page_breaking::systems ()
this looks like a potential memory error. The SCM vector is allocated
on the heap, and hence, is not GC scanned, and may be freed prematurely.
Please double check
OK
I think the subject line says it all. Here's a suggested patch.
Index: scripts/convert-ly.py
===
RCS file: /sources/lilypond/lilypond/scripts/convert-ly.py,v
retrieving revision 1.264
diff -u -r1.264 convert-ly.py
---
On Mon, 2006-08-07 at 12:38 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
The new files are attached in a tar archive (I cc to Han-Wen just in
case the list strips it). There are 13 of them, so I thought it would be
easier.
Looks good. Please apply, after fixing the following issues
On Mon, 2006-08-07 at 00:31 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
Here is my latest patch to add a new page-breaker. This actually adds 2
page breakers now:
Both page-breakers can be tuned with the (book-wide) paper block
variables page-spacing-weight (default 1.0) which
On Sat, 2006-08-05 at 12:07 +0200, Nicolas Sceaux wrote:
Joe Neeman [EMAIL PROTECTED] writes:
The problem is that the two page-breaking problems may not be
independent. In the page-turn-page-breaker, a page break after an even
page is different from a page break after an odd page
On Tue, 2006-07-25 at 16:43 +0200, Nicolas Sceaux wrote:
Joe Neeman [EMAIL PROTECTED] writes:
Here is my latest patch to add a new page-breaker.
May you not abbreviate that much variable names in scheme code?
It's usual to write full names, eg. paper-book and page-number,
iso. p-book
On Tue, 2006-07-25 at 16:36 +0200, Marco Gusy wrote:
Alle 21:02, mercoledì 19 luglio 2006, hai scritto:
Please read the section on Automatic accidentals in the manual.
/Mats
modern
This rule corresponds to the common practice in the 20th century. This rule
prints the same
the change in
interval-sane?, pdf generation would fail if the vertical spacing
overflowed the page. Also, we now check that a page is non-empty before
trying to annotate the systems.
2006-07-24 Joe Neeman [EMAIL PROTECTED]
* scm/define-grobs.scm (all-grob-descriptions): make
401 - 500 of 596 matches
Mail list logo
