Heikki Johannes Junes | 14 May 2003 23:07
Picon
Picon

Extensions .sly and .fly deprecated?


I can see that lilypond-mode.el has still some relics of handling files
whose extension is .sly or .fly instead of .ly. I figured out that these
old extensions were used so that there may not be a \score-field.

I ended up to this problem when had an idea to put in work the compiling of
some region in a lilypond-code. Maybe it is difficult to make such
region-compiling facility and there is even no actual need for compiling
only part of a score (which may not contain a score-field).

Are this extensions still used in some form?

And, is there some command with which one can compile a region which does not
contain a score-field?

Or, should this Command-on-Region in Emacs be taken away, i.e., would
there be need for such facility?

Greetings,

  Heikki
Han-Wen Nienhuys | 15 May 2003 00:29
Picon

Extensions .sly and .fly deprecated?

hjunes <at> cc.hut.fi writes:
> 
> I can see that lilypond-mode.el has still some relics of handling files
> whose extension is .sly or .fly instead of .ly. I figured out that these
> old extensions were used so that there may not be a \score-field.
> 
> I ended up to this problem when had an idea to put in work the compiling of
> some region in a lilypond-code. Maybe it is difficult to make such
> region-compiling facility and there is even no actual need for compiling
> only part of a score (which may not contain a score-field).
> 
> Are this extensions still used in some form?
> 
> And, is there some command with which one can compile a region which does not
> contain a score-field?
> 
> Or, should this Command-on-Region in Emacs be taken away, i.e., would
> there be need for such facility?

Command-on-Region is a little silly for Lilypond code, since
you would typically run Lily on regions in time similar to
skipTypesetting (at least, that's  what I'd suppose.)

--
Han-Wen Nienhuys   |   hanwen <at> cs.uu.nl   |   http://www.cs.uu.nl/~hanwen 
Heikki Johannes Junes | 15 May 2003 01:53
Picon
Picon

Re: Extensions .sly and .fly deprecated?

On Thu, 15 May 2003, Han-Wen Nienhuys wrote:

> hjunes <at> cc.hut.fi writes:
>
> > Or, should this Command-on-Region in Emacs be taken away, i.e., would
> > there be need for such facility?
>
> Command-on-Region is a little silly for Lilypond code, since
> you would typically run Lily on regions in time similar to
> skipTypesetting (at least, that's  what I'd suppose.)
>

Oh, I see. That sounds reasonable. Compiling is faster if one skips some
typesetting.

There might be one possibility to have "Command on Region". After saving
the entire buffer to "emacs-lily.ly":

  - apply skipTypesetting in the very beginning of each score:

    A) by converting each
         \score { ... }
       to
         \score { skipTypesetting ... }

  - stop skipTypesetting inside each \notes { ... } of the region:

    B) by converting
         \notes { ... <MARK_BEGIN> ... }
         \notes { ... }
(Continue reading)

Jan Nieuwenhuizen | 15 May 2003 09:57
Picon
Gravatar

Re: Extensions .sly and .fly deprecated?

Heikki Johannes Junes <hjunes <at> cc.hut.fi> writes:

> Or, should this Command-on-Region in Emacs be taken away, i.e., would
> there be need for such facility?

Command-on-Region is a bit flaked, but very useful for having a quick
'look' at music in email messages.

Jan.

--

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org
Han-Wen Nienhuys | 15 May 2003 14:03
Picon

Re: layout tweaks


[follow-up to lilypond-devel]

rutger <at> cs.vu.nl writes:
> I also feel that more support for control of page breaking
> would be very helpful. Up to now, I came away with twiddling
> point sizes, inter-system distances, margin sizes etc, but
> that feels all very ad-hoc.
> It *is* very important to have control over page breaks, e.g.
> for orchestral parts. Usually, a page break should coincide
> with a rest of sufficient length to turn the page (I know string
> players have other options, but I always feel it is a bit weird
> if half of the group stops playing to turn the page).
> This is much more important than equally filled or equally
> spaced pages!

You make a valid point, and I agree with you that control over page
breaking is important for orchestral parts. Unfortunately, a
full-blown solution also implies that Lilypond must keep track of how
large pages are vertically, how much space titles take up, and the
size of preceding movements. It is completely incompatible with the
current ly2dvi approach, and would be a major undertaking to get
correct.

