On 2009-10-28, Patrick McCarty wrote:
> On 2009-10-28, Neil Puttock wrote:
> > 2009/10/20 Neil Puttock :
> > > 2009/10/20 Patrick McCarty :
> > >
> > >> This should be fixed now in latest git.
> > >
> > > Works for me.
> >
> > I guess I spoke a bit prematurely here, since the fix you pushed
> > al
On 10/28/09 4:39 PM, "Neil Puttock" wrote:
> 2009/10/28 Ian Hulin :
>> I managed to get set up and put the patch for Tracker 836 on as tracker
>> 141076.
>
> This issue doesn't exist; did you delete it after uploading?
>
>> Message:
>> ly/engraver-init.ly in not part of this patch and I didn
2009/10/28 Michael Käppler :
> Okay. I hadn't thought about this. Fixed now.
I only noticed it myself yesterday for reasons which should become
clear if you check out the attached PNG. ;)
Thanks for all the work you've done on this patch. I've just pushed
it to master, so we can move on to the
On 2009-10-28, Neil Puttock wrote:
> 2009/10/20 Neil Puttock :
> > 2009/10/20 Patrick McCarty :
> >
> >> This should be fixed now in latest git.
> >
> > Works for me.
>
> I guess I spoke a bit prematurely here, since the fix you pushed
> always loads aybabtu, even when font-defaults has been redef
Reviewers: Neil Puttock,
Description:
Tracker 836: Add facility to change output file-name for a \book block
or to set a suffix to prevent multiple files over-writing each other
during
a compilation.
This change allows user to to this via functions rather than having to
do
so by manipulating sem
2009/10/20 Neil Puttock :
> 2009/10/20 Patrick McCarty :
>
>> This should be fixed now in latest git.
>
> Works for me.
I guess I spoke a bit prematurely here, since the fix you pushed
always loads aybabtu, even when font-defaults has been redefined.
I've tried amending the code to allow switching
2009/10/26 Graham Percival :
> Could we get an entry in Documentation/changes.tely about the font
> switching? I guess we can't show an actual example of it working
> (unless we make the new font required for compiling lilypond), but it
> would be nice to have a bullet point about this, at least.
2009/10/28 Ian Hulin :
> I managed to get set up and put the patch for Tracker 836 on as tracker
> 141076.
This issue doesn't exist; did you delete it after uploading?
> Message:
> ly/engraver-init.ly in not part of this patch and I didn't change it.
You should apply your patch to master, then y
On Wed, 2009-10-28 at 21:54 +0100, Nicolas Sceaux wrote:
> Le 28 oct. 09 à 08:37, David Kastrup a écrit :
>
> > Carl Sorensen 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 mel
Le 28 oct. 09 à 08:37, David Kastrup a écrit :
Carl Sorensen 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 melisme can go on for lines. Do we have a way to discourage
breaks but not complete
I managed to get set up and put the patch for Tracker 836 on as tracker
141076.
However it looks like I had a bad mail address for this list in my
git-cl configuration.
Cheers,
Ian
--- Begin Message ---
Reviewers: ,
Message:
ly/engraver-init.ly in not part of this patch and I didn't change
On 10/27/09 7:05 PM, "Neil Puttock" wrote:
> 2009/10/27 Carl Sorensen :
>
>> The patch looks good to me. Neil?
>
> Not bad, Ian, but you need to keep an eye on trailing spaces and indentation.
To try to save you time, I'm going to explain the indentation issues.
>
> +PARSER->lexe
Hi Neil,
Looks fine.
Good.
Sorry to be a pain, but there's one more thing I missed: all the
regtests which rely on default settings need to reset the default
paper size, otherwise the line-width setting from the lilypond-book
preamble messes up the spacing.
Okay. I hadn't thought about t
Carl Sorensen 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 melisme can go on for lines. Do we have a way to discourage
breaks but not completely disallow them?
--
David Kastrup
> 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?
Hmm. How often does this happen in real scores? I think that in most
circumstances good (and thus flexible) spacing is much more important,
and a user should loc
15 matches
Mail list logo
