2008/5/24 Graham Percival <[EMAIL PROTECTED]>:
> On Sat, 24 May 2008 16:21:06 +0200
> John Mandereau <[EMAIL PROTECTED]> wrote:
>> I'll have a look to see if I can fix it in a reasonnable time, but as
>> I don't promise anything for this, I added it to the tracker:
>> http://code.google.com/p/lily
On Sat, 24 May 2008 21:31:16 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> You wrote Sunday, May 11, 2008 10:35 PM
>
> > Any brilliant suggestions? I'm stuck. :|
>
> First, I'd give the full paths to the file that would be used by
> default during install, and say that's what they are.
On Sat, 24 May 2008 16:21:06 +0200
John Mandereau <[EMAIL PROTECTED]> wrote:
> On 2008/05/23, Graham Percival wrote:
> > On Fri, 23 May 2008 21:19:56 +0100
> > "Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> >
> > > Other commands are more selective. For example, text for
> > > ottava brackets can
Graham
I just came across this in my inbox and realised I hadn't replied to it.
Sorry.
You wrote Sunday, May 11, 2008 10:35 PM
Trevor, I modified LM 4.6.3 Other... a bit, but it's now a mess.
I didn't think that you'd introduced "GUB",
That's right, it hasn't been mentioned.
so I call
On Sat, 24 May 2008 15:59:13 +0200
John Mandereau <[EMAIL PROTECTED]> wrote:
> On 2008/05/24, Neil Puttock wrote:
>
> > Could there be something wrong with the patch? It's attached if you
> > want to have a look.
>
> The patch looks fine.
Oops, my fault. I applied the patch and compiled it, b
2008/5/24 Francisco Vila <[EMAIL PROTECTED]>:
> My Gcc version is 4.2.3 (standard in Ubuntu 8.04) and I compile well,
> send me a test file or whatever if you want to know if my output is
> correct.
Same here; I'm using exclusively a GCC-4.2.3 home-made LilyPond
(merging master and dev/rune), so
My Gcc version is 4.2.3 (standard in Ubuntu 8.04) and I compile well,
send me a test file or whatever if you want to know if my output is
correct.
2008/5/24 John Mandereau <[EMAIL PROTECTED]>:
> Hi,
>
> After the patch I sent last Sunday to make LilyPond work when compiled
> with GCC 4.3.0 x86, I
On 2008/05/23, Graham Percival wrote:
> On Fri, 23 May 2008 21:19:56 +0100
> "Trevor Daniels" <[EMAIL PROTECTED]> wrote:
>
> > Other commands are more selective. For example, text for
> > ottava brackets can only be entered as quoted text.
>
> I consider this a bug. I can see the difficulties f
On 2008/05/24, Neil Puttock wrote:
> > indicating-cross-staff-chords-with-arpeggio-bracket.ly
> That's weird; the new file is definitely in the patch I sent Graham,
> and I can see it's present in gitk.
It's present in your local branch, but not on git.sv.gnu.org (and thus
not in my local branch
Hi John,
2008/5/24 John Mandereau <[EMAIL PROTECTED]>:
> Hi Neil,
>
> It looks like you haven't added some input/lsr/*.snippet-list or some
> input/lsr/*.ly files to commit last time you used makelsr.py. I fixed
> it in a silly way, but you may want to update LSR again (and commit all
> necessary
Hi Neil,
It looks like you haven't added some input/lsr/*.snippet-list or some
input/lsr/*.ly files to commit last time you used makelsr.py. I fixed
it in a silly way, but you may want to update LSR again (and commit all
necessary files, i.e. input/lsr/*.ly and input/lsr/*.snippet-list) in
case y
On 2008/05/24, Trevor Daniels wrote:
> Valentin Villenave wrote Saturday, May 24, 2008 8:44 AM
> > 2008/5/24 Graham Percival <[EMAIL PROTECTED]>:
> >> This looks right to me, and since nobody has come up with any
> >> better names, let's go with bracketed/quoted/bare.
> >
> > bracketed might be con
Hi,
After the patch I sent last Sunday to make LilyPond work when compiled
with GCC 4.3.0 x86, I noticed that many formatting details were
completely screwed up (strange skyline spacing, overlapping staves,
irregular horizontal spacing). There are less formatting oddities when
compiling with GCC
Valentin Villenave wrote Saturday, May 24, 2008 8:44 AM
2008/5/24 Graham Percival <[EMAIL PROTECTED]>:
This looks right to me, and since nobody has come up with any
better names, let's go with bracketed/quoted/bare.
bracketed might be confusing with [bracketed text]]
or (bracketed text), I g
2008/5/24 Graham Percival <[EMAIL PROTECTED]>:
> This looks right to me, and since nobody has come up with any
> better names, let's go with bracketed/quoted/bare.
bracketed might be confusing with [bracketed text]]
I don't speak English, but I assume there's no such thing as "braced text"?
...
15 matches
Mail list logo