The most feasible idea I can think of right now, is to have a
page-break forcing mechanism, (similar to the
input/test/between-systems.ly), where TeX pagebreaks are implemented
such that they will never lead to orphaned systems.

(I remember twiddling with page breaks, and having the problem that
(Continue reading)

Han-Wen Nienhuys | 15 May 2003 17:20
Picon

CVS fails

bobroff <at> centrum.is writes:
> I'm still getting a 'make' error with CVS.  I went so far as to do a
> fresh checkout and it still fails.  ChangLog version is 1.884.  Distro
> is RedHat 9.0.  Here is the end of the console output.

Please keep discussions  on compiling 1.7 on the devel list.

(1.7 is in development. It breaks sometimes - especially if I'm busy
   with it.).

--

-- 

Han-Wen Nienhuys   |   hanwen <at> cs.uu.nl   |   http://www.cs.uu.nl/~hanwen 
David Bobroff | 15 May 2003 19:17
Picon
Picon

CVS failures and posts


> Please keep discussions  on compiling 1.7 on the devel list.

Will do.

> (1.7 is in development. It breaks sometimes - especially if I'm busy
>    with it.).

Understood.  One question: Do you want feedback concerning build fails
as I was doing (only on this list rather than the user list)?  I would
assume so.  I ask so that I don't clutter this list with unnecessary
posts.

By the way, ChangLog version 1.885 compiles just fine now on RedHat 9.0.

-David Bobroff
Jan Nieuwenhuizen | 15 May 2003 21:21
Picon
Gravatar

Re: CVS failures and posts

David Bobroff <bobroff <at> centrum.is> writes:

> Understood.  One question: Do you want feedback concerning build fails

Yes, please do.

Jan.

--

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org
David Bobroff | 15 May 2003 23:50
Picon
Picon

CVS ChangLog 1.888 fails

CVS ChangLog version 1.888 fails on RedHat 9.0.  I did 'make clean' and
'make distclean' just to be sure.

Should I send a log file or is the end of the console output (see below)
sufficient?

-David Bobroff

make[2]: Entering directory `/home/lily-cvs/lilypond/Documentation/user'
chmod a+w out/lilypond.nexi
chmod: failed to get attributes of `out/lilypond.nexi': No such file or
directory
make[2]: [out/lilypond.nexi] Error 1 (ignored)
/usr/bin/python ../../scripts/lilypond-book.py -I
/home/lily-cvs/lilypond/Documentation/user -I ./out -I../../input -I
../../input/tricks/ -I ../../input/regression/ -I ../../input/test/ -I
../../input/tutorial/ -I /home/lily-cvs/lilypond/mf/out/  -I
/home/lily-cvs/lilypond/mf/out/ --dependencies --outdir=./out
--format=texi --no-lily --extra-options '-e "(ly:set-option (quote
internal-type-checking) #t)"' -o lilypond.nexi lilypond.tely
lilypond-book (GNU LilyPond) 1.7.18
Reading `/home/lily-cvs/lilypond/Documentation/user/lilypond.tely'
Reading `/home/lily-cvs/lilypond/Documentation/user/dedication.itely'
Reading `/home/lily-cvs/lilypond/Documentation/user/macros.itexi'
Reading `/home/lily-cvs/lilypond/Documentation/user/preface.itely'
Reading `/home/lily-cvs/lilypond/Documentation/user/introduction.itely'
Reading `/home/lily-cvs/lilypond/Documentation/user/tutorial.itely'
Reading `/home/lily-cvs/lilypond/Documentation/user/refman.itely'
Reading `/home/lily-cvs/lilypond/Documentation/user/literature.itely'
Reading `/home/lily-cvs/lilypond/Documentation/user/internals.itely'
(Continue reading)

Han-Wen Nienhuys | 16 May 2003 00:49
Picon

CVS failures and posts

bobroff <at> centrum.is writes:
> 
> > Please keep discussions  on compiling 1.7 on the devel list.
> 
> Will do.
> 
> 
> > (1.7 is in development. It breaks sometimes - especially if I'm busy
> >    with it.).
> 
> Understood.  One question: Do you want feedback concerning build fails
> as I was doing (only on this list rather than the user list)?  I would

Yes, but not for documentation build failures.

--

-- 

Han-Wen Nienhuys   |   hanwen <at> cs.uu.nl   |   http://www.cs.uu.nl/~hanwen 

Gmane