I want to open up the conversation about merging rests again (see bug
1228 http://code.google.com/p/lilypond/issues/detail?id=1228). Below
is a first go at a scheme based engraver. It doesn't kill any grobs so
the chance of segfaults is lower. Do overlapping grobs have any other
unintended conseque
Thomas Morley writes:
> I didn't manage to fix:
> filtering-parts-from-the-command-line.ly
You just did not try hard enough. It was a really obscure bug in the
lexer. I'll commit a fix to staging once make check goes through.
I think I need a beer.
--
David Kastrup
___
David,
On Tue, Feb 21, 2012 at 11:10 AM, David Kastrup wrote:
>
> Sorry for the unnecessary work caused by not thinking about this
> sufficiently from your point of view. And sorry for the "it does not
> take a genius" tone of my previous message that was uncalled for, stupid
> and offensive.
David Nalesnik writes:
> On Tue, Feb 21, 2012 at 10:37 AM, David Kastrup wrote:
>
> So please check with the _current_ convert-ly. It has an option
>
> -t, --to=VERSION convert to VERSION [default: 2.15.31]
>
> for telling it at which version to stop. You don't
David,
On Tue, Feb 21, 2012 at 10:37 AM, David Kastrup wrote:
> David Kastrup writes:
>
> > David Nalesnik writes:
> >
> >> David,
> >>
> >> On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup wrote:
> >>
> >> Uh, convertrules.py converts interval-translate to coord-translate
> >> so
> >>
Thomas Morley writes:
> Hi David,
>
> 2012/2/20 David Kastrup :
>> Thomas Morley writes:
>>
>>> Hi David, Phil,
>>>
>>> I'll be offline for two days, perhaps three. (Visiting a funeral, ~800
>>> km away from my home)
>>> May I ask you to continue the updating work?
>>
>> I'm just going to take a
David Kastrup writes:
> David Nalesnik writes:
>
>> David,
>>
>> On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup wrote:
>>
>> Uh, convertrules.py converts interval-translate to coord-translate
>> so
>> where is the actual problem?
>>
>>
>>
>> Certainly coord-translate is th
David Nalesnik writes:
> David,
>
> On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup wrote:
>
> Uh, convertrules.py converts interval-translate to coord-translate
> so
> where is the actual problem?
>
>
>
> Certainly coord-translate is the natural fix (thank you!), but when I
David,
On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup wrote:
>
> Uh, convertrules.py converts interval-translate to coord-translate so
> where is the actual problem?
>
>
Certainly coord-translate is the natural fix (thank you!), but when I run
convert-ly and the snippet is updated to 2.14.0, this
David Nalesnik writes:
> David,
>
> On Mon, Feb 20, 2012 at 5:01 AM, David Kastrup wrote:
>
> Thomas Morley writes:
>
> > 2012/2/19 David Kastrup :
>
>
> > Furthermore, I realized, that there seems to be no conversion
> rule for
> > the following 2.12.3-defini
David,
On Mon, Feb 20, 2012 at 5:01 AM, David Kastrup wrote:
> Thomas Morley writes:
>
> > 2012/2/19 David Kastrup :
>
> > Furthermore, I realized, that there seems to be no conversion rule for
> > the following 2.12.3-definitions:
> >
> > From 2.12.3: \scm\lily-library.scm
> >
> >(define
Nils writes:
> Hello list,
>
> since lilypond-book makes an image of each staff-system and places
> them as normale TeX lines all spacing between the systems vanishes,
> which looks ugly.
>
> This was discusses already here:
> http://old.nabble.com/system-system-spacing-in-lilypond-book-file-td31
On Tue, Feb 21, 2012 at 12:43 AM, Jan-Peter Voigt wrote:
> On 15.02.2012 20:14, Ralph Palmer wrote:
>
>> ...
>>
>>
>> I would like to :
>> 1) have LilyPond put as many complete scores as possible on each page;
>> 2) have LilyPond *not* make a page break within a score, if possible; and
>> 3) have
Hello list,
since lilypond-book makes an image of each staff-system and places them as
normale TeX lines all spacing between the systems vanishes, which looks ugly.
This was discusses already here:
http://old.nabble.com/system-system-spacing-in-lilypond-book-file-td31930124.html
and the solutio
On 15.02.2012 20:14, Ralph Palmer wrote:
...
I would like to :
1) have LilyPond put as many complete scores as possible on each page;
2) have LilyPond *not* make a page break within a score, if possible; and
3) have LilyPond allow a page break within a score, if there's no way
that score can fi
Hello Ralph, hello Harm,
I tested the following, wich seems to allow page-breaking as expected.
The page-break-permission is, although dedicated to score, found in the
global context above the current actual musical score. Setting
(overriding) it affects all following scores and markups. (ques
lilypond-7 wrote:
>
> I can't seem to find the right search terms to reveal how
> to extend bar lines across ungrouped staves. I'd like both
> the bar line and the final barline to extend across both
> staves in the two-bar example below.
>
> \score {
> <<
> \relative c' {
> e1
>
17 matches
Mail list logo
