Syntax Highlighting / lilypond.words.vim

2004-02-10 Thread Lyle Raymond
I spend most of my time editing in vi, so I cut and pasted Heikki Junes' 
lilypond.vim file into /syntax and inserted the appropriate text into 
filetype.vim, but now I apparently need to find lilypond.words.vim for the 
operation to be complete.  Where can I get it?



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


Re: Hi from new user + two quick questions

2004-02-10 Thread Ferenc Wagner
Lyle Raymond [EMAIL PROTECTED] writes:

 1.  I write for a jazz quartet.  I need to print
 individual parts, with the instrument name boldly
 displayed in the upper left of the page.  I can only find
 instructions regarding extracted orchestra parts.  How can
 I simply add the bold text in the corner?

See Titling layout in the manual.  poet or piece may
be easily tweaked to your liking by some LaTeX commands,
like eg.

poet = \\textbf{\\large Instrument}

-- 
Feri.


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


Re: Syntax Highlighting / lilypond.words.vim

2004-02-10 Thread Aaron
Hi Lyle,
I also use vim (gvim) for lilypond editing.
I am looking for others to who use vim to create some sort of group to 
work on an extented vim mode for lilypond.

I made a lilypond ftplugin for vim but it is now out of date and needs 
much debugging.

If you are interested or anyone else let me know.

also
The lilypond vim files that are missing I found by searching google and 
downloading them from the cvs.

Aaron





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


Re: Syntax Highlighting / lilypond.words.vim

2004-02-10 Thread Ferenc Wagner
Lyle Raymond [EMAIL PROTECTED] writes:

 I apparently need to find lilypond.words.vim for the
 operation to be complete.  Where can I get it?

It should be distributed with LilyPond.  You don't say which
package you installed so we can't help more; recent Debian
packages put it into /usr/share/doc/lilypond.  Tell at least
a version number so that somebody can send one to you.
-- 
Feri.


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


Re:

2004-02-10 Thread Jan Kohnert
Am Dienstag, 10. Februar 2004 02:34 schrieb Joe Krame:
 GNU LilyPond 1.6.6
 Now processing: `test.ly'
 Parsing...
 error: can't find `feta20.afm'
 Fonts have not been installed properly.  Aborting

Tex cannot find the fonts, which should have been installed in
$PREFIX/lilypond/fonts/afm/
(f.e. for SuSE rpm) or
$PREFIX/lilypond/$VERSION/fonts/afm/
What says kpsewhich feta20.afm ?

There are two scripts in the installation
lilypond.profile and lilypond.login
which sould be executed right at login time and set the correct paths for tex.

If this is for some reason not possible for you, try to add the correct font 
paths in /etc/texmf/texmf.cnf 
(BUT BE SURE YOU KNOW WHAT YOUR DOING!)
and than do a texhash.

 Thanks a lot for your help.

No Problem.

Regards Jan

-- 
OpenPGP public key available:
http://home.arcor.de/jan.kohnert/gnupg_publickey.asc

Key-Fingerprint:
BA8E 11D1 FE7C 9353 7276 5375 486E 9BED 2B03 DF29

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


Re: Font problems

2004-02-10 Thread Mats Bengtsson
Please always specify a subject on your emails. In these
days when there are lot of spam and virus emails, it was
just about to delete your email withour reading it.
Also, always tell what operating system you use (and what
distribution if it is a Linux systems) and how you installed
LilyPond (from source code or from some package).
Jan Kohnert wrote:
Am Dienstag, 10. Februar 2004 02:34 schrieb Joe Krame:

GNU LilyPond 1.6.6
Now processing: `test.ly'
Parsing...
error: can't find `feta20.afm'
Fonts have not been installed properly.  Aborting


Tex cannot find the fonts, which should have been installed in
$PREFIX/lilypond/fonts/afm/
(f.e. for SuSE rpm) or
$PREFIX/lilypond/$VERSION/fonts/afm/
What says kpsewhich feta20.afm ?
There are two scripts in the installation
lilypond.profile and lilypond.login
which sould be executed right at login time and set the correct paths for tex.
If this is for some reason not possible for you, try to add the correct font 
paths in /etc/texmf/texmf.cnf 
(BUT BE SURE YOU KNOW WHAT YOUR DOING!)
and than do a texhash.
This should never be necessary. If Jan knew more details about the
LilyPond installation, I'm sure he would never recommend this solution,
especially not since there are many more files than the .afm files that
have to be known to the TeX related programs.
   /Mats

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


Re: Font problems

2004-02-10 Thread Jan Kohnert
Am Dienstag, 10. Februar 2004 11:47 schrieb Mats Bengtsson:
 Please always specify a subject on your emails. In these
 days when there are lot of spam and virus emails, it was
 just about to delete your email withour reading it.

