Graham Percival wrote:
The problem is that, AFAIK, there is no difference in the file format
between include-files and non-include files. (apart from the lack
of a \score{} section in include files)
I don't see why that is a "problem".
You could argue the same with .c and .h files or with .ps and
Wouldn't it be a good idea, before 2.0 to change the file extension
convensions so that you could distinguish files to be compiled from
files to be included?
It would be nice to be able to do something like "lilypond *.ly" without
getting errors about include-files.
(.lyi would be a natural exte
On Sun, 14 Sep 2003 13:34:46 +0200
Rune Zedeler <[EMAIL PROTECTED]> wrote:
> Wouldn't it be a good idea, before 2.0 to change the file extension
> convensions so that you could distinguish files to be compiled from
> files to be included?
The problem is that, AFAIK, there is no difference in the f
[EMAIL PROTECTED] writes:
> >
> > c8[ c4 c8]
> >
> > should produce
> >
> > === | ===|
> > | | |
> > x x x
> >
> >
> > (which is a bit silly, but logical)
>
> I agree, but do you think the steam of the 1/4 note should have the
> same direction of the other notes? li
* Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> [EMAIL PROTECTED] writes:
> > Of course this solved my problem, but on a second thought, shouldn't
> > the behavior be changed when unbeamed notes like 1/4 is (accidentally
> > or not) put inside a beamed group like c4[ d'8 e f g] ? Sure lilypond
>
[EMAIL PROTECTED] writes:
> Of course this solved my problem, but on a second thought, shouldn't
> the behavior be changed when unbeamed notes like 1/4 is (accidentally
> or not) put inside a beamed group like c4[ d'8 e f g] ? Sure lilypond
> tells "warning: stem doesn't fit in beam:" but maybe th
* Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> > There is a bug in 1.9.x with beams across barlines (it was working in
> > 1.8 for sure). The note _before_ the beamed group gets a stem with the
> > same size and direction of the stem of the beamed notes, as if it were
> > part of the group. Here i
Wouldn't it be a good idea, before 2.0 to change the file extension
convensions so that you could distinguish files to be compiled from
files to be included?
It would be nice to be able to do something like "lilypond *.ly" without
getting errors about include-files.
(.lyi would be a natural extensi
