Re: lilypond emacs mode?

2002-09-08 Thread Atte Andre Jensen

On 6 Sep 2002, superk wrote:

> however, i'm used to using emacs mode such as XML/SGML in a DocBook
> environment. is there such a mode i could use for lilypond and how could
> i install/run it please?

What you need should be included with lily and already on your computer.
Since you don't write what os you're using I don't know where the files
exactly would be. Anyways: I have these four files in my .elisp folder:

/home/atte/.elisp/lilypond-font-lock.el
/home/atte/.elisp/lilypond-indent.el
/home/atte/.elisp/lilypond-init.el
/home/atte/.elisp/lilypond-mode.el

And the following two lines in my .emacs

(load-library "lilypond-mode.el")
(add-to-list 'auto-mode-alist '("\\.ly$" . LilyPond-mode))

You also need gv installed, but you prob already use that...

Hope this helps

-- 
peace, love & harmony
Atte



___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user



Re: font (?) help request

2002-09-08 Thread Jan Nieuwenhuizen

"Alex Langley" <[EMAIL PROTECTED]> writes:

> I have searched in the archives and manual, I must be missing
> something when it comes to lyric and notehead fonts.  Here's
> the situation:
>
> cygwin lilypond 1.6.0 ...I can get everything but the lyrics to
> show up.

Try using ly2dvi -P (not -p), and use the postscript output, or
install tetex-base and tetex-extra too.

> Any help will be much appreciated!

You may also see this thread:

http://mail.gnu.org/pipermail/lilypond-user/2002-August/002376.html


If it doesn't work, please post your ly2dvi --verbose output.

Good luck,
Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org



___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user



Re: (no subject)

2002-09-08 Thread Jan Nieuwenhuizen

Colin Cotter <[EMAIL PROTECTED]> writes:

> Lilypond book is producing lilypond-123123.midi and 
> lilypond-123123.ly but not a tex file.

> Any suggestions?

Maybe you need to add a \paper block to the lilypond snippet in your
source?  Hard to tell without seeing the source.

Jan.
-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org



___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user



Problems with lilypond-book

2002-09-08 Thread Colin Cotter

Hello,
I have reposted my question with the source attached. I hope that you can 
spot what I am doing wrong!

I am having a problem with lilypond-book. I use the command
lilypond-book gloworms-book.tex

followed by
latex gloworms-book.latex

I am including some lilypond music by using \lilypondfile 
and the error I am getting is something like lilypond-123123.tex not 
found. Lilypond book is producing lilypond-123123.midi and 
lilypond-123123.ly but not a tex file. 
Any suggestions?
Colin





___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user


\include "paper16.ly"
\include "english.ly"

\paper {
% standard settings are too big and wide for a book
indent = 1.0 \cm
linewidth = 15.0 \cm
}

\header {
title = "New Tunes"
}

% Sausage Sandwich
\score {
\notes 
\relative c''  {
\time 9/8
\key g \major
\repeat "volta" 2 {
b8 d, d b' d, c' d4 c8 b d, d d' d, d d' d, d b' d, d 
b' d, c' d4 c8 b d, d d' c d b a g  
}   
\repeat "volta" 2 {
fs4 e8 d a' a b d, c' b d, d d' d, d d' d, d 
fs4 e8 d a' a b d, c' b a g b e, c' d4.
}
}
\header {
opus = "Sausage Sandwich" 
}
\midi {
\tempo 8 = 200}
}


