On Sun, Sep 9, 2012 at 1:22 PM, Joseph Rushton Wakeling
joseph.wakel...@webdrake.net wrote:
On 08/09/12 16:10, Han-Wen Nienhuys wrote:
I have in the past talked with people from Henle; also, Schirmer has a
style guide that you can order as a book.
How far in the past are we talking about
https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
) procedure, and I'm
wondering what distros you developers
prefer to use (and why).
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl
.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
a damn about the
developer community.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Mon, May 18, 2009 at 10:30 AM, Francisco Vila paconet@gmail.com wrote:
I guess 'Feta' comes from 'font-en-tja' whatever this means, and the
Like LilyPond, font-en-tja is a private pun on the name of a girl that
Jan and I used to know.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
with the notion that Lily has a custom music font. Poeple only
need to know it is called emmentaler and is an OTF font when they need
to access it outside lilypond.
On Mon, May 18, 2009 at 11:26 AM, Francisco Vila paconet@gmail.com wrote:
2009/5/18 Han-Wen Nienhuys hanw...@gmail.com:
On Mon, May
On Mon, May 18, 2009 at 12:07 PM, Han-Wen Nienhuys hanw...@gmail.com wrote:
As for the naming: it started with Feta, then there was font for old
notation, which we named after old cheese (parmesan), then we created
OTF that contained both and the alfabet, so it was named after a big
cheese
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel
are not affected.
--
The Savannah Hackers
___
savannah-annou...@gnu.org mailing list
http://lists.gnu.org/mailman/listinfo/savannah-announce
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
LGTM
On Thu, May 28, 2009 at 5:00 AM, Patrick McCarty pnor...@gmail.com wrote:
Hello,
I need the attached patch to compile LilyPond.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond
of GDP and the frogs, in
particular).
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
gra...@percival-music.ca wrote:
According to
http://savannah.gnu.org/forum/forum.php?forum_id=5828
a push is precisely what we should do -- since git is a
decentralized source control system, that will upload all the
missing history.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
WINE.
I'll have a go at updating Pango next, as it has been implicated in
other font problems.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman
package to
g_win32_get_package_installation_directory() is deprecated and it is
ignored.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
requests with the powers that be?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
consensus with them. Furthermore, I think it is a wise use of time to
simple ignore whiners.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman
in the installation directory.
I already know what is wrong. I'll try to push a new release tonight.
(I found this bug on XP and fixed it there. I was assuming that the
Gub3 checksumming would rebuild the installers automatically, but that
was naive.)
--
Han-Wen Nienhuys - han...@xs4all.nl - http
Hi there,
can someone fix this? This currently hangs the website update.
mkdir -p out/locale/de/LC_MESSAGES/
msgfmt --output=out/locale/de/LC_MESSAGES/newweb.mo po/de.po
po/de.po:166: end-of-line within string
po/de.po:167: end-of-line within string
--
Han-Wen Nienhuys - han...@xs4all.nl
Please try 2.13.1-2 to see if this helps.
On Thu, Jun 4, 2009 at 5:25 PM, Paul Scottpsl...@ultrasw.com wrote:
Han-Wen Nienhuys wrote:
On Wed, Jun 3, 2009 at 3:04 PM, Patrick McCarty pnor...@gmail.com wrote:
Yes, I was testing the GUB binary at lilypond.org.
I have just confirmed
.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org
939d350c114854ce026e31eddb07abf73be6840f refs/tags/release/2.13.1-1
$ tags/release/2.13.1-1|head
tag release/2.13.1-1
Tagger: Han-Wen Nienhuys han...@lilypond.org
Date: Mon Jun 1 11:30:54 2009 -0300
commit 457b7a93eec7afdab5c76e99f3f4c151047e3bdb
Author: Reinhold Kainhofer reinh
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel
On Mon, Jun 8, 2009 at 11:27 AM, Graham
Percivalgra...@percival-music.ca wrote:
On Mon, Jun 08, 2009 at 10:07:30AM -0300, Han-Wen Nienhuys wrote:
The docs are specific to a given lilypond version, and should
therefore always be part of the main branch that contains the code.
The website
(and it is).
No, it is an automatic event, but only happens if the upload script
executes until the end.
I'll see what I can do wrt shipping the version number in the gub binaries.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
to be fail safe. So, possibly this is a GUB
bug/glitch/loophole, Han-Wen?
Could be; unfortunately, I have deleted the gub2 directory containing
the signatures used for creating the tarball, so I am not sure.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
. Please
don't go back to the lilypond 1.4 model; we abandoned it for a reason.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
at
the patches for #3. As long as the tarball builds on the system
requirements we list, I think we should just tell people to wait,
and spend our time working on that new release.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
--
Han-Wen Nienhuys - han
On Tue, Jun 9, 2009 at 12:35 PM, Graham
Percivalgra...@percival-music.ca wrote:
Err, did you send this privately deliberately?
On Tue, Jun 09, 2009 at 12:15:36PM -0300, Han-Wen Nienhuys wrote:
On Tue, Jun 9, 2009 at 11:36 AM, Graham
Percivalgra...@percival-music.ca wrote:
That's true
/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
generated files like ChangeLog or RELEASE-COMMIT in that dir,
should we?
correct. I think RELEASE-COMMIT is a new feature and has not been
debugged properly.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel
'' }
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
:
46 d-set_property (dot-count, scm_from_int (dur-dot_count ()));
This also means that the callback for 'dot-count
(dots::calc-dot-count) never gets used.
that would be a bug.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
:
Something like 'suppress-accidental that would fit right where
'force-accidental goes in the scheme expression. Is that
possible? Would it be difficult to implement?
It's quite simple to do.
Attached is a patch which uses an ampersand to hide accidentals.
--
Han-Wen Nienhuys - han
:
This patch fixes issue 778 in the tracker. If I should add a
regression test, I can do that.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman
On Sun, Jun 21, 2009 at 9:29 PM, Graham
Percivalgra...@percival-music.ca wrote:
macos-lilypad/ (new repo - question mark? should it be
integrated with gub?)
I would just leave this alone; it's not being developed, any effort
you invest in it is wasted.
--
Han-Wen Nienhuys - han
LilyPond, without the slash. I am not
very fond of the moniker though, and think just 'LilyPond' is easier
to read and looks.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
the spelling of
any syllable (and the space it takes up), so how do you decide between
contracting
aB - c - d - e
and
a - b - Cd - e
first?
the changed spelling may alter the size of the word, and may trigger
another round of contractions.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
library functions.
It should be fairly simple to check the functions (like you do here
ad-hoc) in a separate .scm file that is loaded if you run
ly/test-scm-functions.ly or something similar.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
an automated set of tests, that checks for example that
(eq? (split-at-predicate odd? '(2 3 6 8 9 0))
'((2) (6 8) (0)))
holds. It would be .ly file that runs Scheme function on a set of
inputs, and compares them to a set of outputs to make sure that they
match.
--
Han-Wen Nienhuys
GUILE itself,
but I am not sure if they export the functionality.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
the wrong place; auto beam settings does not control
how a (single) grob appears, so it should not be part of the Beam
grob.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
, like fixing lilypond code.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
-HEAD.webdoc.tar.bz2
the build number also seems broken. It should be build -1, not -0.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond
the headache.
Why dont you just leave them, and remove them if someone sends a nastygram?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
sure
that there are more interesting bugs in our tracker that need to be
dealt with more urgently.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman
?
No. But I do wish they would fix this...
I am currently without a lot of spare time at my work, but I can try
to have a gander over at the code to see if I can do something.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond
number. I suspect that this causes slight
breakage in certain scripts.
I get -0 every time, and I haven't a clue why.
The number should be (released build + 1). I think there is a bug somewhere.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
.
Interesting. Possibly this answers how Han-Wen made releases.
I'd just change the regexp and add HEAD\. [or even (HEAD\.)?]
and see when that breaks ... that could give more understanding
if it isn't a full fix :-0
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
will wedge yourself when you dont manage to deliver
the translation infrastructure for the new site, and in the process,
will probably piss off the guys that worked hard to translate the old
site.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
how development
tools work. If you think stepmake is bad, I invite you to write some
autoconf scripts to get a taste for how clean it actually is.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
staves automatically. I suggest you piggy-back off
that, generating a list of clefs with moments when to insert the
clefs, similar to scm/autochange.scm ; then translate that list into a
bunch of \skip and \clef commands.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
nice, but since x11-color.scm is basically dumb data,
this change introduces more places where bugs could hide.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
::set_parent() calls.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
the new features at their leisure.
Not sure if that would work for this change though.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
, just like all the doc policy items.
Sure - just include a .emacs snippet in the appropriate docs, so I
know how to configure my editor, if I ever get to hacking lily again.
:)
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
, though.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
of the two
behaviors.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
, as compared to GNU, and I think we generally had a tendency
to have ever stricter coding guidelines. For example, we have
underscores on class data members.
I don't see why we should not allow ourselves to be stricter wrt to
tabs as well.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl
, KDE/Qt has, X11 has, etc.
Hmm, we could just add this to every c++ file
// Local Variables:
// indent-tabs-mode: nil
// End:
that would fix everything, how about that?
Let's try to keep generated boilerplate to a minimum.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl
On Tue, Jul 28, 2009 at 7:08 PM, Graham
Percivalgra...@percival-music.ca wrote:
On Tue, Jul 28, 2009 at 03:56:53PM +, Han-Wen Nienhuys wrote:
On a larger scale, I am somewhat disappointed that a lot of the latest
lilypond efforts seem to be centered around janitorial work. While
-- ly:dispatcher?
listener -- ly:listener?
There are no other C++ predicate callbacks that have this problem.
Should I make convert-ly rules for them?
No; if someone complains, figure what to do afterwards.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
{ } and . The confusion
arises from your use of #(set! .. ), ie. direct interaction with the
scheme interpreter. It is assumed that people who do this know what
they are doing. Note that in 'native' lilypond syntax, this problem
is nonexistent, since assignments may only occur at toplevel.
--
Han-Wen
could be in another score entirely... I really think this needs to be
fixed.
Does this make more sense?
No. In the specific case, I'd recommend making another music function
that takes an argument, so you can pass the 15/16 explicitly, without
mucking with variables.
- Mark
--
Han-Wen
recall any major change that I contributed to 2.13.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sat, Aug 1, 2009 at 2:19 AM, Patrick McCartypnor...@gmail.com wrote:
Hello,
Is scm/kpathsea.scm used anymore? If not, can it be removed from
LilyPond's source?
It's a vestige from the time that we had special support for TeX. Feel
free to junk.
--
Han-Wen Nienhuys - han...@xs4all.nl
computed.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
and this was long before we started using mailing list
archives).
I can imagine how this would be implemented, but it would be a lot of
work. If anyone is up for a challenge, I can give some pointers. :)
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
On Fri, Jul 31, 2009 at 3:10 PM, Mark Poleskymarkpole...@yahoo.com wrote:
Han-Wen Nienhuys wrote:
No. In the specific case, I'd recommend making another music
function that takes an argument, so you can pass the 15/16
explicitly, without mucking with variables.
So it sounds like you
this action. In general the whole purpose of
having a source code control system is to _have_ an archive old
material. Why do you want to delete old stuff, or move it into a
different repo where nobody will be able to find it?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
On Thu, Aug 6, 2009 at 11:19 AM, Mark Poleskymarkpole...@yahoo.com wrote:
Han-Wen Nienhuys wrote:
I think in general the manual should not encourage users to define or
set variables using Scheme, exactly because the scoping semantics are
confusing.
I just had an idea. Why not make
of arguments, and by convention music is always in the last arguments,
so \afterGrace invocation should look something like
\afterGrace #'(15 . 16) d1 {c16[ d] }
You could use #15/16 ; GUILE nowadays has exact rationals.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
developers' time with hard-to-read code.
They were an in-crowd joke at some point, but I think the joke has
lasted long enough. I approve of changes that bring regularity in
this file naming scheme.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
On Mon, Aug 10, 2009 at 10:19 PM, Graham
Percivalgra...@percival-music.ca wrote:
The main doc pages all contain stuff like:
@c don't remove this comment.
@ignore
@omfcreator Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
@omfdescription Learning Manual of the LilyPond music
feta-accidentals
I also propose changing the following for fet_begingroup symmetry:
feta-arrow feta-arrowheads
paremsan-heads parmesan-noteheads
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
. The metrics for feta are computed by parsing the
metafont .log file. The .TFM files are unused, because of the limits
on different sizes, and because it does not support no negative width.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
, so they should be exact (for example:
note head dimensions); for others, the difference is unimportant: the
bass clef is covered by the staff anyway, so the half-linethick error
does not make a difference
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
that for
adjusting the bounds.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
continue the release if there are
regression errors.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
happens at most once every two weeks.
This is the wrong priority: this is the release manager's task, and
in the ideal world, and the RM would continue the release if there are
regression errors.
I mean: he would stop the release process.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org
?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
as '().
It there a preference? I suspect that we ought to be consistent, although
it's not highly important. It could be part of the code janitor work,
though.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel
to
save on symbol2scm call?
Sorry - I only took a brief look. It might not be worth the trouble
in this case, but in general it is better for the C++ part to work
with SCMs, so the symbol lookups can be memoized in the caller.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl
not to be
duplicated in the other backends, despite the comment. Perhaps it's
obsolete code?
The PS backend code went through various revisions, because it was
written before we had any page layout code. I suspect it is a vestige
of that era.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl
.
Before investing a lot of time in optimizing things, I recommend
running a profile.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond
- which isn't an issue on Mac OS X.
The lilypond installer is an aggregration of several packages, each
under its own license, rather than a derived work which would have to
be under GPL. There is no problem here.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
blessing.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Wed, Sep 9, 2009 at 7:24 PM, Joseph
Wakelingjoseph.wakel...@webdrake.net wrote:
Han-Wen Nienhuys wrote:
Jan and I know that the current situation wrt copyright headers and
license notes is not ideal, but we never could bring ourselves to fix
it, because there always were more important
you want with it.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
hypothesizing by non-lawyers, distracting people that actually produce
contributions.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
(or
laymen-people-interpreting-law) and bikeshedding discussions that this
'upgrade' has to involve. Ie. please reach consensus without me.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel
, 2020, we'll need at
least one lead developer with good Scheme-fu to (1) write most of the
heavy-lifting code, and/or (2) vet my/our Froggie work. In either case, my
Ouch. The traditional role is that the 'lead' (you, that is?) be the
programmer.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
-book.py - the source of the paper blocks created
by lilypond-book
Documentation/contributor/doc-work.itexi - and example of the
paper blocks created by lilypond-book
Does this command do anything?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
.
Now, GUB will build the version that is on your disk.
after releasing, merge the release branch back into master.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
On Fri, Sep 18, 2009 at 10:27 PM, Han-Wen Nienhuys hanw...@gmail.com wrote:
On Fri, Sep 18, 2009 at 2:26 PM, Graham Percival
gra...@percival-music.ca wrote:
Ok, no release today, at most 2 hours of work on Monday, and an
unknown (but fairly small) amount of time after that.
**
* could
the default is to collect all scores together and join them in a \book.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
.
I recommend you to read Eric Sandberg's thesis carefully to have a
better understanding how things mesh together.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
the hashes
change, and the comparison does not work anymore. It might be a good
idea to also strip the lp-book boilerplate from the input to the hash.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
101 - 200 of 3768 matches
Mail list logo
