[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tips and Tricks on making Vim a good environment for Lilypond?
From: |
Ivan Kuznetsov |
Subject: |
Re: Tips and Tricks on making Vim a good environment for Lilypond? |
Date: |
Mon, 21 Jan 2019 18:58:08 -0600 |
Mason Hock <address@hidden> writes:
>
> I use vim for everything except large Lilypond projects that consist of
> multiple input files. The ability to click on an object in the score and
> jump to that place in the code, even if the file containing that code is
> not open, outweighs for me vim's advantages as a text editor, but I also
> have not spent much time trying to come up with an alternative solution
> in vim. How do you angle this.
Well, so far I have just used Lilypond
for solo guitar music, and duets including guitar,
so perhaps I have not begun to work on projects that
are considered large.
> I'd be interested to see one of your Makefiles.
They are no big deal, I am sure. An example:
###########################################
all: panfan-entire.pdf
wav: panfan-entire.wav
clean:
/bin/rm -f *.pdf *.wav *.midi
panfan-entire.pdf: \
panfan-entire.ly \
panfan-include.ly \
panfan-sec01.ly \
panfan-sec02.ly \
panfan-sec03.ly \
panfan-sec04.ly \
panfan-tempo-sec01.ly \
panfan-tempo-sec02.ly \
panfan-tempo-sec03.ly \
panfan-tempo-sec04.ly
lilypond panfan-entire.ly
panfan-entire.wav: panfan-entire.midi
timidity -A200 -Ow -o panfan-entire.wav panfan-entire.midi
###########################################
Makefile
Description: Binary data