Just answered, didn't care for the not specified subject, Sorry :-(

  If this is for some reason not possible for you, try to add the correct
  font paths in /etc/texmf/texmf.cnf
  (BUT BE SURE YOU KNOW WHAT YOUR DOING!)
  and than do a texhash.

 This should never be necessary. If Jan knew more details about the
 LilyPond installation, I'm sure he would never recommend this solution,
 especially not since there are many more files than the .afm files that
 have to be known to the TeX related programs.

I added my /usr/lilypond/2.0.1/fonts to that file did a texhash and it worked, 
because for some reason my SuSE does not want to execute the scripts in 
/etc/profile.d ... :-(
Thatswhy the (possible) solution.
Surely not that elegant...

 /Mats

Regards Jan

-- 
OpenPGP public key available:
http://home.arcor.de/jan.kohnert/gnupg_publickey.asc

Key-Fingerprint:
BA8E 11D1 FE7C 9353 7276 5375 486E 9BED 2B03 DF29

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


Re: Font problems

2004-02-10 Thread Mats Bengtsson


Jan Kohnert wrote:
Am Dienstag, 10. Februar 2004 11:47 schrieb Mats Bengtsson:

Please always specify a subject on your emails. In these
days when there are lot of spam and virus emails, it was
just about to delete your email withour reading it.


Just answered, didn't care for the not specified subject, Sorry :-(
This was intended for Joe who sent the original question.

If this is for some reason not possible for you, try to add the correct
font paths in /etc/texmf/texmf.cnf
(BUT BE SURE YOU KNOW WHAT YOUR DOING!)
and than do a texhash.
This should never be necessary. If Jan knew more details about the
LilyPond installation, I'm sure he would never recommend this solution,
especially not since there are many more files than the .afm files that
have to be known to the TeX related programs.
I added my /usr/lilypond/2.0.1/fonts to that file did a texhash and it worked, 
because for some reason my SuSE does not want to execute the scripts in 
/etc/profile.d ... :-(
Thatswhy the (possible) solution.
Surely not that elegant...
Note that the lilypond program will work anyway, since it internally
does the same settings as are done in lilypond-profile.
What will not work if you have not sourced lilypond-profile is
- xdvi (your solution may solve that depending on what you changed in 
texmf.cnf)
- latex-book followed by latex and dvips (your solution does not solve
  these issues if you just set the font paths).

Regarding /etc/profile.d/, I know that Debian don't want packages to
set environment variables to avoid that several packages use the same
variable name. Their solution is to install all the necessary LilyPond
files in the original texmf/ directory of teTeX.
On RedHat, the following lines in /etc/profile, make sure that the
files in /etc/profile.d/ are sourced at startup.
for i in /etc/profile.d/*.sh ; do
if [ -r $i ]; then
. $i
fi
done
If you have the lilypond-profile.sh file in /etc/profile.d/ but it isn't
read for some reason, just add the line
. /etc/profile.d/lilypond-profile.sh
in your personal ~/.profile
That's much better than fiddling with the texmf.cnf file.
   /Mats

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


Re: lilypond-user faq, documentation, and small issues

2004-02-10 Thread Mats Bengtsson
(Please use a setting in your email program to break the lines at
regular intervals. When I edit the reply to your email, each of your
items appears on a single long line).
Todd M. Zimnoch wrote:
	I'm new to this group, and while I've found the archives, I haven't found a faq for this group.  Does one exist?
There have been long the discussions on the mailing list on the need for
a FAQ. In the end it boils down to that someone has to be responsible
and keep it up to date (which is a challenging task since LilyPond still
keeps evolving at a high rate). Also, the ambition is rather to improve
the problem and the ordinary documentation when a FAQ appears.
	I've waded through lilypond's documentation, mostly skimming, and one area I haven't found that I would personally find most useful is a straight listing of all properties.  e.g., a \header block has fields for piece, copyright, title, subtitle, subsubtitle, opus, poet, head, pagenumber, composer I don't imagine that's exhaustive, but I can't find an exhaustive list. (item 6.1.1 in lilypond's documentation comes close)  Staves have their own list of properties I'd like to know more about, e.g. instr, instrument.  Have I missed a resource or read too fast?
The list of \header fields is documented in
http://lilypond.org/doc/v2.0/Documentation/user/out-www/lilypond/Invoking-lilypond.html#Invoking%20lilypond
For all other properties, you can find complete lists in the on-line
manual if you click on Program reference. Lists for each kind of
context are found under Translation - Contexts and lists for each
kind of graphical object under Backend - All layout objects:.
However, the easiest way to navigate to such a list is often to follow
the links under See also at the bottom of the page in the user manual.
Also, one great source of information and examples is the Tips and
Tricks document as well as the Regression test document on
lilypond.org.
	My more immediate problems concern rehearsal marks and large scores with separate parts printing.  Is there a way to set or define rehearsal marks so they can be easily included with a \notes block?  I'm not enjoying editting every \notes block to place rehearsal marks on every part and I'd like a way to guarantee that the rehearsal marks are in exactly the same location for every part.  :/
Have you found http://www.mutopiaproject.org/ yet? Here you will find
lots of larger examples of using LilyPond (in the advanced search page
you can specify examples that match your own LilyPond version).
There are also a couple of examples in your own LilyPond installation,
typically in /usr/share/doc/lilypond/*/input/mutopia/.
In many of these examples, you'll find something like
global = \notes{ \skip 1*13 \mark A \skip 1*25 \mark B \bar || }
which can be used both in a full score and in a separate part using
\score{ % Full score
  \new StaffGroup 
\new Staff  \global \flute 
\new Staff {\oboe}
...
  
}
\score{ % Oboe part
  \new Staff  \global \oboe 
}


	Also, if the rehearsal mark appears at the begining of a staff it prints over and behind the clef directly on top of the measure number (easy-to-miss and hard-to-read) rather than above the key signature (standard for sheet music I've played).  How can I move it?
You can find some recent discussions on this topic on the mailing list
archives. I'm not sure what the best solution is for the moment.
   /Mats

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


dvipdfm - debian sarge - first install

2004-02-10 Thread smacnay
Hi,

I just installed lilypond and find it awesome.  I am putting small
snippets of melody in a latex doc and have had no troubles.  I get a
great .dvi and .ps file using 'lilypond-book --outdir=/tmp file.tex  cd /tmp  
latex file.latex  dvips file.dvi

However, if I try to 'dvipdfm file.dvi' I get errors and see no stems
on the notes.  I see error messages like this:

Unrecognized special ignored
Current input buffer is --lyscale1.405839  0.0650 0.0650 2. 1.2250
0.11...
--

and there are as many as there are notes.

ps2pdf does work.

Is this a font issue or a dvipdfm issue?  Thanks for any help.

Yours,

Sterling


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


dvipdfm results in no note stems

2004-02-10 Thread smacnay
Hi,

I am just stating to use lilypond on a Debian Sarge system.  Fresh
install of lilypond in the past few days.  I have been inserting small
sections on music in LaTeX files and using 'lilypond-book --outdir=/tmp
file.tex  cd /tmp  latex file.latex  dvips -Ppdf -u +lilypond.map
file.dvi  dvipdfm file.dvi'.

On the last command, I get errors like:

Unrecognized special ignored
Current input buffer is --lyscale1.405839  0.0650 0.0650 3. 0.2250
0.11...
--

one of these for each note stem that is missing.  There also seemed to
be a processing error on an imbedded eps file in the same LaTeX doc but
that was ignored as well.

I do find that ps2pdf does work in making a pdf file.  Any help on this
would be greatly appreciated.

If this is a duplicate message, I apologize.  I sent an earlier message
before subscribing to the list and am not sure if it made it in or not.

Great program!

Sterling MacNay


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


Problem with MIDI generation with 2.1.18

2004-02-10 Thread darius
Hi !

I upgraded to cygwin 2.1.18 yesterday, and experienced two problems:

-  \autochange does not seem to work as well as it used to be.
I guess I did something wrong. Here is my PianoStaff:

solo = \context PianoStaff = solo 
\property Staff.midiInstrument=vibraphone
\context Staff=up { 
   \property Staff.midiInstrument=vibraphone
\context Voice=foo{
   \notes { \time 4/4  \key b \minor }
\voiceOne
\HighSoloNotes
}
}
\context Staff=down {
\property Staff.midiInstrument=vibraphone
 \notes { \time 4/4  \key b \minor }
\clef bass
\autochange \context Voice = bar {\LowSoloNotes}
}




- MIDI file generation crashes with a stack trace (the log is given below)
  I tried to simplify a number of things, assuming that this might be due
  to excessively complex data structure, but it did not help. 

  This raises a related question about Lilypond's internals: 
  when are variables expanded ? when I write:

a = \notes {a b c d e f }

b = \notes { \a \a \a }

  are the a's in b expanded when declaring b, or when actually using b ?

Cheers,

Darius/.

lilypond (GNU LilyPond) 2.1.18
Opening pipe `/usr/bin/lilypond-bin --version '
Opening pipe `kpsexpand \$TEXMF'
Opening pipe `kpsewhich -expand-path=\$T1FONTS'
Invoking `/usr/bin/lilypond-bin  -I /cygdrive/z/concerto -I /cygdrive/z/concerto 
-I /cygdrive/z/concerto --no-paper --verbose Ostinato'
lilypond_datadir: `/usr/share/lilypond'
local_lilypond_datadir: `/usr/share/lilypond/2.1.18'
localedir: `/usr/share/locale'
LILYPONDPREFIX: `'

[/usr/share/lilypond/2.1.18/scm/define-music-types.scm][/usr/share/lilypond/2.1.
18/scm/output-lib.scm][/usr/share/lilypond/2.1.18/scm/c++.scm]
[/usr/share/lilypond/2.1.18/scm/chord-ignatzek-names.scm][/usr/share/lilypond/2.
1.18/scm/chord-entry.scm][/usr/share/lilypond/2.1.18/scm/chord-generic-names.
scm][/usr/share/lilypond/2.1.18/scm/molecule.scm][/usr/share/lilypond/2.1.
18/scm/new-markup.scm][/usr/share/lilypond/2.1.18/scm/bass-figure.scm]
[/usr/share/lilypond/2.1.18/scm/music-functions.scm][/usr/share/lilypond/2.1.
18/scm/part-combiner.scm][/usr/share/lilypond/2.1.
18/scm/define-music-properties.scm][/usr/share/lilypond/2.1.18/scm/auto-beam.
scm][/usr/share/lilypond/2.1.18/scm/chord-name.scm][/usr/share/lilypond/2.1.
18/scm/define-translator-properties.scm][/usr/share/lilypond/2.1.
18/scm/translation-functions.scm][/usr/share/lilypond/2.1.18/scm/script.scm]
[/usr/share/lilypond/2.1.18/scm/drums.scm][/usr/share/lilypond/2.1.18/scm/midi.
scm][/usr/share/lilypond/2.1.18/scm/beam.scm][/usr/share/lilypond/2.1.
18/scm/clef
Now processing: `Ostinato.ly'
Parsing...[/usr/share/lilypond/2.1.18/ly/init.ly[/usr/share/lilypond/2.1.
18/ly/declarations-init.ly[/usr/share/lilypond/2.1.18/ly/nederlands.ly]
[/usr/share/lilypond/2.1.18/ly/chord-modifiers-init.ly][/usr/share/lilypond/2.1.
18/ly/script-init.ly][/usr/share/lilypond/2.1.18/ly/scale-definitions-init.ly]
[/usr/share/lilypond/2.1.18/ly/grace-init.ly][/usr/share/lilypond/2.1.
18/ly/midi-init.ly[/usr/share/lilypond/2.1.18/ly/performer-init.ly]]
[/usr/share/lilypond/2.1.18/ly/engraver-init.ly][/usr/share/lilypond/2.1.
18/ly/dynamic-scripts-init.ly][/usr/share/lilypond/2.1.18/ly/spanners-init.ly]
[/usr/share/lilypond/2.1.18/ly/property-init.ly]][/cygdrive/z/concerto/Ostinato.
ly[/usr/share/lilypond/2.1.18/fonts/afm/feta20.afm][/usr/share/lilypond/2.1.
18/fonts/tfm/feta20.tfm]Interpreting music...elapsed time: 0.42 seconds.scm]
[/usr/share/lilypond/2.1.18/scm/slur.scm][/usr/share/lilypond/2.1.18/scm/font.
scm][/usr/share/lilypond/2.1.18/scm/define-grob-properties.scm]
[/usr/share/lilypond/2.1.18/scm/define-grobs.scm][/usr/share/lilypond/2.1.
18/scm/define-grob-interfaces.scm][/usr/share/lilypond/2.1.18/scm/paper.scm]
Backtrace:
In /usr/share/lilypond/2.1.18/scm/part-combiner.scm:
 568:  981* [generate-split-list ((# #) (# #) (# #) (# #) ...)]
 553:  982  (if (null? event-list) (quote ()) ...)
  ...
 567:  983  [cons (#Mom 271/2 . -1) ...
 568:  984*  [generate-split-list ((# #) (# #) (# #) (# #) ...)]
 553:  985   (if (null? event-list) (quote ()) ...)
   ...
 567:  986   [cons (#Mom 136 . 1) ...
 568:  987*   [generate-split-list ((# #) (# #) (# #) (# #) ...)]
 553:  988(if (null? event-list) (quote ()) ...)
...
 567:  989[cons (#Mom 545/4 . 1) ...
 568:  990*[generate-split-list ((# #) (# #) (# #) (# #) ...)]
 553:  991 (if (null? event-list) (quote ()) ...)
 555:  992 (let* (# # # #) (if # # #))
 558:  993*[filter #procedure #f (x) (#Music NoteEvent)]
In /usr/share/guile/1.6/srfi/srfi-1.scm:
 743:  994 (letrec ((filiter (lambda # #))) (filiter pred list (quote (
 ...
 746:  995 [filiter #procedure #f (x) () ...
 747:  996* (cond ((pred (car rest)) (cons (car rest) result)) (#t result))
 747:  997* [#procedure #f (x) #Music NoteEvent]
In