2008/12/12 Eyolf Østrem :
> I don't know about the devs -- you're probably right that to them, new
> features are more interesting -- but THIS user sticks with LilyPond because
> the
> output is superb. As it is, LP deals with 99% of the western music notation
> canon, and to me, the perfectioning
> OK, I buy your idea, but the involved changes are invasive and will
> also require changes in GUB. I'll do my best to keep everything
> working thanks to testing and greping through the sources, but I may
> miss some details -- you have been warned.
:-) A new build will show all the problems.
My impression is that we have more people doing bug fixes now than a
couple of
years ago (at that time it was primarily Han-Wen and Jan), but that the
number of
fixed bugs per week and bug fixer is lower. On the other hand, the
number of newly
introduced bugs (not to be confused with the number
Problem building the netpbm package. gcc doesn't seem to
recognize the "-flax-vector-conversions" option, but doens't gub
download gcc itself to avoid specific-version compiler problems?
Log attached.
Cheers,
- Graham
must rebuild[linux-x86]: tools::netpbm tools::curl tools::expat tools::git
ge
On Fri, Dec 12, 2008 at 11:25:44AM +0100, Werner LEMBERG wrote:
>
> > I've started creating auxscripts/ (for scripts that needn't be built)
> > and auxpython/ (for Python modules that needn't be built), and I'll
> > commit as soon as I can't find remaining breakages.
>
> Someone this list (Graham
On Fri, Dec 12, 2008 at 01:09:53PM +0100, Mats Bengtsson wrote:
> My impression is that we have more people doing bug fixes now
> than a couple of years ago (at that time it was primarily
> Han-Wen and Jan), but that the number of fixed bugs per week
> and bug fixer is lower.
Oh, definitely -- b
It uses compiled GCC for the cross compiler, but 'local' packages
(like netpbm) get compiled with local GCC. As a workaround, you can
installn netpbm from the distribution and disable it in gub.
On Fri, Dec 12, 2008 at 12:18 PM, Graham Percival
wrote:
> Problem building the netpbm package. gcc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. Dezember 2008 schrieb Han-Wen Nienhuys:
> It uses compiled GCC for the cross compiler, but 'local' packages
> (like netpbm) get compiled with local GCC. As a workaround, you can
> installn netpbm from the distribution and disable it in
Hi Werner,
> Hehe, still not perfect. Sorry for being such a PITA :-)
If you weren't, I'd ask you to be. ;-) Lilypond wouldn't be what it is
if it weren't for people like Han-Wen, you and the other developers
who aim for the highest possible quality standards. Vice versa I
apologize for giving yo
Is there a way to set the accidental style in the layout block?
If not, shouldn't there be? Something like...
\layout {
\context {
\Score
accidentalStyle = #'modern
}
}
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.or
2008/12/12 Mark Polesky :
> Is there a way to set the accidental style in the layout block?
Yes :
\layout {
\context { \Score % or Staff, or Voice
autoAccidentals = #yourstyle
autoCautionaries = #yourotherstyle
}
}
yourstyle may be one of the predefined styles (have a look at
music-functio
My goodness, Valentin, I would never have figured that out.
Is this described in the docs somewhere? It should be.
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Does anyone think it would be worth adding the
syntactic sugar to allow this?
\layout {
\context {
\Score
accidentalStyle = #'modern
}
}
or this?
\layout {
#(layout-set-accidental-style 'modern)
}
as opposed to the current method (as I understand it):
modern = #`(Staff ,(make-ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's a patch that adds ticked barlines (i.e. a tick of the length of a staff
space through the top-most staffline):
http://codereview.appspot.com/10645
Please review.
Unfortunately, I'm running into one problem: It seems that for each barl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. Dezember 2008 19:41:44 schrieb Galen Toews:
> I cannot find how to produce a thick bar.
As far as I can seen in the code in bar-line.cc, there is currently no way to
create a single thick bar line. In compound barlines, a thick line i
Le vendredi 12 décembre 2008 à 06:21 -0800, Graham Percival a écrit :
> On Fri, Dec 12, 2008 at 11:25:44AM +0100, Werner LEMBERG wrote:
> > Someone this list (Graham?) made the suggestion to move all script
> > subdirs into the `script' directory to avoid cluttering of
> > lilypond's top-level dire
2008/12/12 Reinhold Kainhofer :
> Unfortunately, I'm running into one problem: It seems that for each barline in
> a staff group the function is called multiple times and the resulting stencil
> also shifted differently. In particular, for all staves except the last in a
> staff group a tick is cr
2008/12/10 Han-Wen Nienhuys :
> Some random comments:
Thanks for these suggestions! They are implemented in the attached
patches. Please let me know if you'd like some further corrections.
> - have a look at scm/script.scm to set defaults just for staccato.
Following Neil's suggestions, I set t
On Fri, Dec 12, 2008 at 10:20 PM, Maximilian Albert
wrote:
u
>> - add a regtest. Should be short, with a short doc string explaining
>> the functionality.
>
> Done (patch #2). I hope it meets the requirements for a regtest.
> Please let me know if anything is missing or wrong.
No need to test 3 v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 13. Dezember 2008 00:55:11 schrieb Neil Puttock:
> 2008/12/12 Reinhold Kainhofer :
> > Unfortunately, I'm running into one problem: It seems that for each
> > barline in a staff group the function is called multiple times and the
> > result
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a server with a 64-bit processor, on which I have installed a 32-bit
Linux distribution (so I can reuse all my 32-bit self-created packages, among
other reasons). Now, Graham is trying to use that server also as a build
machine for lilypond r
On Fri, Dec 12, 2008, Reinhold Kainhofer said:
> Should we change \bar "." to create a single
> thick barline for reasons of consistency and instead add a new
> bar line style \bar "dot" to create a single dot as a bar line?
newbies dumb Q - will the switch impact extant user files?
is there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 13. Dezember 2008 02:48:14 schrieb dem...@suffolk.lib.ny.us:
> On Fri, Dec 12, 2008, Reinhold Kainhofer said:
> > Should we change \bar "." to create a single
> > thick barline for reasons of consistency and instead add a new
> > bar line
On Fri, Dec 12, 2008 at 03:09:12PM -0800, Mark Polesky wrote:
> My goodness, Valentin, I would never have figured that out.
> Is this described in the docs somewhere? It should be.
Add it to LSR with the tag "docs" and whatever else you think it
needs.
Cheers,
- Graham
_
> Question to the other developers: Should we change \bar "." to
> create a single thick barline for reasons of consistency and instead
> add a new bar line style \bar "dot" to create a single dot as a bar
> line?
I don't object, but I've never seen a single thick barline in the
wild...
Wer
> Please let further suggestions be coming. :-)
No further suggestions. I've applied it to the git. Thanks! Please
provide proper entries for NEWS.tely and other documentation files,
together with a regression test (or extending an existing one).
Werner
26 matches
Mail list logo