% Black Bathroom
\score {
\notes 
\relative c''  {
\time 2/2
\key g \major
\repeat "volta" 2 {
b4. b8~b a g a b d, c' d, d' d, c'4
b4. b8~b a g a
}   
\alternative {{b g a4 g d'8 c}{b g a4 g b8 a}}
\repeat "volta" 2 {
g e e4 g8 e a e b' e, d'4 b8 e, d'4 
g,8 e e4 g8 e a e 
}
\alternative{{b' e, cs'4 d b8 a}{b'8 e, cs'4 d d8 c}}
}
\header {
opus = "Black Bathroom"
}
\midi { \tempo 2 = 140}
}



gloworms_book.tex
Description: TeX document


Re: tab

2002-09-08 Thread David Raleigh Arnold

On Sat, 07 Sep 2002 10:38:30 Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > On Fri, 06 Sep 2002 20:56:54 Han-Wen Nienhuys wrote:
> > > [EMAIL PROTECTED] writes:
> > > > On Fri, 06 Sep 2002 17:54:27 Han-Wen Nienhuys wrote:
> > > > 
> > > > > Fingerings should be done more automatically anyway;
> > > > 
> > > > What does that mean?
> > > 
> > > I mean the formatting. The business of putting fingerings left, right,
> > > up and down of the notes should really be done by Lilypond-- that's
> > > why I don't like the idea of extra syntax for more manual formatting
> > > options.
> > 
> > You "should" do it so you see to it that it can't be
> > done until that day, which is not going to be soon,
> > that you can do it?  How does making lilypond less 
> > usable make it better?
> 
> It probably saves you some (maybe a lot) of typing when you can use ;4
> and \4 for left and right for the moment (as opposed to using
> #'extra-offset) , but when I do that, I lose the ability of of using ;
> and \ for other useful things, and --much more important-- it produces
> a compatibility headache.
> 
> Developing lilypond is hard enough when I only have to maintain
> compatibility with the ideas that I didn't realize were clumsy when I
> introduced them. Introducing or allowing things that seem clumsy at
> first sight seems unwise. I've done it in the past (cf. lyric
> alignment code, text markup, big parts of the ancient notation, etc.),
> but I've always regretted doing so, because at some point, I have to
> dive into that not-so-solid code to maintain it.

The hardest thing is the lack of ability to pass values to
the likes of #'extra-offset, which makes the user have to
have a different definition for each value.  Of course I can
do that now, but I'd rather do it in lilypond.  Is it particularly
impossible to adopt or adapt the LaTeX \newcommand to make
that possible?  With that you can pass multiple parameters to a
command (or combination of commands?)  I've been doing
a whopper of a lilypond-book
file and I'll miss \newcommand going back to ly2dvi.  If it
is usable now to any extent with ly2dvi then that
deserves to be documented.

As for fingering, the traditional thing is to have the finger
close to the notehead to which it refers, using whatever
whitespace is available, including that on the staff.
Engravers made many mistakes in
placement.  There is no prospect of doing it automatically
in the old way ever.  

The worst practice is to have a finger follow a note
in the notation.  Fortunately, that doesn't quite happen.
That's as bad as having an accidental follow a note.

Attached is an excerpt which demonstrates the necessity
of being able to move the finger indication close
to the notehead.  Works under 1.4.13.  The stem length
depends on the position on the staff now, (Cool!) so you
could move the finger indication closer to the 
notehead when the notehead is on or below the bottom
line of the staff and the stem is down, and the 
inverse of course.  That would eliminate the problem
in the vast majority of cases.

It is incorrect to tuck in rests that way when the
stem is down, because a simultaneous rest *must* precede the
stem.  I don't think engravers would have liked tucking
fingering much for a lower voice, but they would have *hated*
having the fingering all over the place the way it is
in the second page, and it would be centered nicely under
the note, and everyone will love it.

I see you changed \transpose to make it work like
\clef.  Good job!
 

Information is not knowledge.   Belief is not truth.
Indoctrination is not teaching.   Tradition is not evidence.
 David Raleigh Arnold   [EMAIL PROTECTED]


excerpt.lytex
Description: Binary data


Re: tab

2002-09-08 Thread Nicolas Sceaux


Sun, 8 Sep 2002 10:54:31 +, tu as dit : 

 > The hardest thing is the lack of ability to pass values to
 > the likes of #'extra-offset, which makes the user have to
 > have a different definition for each value.  Of course I can
 > do that now, but I'd rather do it in lilypond.  Is it particularly
 > impossible to adopt or adapt the LaTeX \newcommand to make
 > that possible?  With that you can pass multiple parameters to a
 > command (or combination of commands?)  I've been doing
 > a whopper of a lilypond-book
 > file and I'll miss \newcommand going back to ly2dvi.  If it
 > is usable now to any extent with ly2dvi then that
 > deserves to be documented.

Oh yes... a \newcommand equivalent, which can take arguments, 
is what I ever wanted to have in lilypond but was afraid to ask !

Nicolas


___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user



noteheads

2002-09-08 Thread olav gundersen

Hi!

I guess there must be a simple answer to a very simple question:

I want to use the noteheads-1slash and noteheads 2-slash instead of the 
ordinary noteheads. How do I do it?

Olav Gundersen


___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user



lyric syllable alignment problem

2002-09-08 Thread Nicolas Sceaux

Hi,

I am running lilypond 1.6.0 (debian unstable package)

While moving my pieces from 1.4.x to 1.6.x, I met some troubles.
The following example shows one of them: lyric syllables are not
aligned with the first note of beam groups, as they used to be.

\score {
\addlyrics
\context Staff <
\clef treble
\property Staff.autoBeaming = ##f
\property Staff.automaticMelismata = ##t
\notes { R1 c'8 [c' d'] [c' d' e'] [c' d'] c' d' e' r r2
 c'' c'' c'' c'' c'' c'' c'' c''
 c'' c''} >
\context Lyrics {\lyrics{ il la -- "bro, o" gi -- "ra il" guar -- do. }}

\paper { }
}

ly2dvi gives the following result:
http://nicolas.sceaux.free.fr/mutopia/test-pb.png

This behaviour is not systematic: when removing the first "R1",
syllable alignment is fine:
http://nicolas.sceaux.free.fr/mutopia/test-ok.png

Maybe I simply need to upgrade ?

Thanks in advance
Nicolas


___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user



Re: tab

2002-09-08 Thread Han-Wen Nienhuys

[EMAIL PROTECTED] writes:
> have a different definition for each value.  Of course I can
> do that now, but I'd rather do it in lilypond.  Is it particularly
> impossible to adopt or adapt the LaTeX \newcommand to make
> that possible?  With that you can pass multiple parameters to a
> command (or combination of commands?)  

It is absolutely out of the question. I am not, NEVER going to add
macros to lilypond. They make a complete mess of a nice language, and
if you don't believe me, go read LaTeX definition files, or try to
make heads and tails of what's written in chapter 20 of the TeX book.

I mean, if Donald Knuth manages to make a macro language into
something unintelligible, how do you suppose that a mere mortal like
me is ever going to make something clean out of it?

This decision is final. If you want parametrisation, learn Scheme.

--
Han-Wen Nienhuys   |   [EMAIL PROTECTED]   |   http://www.cs.uu.nl/~hanwen 


___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user



Re: How to produce a5 paper music

2002-09-08 Thread Laurie Savage

THanks, that looks complex but promising.

Cheers,

Laurie


On Sat, 7 Sep 2002, Marco Caliari wrote:

> Hi.
> 
> I think the simplest way to produce a5 paper music with Lilypond is:
> 
> include \paper{papersize="a4" orientation="landscape"} at the beginning of 
> your own file (say enea.ly);
> 
> include \paper{linewidth=280.0\mm} at the end of the score
> 
> ly2dvi
> 
> (view with xdvi -paper a4r enea.dvi)
> 
> dvips -ta4 -tlandscape enea.dvi
> 
> (my gv cannot view enea.ps but...)
> 
> pstops -pa4 "2:0L@.71(21cm,14.85cm)+1L@.71(21cm,0)" enea.ps enea.a5.ps  
> 
> my gv CAN view and print fine enea.a5.ps
> 
> Bye
> 
> 

-- 
Laurie Savage

Science @ Pascoe Vale Girls' College
03 9306 2544




___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user



Re: tab

2002-09-08 Thread David Raleigh Arnold

I apologize for my reply going astray.  Too much
hurry and not enough attention.

I saw that \newcommand had limitations of a peculiar
sort, that it was a mess, but I found it useful.
Did I do wrong to encourage them?

You don't have to tell me that LaTeX is a mess.
Part of it is that Knouth and Lamport know a
lot about typography but not nearly enough.

I don't believe that the mess was the result of
users trying to cut down on typing, I just don't.

I have a way of passing values now, fairly easily.
How are you hurt?


Information is not knowledge.   Belief is not truth.
Indoctrination is not teaching.   Tradition is not evidence.
 David Raleigh Arnold   [EMAIL PROTECTED]


___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user