Re: Multiple parts with multiple verses for each part.
Hello, On 2 January 2012 02:17, Widget wid...@pcug.org.au wrote: Hi I’m not-quite-a-beginner with Lilypond trying to engrave a couple of Christmas carols in three and four parts. The complication is that I would like to put the verses one after another for each part, rather than have a single line of text. The only example of something like it that I’ve found is http://www.mutopiaproject.org/cgibin/make-table.cgi?searchingfor=all+my+heart though the code is rather complex. My question: is there a simpler example I can try and dismantle to see how to include multiple verses for each part? It's all in here http://lilypond.org/doc/v2.14/Documentation/notation/stanzas Regards -- -- James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
syntax highlighting in the doc, call for testers
Hi LilyPonders,
I'm following Graham's suggestion[0] and I'm asking here if you could
please test the attached lilypond language file for source-highlight.
There's an issue on the tracker[1] about syntax highlighting in the doc.
The first step to make it happen is writing a language file for a third
party package called source-highlight[2]. Before submitting it to
source-highlight developers I'd appreciate some feedback from you. Not
much about color scheme (I'm trying to follow Frescobaldi highlighting
as much as possible).. what I really need is being sure that the regexp
work fine in real files.
The files I've tested so far seem to work fine now (with this last
version I'm attaching), but I may have missed something.
On Linux you just need to install the source-highlight package.
On Windows you may want to try these binaries[3]. It's v1.2.1 while I'm
using v3.1.5, so I don't guarantee it will work.
Once you have source-highlight installed, place the attached files in a
directory, open the terminal and change to that directory. Then launch
the following command:
source-highlight -s lilypond.lang --style-file=lilypond.style -i test.ly
-o test.html
NOTE: input files can be anywhere, but lilypond.lang, lilypond.style and
lang.map must be in the current working directory (i.e. where you launch
the command).
You can test it using your files or Mutopia files (better if v2.14, see
advanced search of Mutopia).
I'll send the files to source-highlight developers next Sunday.
If you have any comment/improvement let me know.
Thanks,
Federico
[0] http://lists.gnu.org/archive/html/lilypond-devel/2011-12/msg00722.html
[1] http://code.google.com/p/lilypond/issues/detail?id=1005
[2] http://www.gnu.org/software/src-highlite/
[3] http://gnuwin32.sourceforge.net/packages/source-highlight.htm
java = java.lang
moc = cpp.lang
cpp = cpp.lang
c = c.lang
C = cpp.lang
cc = cpp.lang
cs = csharp.lang
csharp = csharp.lang
h = cpp.lang
hh = cpp.lang
H = cpp.lang
hpp = cpp.lang
javascript = javascript.lang
js = javascript.lang
prolog = prolog.lang
pl = prolog.lang
perl = perl.lang
pm = perl.lang
php3 = php.lang
php4 = php.lang
php5 = php.lang
php = php.lang
ctp = php.lang
protobuf = proto.lang
proto = proto.lang
python = python.lang
py = python.lang
ruby = ruby.lang
rb = ruby.lang
flex = flex.lang
lex = flex.lang
l = flex.lang
ll = flex.lang
bison = bison.lang
yacc = bison.lang
y = bison.lang
yy = bison.lang
changelog = changelog.lang
lua = lua.lang
ml = caml.lang
caml = caml.lang
mli = caml.lang
sml = sml.lang
sig = sml.lang
syslog = log.lang
log = log.lang
pas = pascal.lang
pascal = pascal.lang
fortran = fortran.lang
free-fortran = fortran.lang
fixed-fortran = fixed-fortran.lang
html = html.lang
htm = html.lang
tex = latex.lang
latex = latex.lang
cls = latex.lang
sty = latex.lang
dtx = latex.lang
lgt = logtalk.lang
logtalk = logtalk.lang
diff = diff.lang
patch = diff.lang
lang = langdef.lang
langdef = langdef.lang
outlang = outlang.lang
style = style.lang
ps = postscript.lang
eps = postscript.lang
postscript = postscript.lang
kcfg = xml.lang
ui = xml.lang
kdevelop = xml.lang
rc = xml.lang
docbook = xml.lang
kidl = xml.lang
xml = xml.lang
xhtml = xml.lang
bash = sh.lang
sh = sh.lang
csh = sh.lang
ksh = sh.lang
tcsh = sh.lang
shell = sh.lang
tcl = tcl.lang
tk = tcl.lang
txt = nohilite.lang
sql = sql.lang
bib = bib.lang
makefile = makefile.lang
am = makefile.lang
in = makefile.lang
css = css.lang
m4 = m4.lang
ac = m4.lang
autoconf = m4.lang
sl = slang.lang
slsh = slang.lang
slang = slang.lang
properties = properties.lang
desktop = desktop.lang
ini = desktop.lang
conf = conf.lang
lsm = lsm.lang
spec = spec.lang
haxe = haxe.lang
hx = haxe.lang
ldap = ldap.lang
ldif = ldap.lang
glsl = glsl.lang
xorg = xorg.lang
scala = scala.lang
ada = ada.lang
adb = ada.lang
pc = pc.lang
pkgconfig = pc.lang
oz = oz.lang
texinfo = texinfo.lang
texi = texinfo.lang
hs = haskell.lang
hs = haskell.lang
lhs = haskell_literate.lang
haskell = haskell.lang
manifest = manifest.lang
mf = manifest.lang
asm = asm.lang
s = asm.lang
applescript = applescript.lang
scpt = applescript.lang
vbscript = vbscript.lang
vbs = vbscript.lang
awk = awk.lang
bat = bat.lang
batch = bat.lang
clipper = clipper.lang
prg = clipper.lang
cbl = cobol.lang
cobol = cobol.lang
dmd = d.lang
d = d.lang
errors = errors.lang
erl = erlang.lang
erlang = erlang.lang
vala = vala.lang
lisp = lisp.lang
el = lisp.lang
scm = scheme.lang
scheme = scheme.lang
po = po.lang
pot = po.lang
opa = opa.lang
javalog = javalog.lang
upc = upc.lang
tml = tml.lang
ly = lilypond.lang
# Symbols
cbracket = {|}
symbol = (|)|~|^|_
dynamic = '\\(||!|f{1,5}|p{1,5}|m(f|p)|fp|(r|s)fz|s(f|p){1,2})(?!\w)'
string delim \ \
# Scheme
scheme_block delim #'(( )) multiline
scheme delim '#(\'|\()' '\)|$' # single line only
# Comments
comment delim %{ %} multiline nested
comment start %
# Numbers
specialchar = '(?!#)-[1-5]\b', '\\[0-9]\b' # strings and fingerings
note_duration =
Re: Bug squad - updated list
Phil Holmes wrote: Thanks to Ralph, Marek and Eluze for volunteering to help with the Bug Squad. Based on their input, I believe this is a workable schedule. Monday:Ralph Tuesday:Eluze Wednesday: Brett Thursday: Ralph Friday: Marek Saturday:Brett Sunday: Phil Please could all squad members reply to confirm this is OK, and I'll update the CG. If there are other aspects of the CG that aren't clear, please let me know and I'll tackle those at the same time. i believe i've set up my email client correctly but i seem not to get any mails in the bug-answers folder unless i star issues - but i can't believe i have to star all the issues! what did i misunderstand?! Eluze -- View this message in context: http://old.nabble.com/Bug-squad---updated-list-tp32825412p33066294.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bug squad - updated list
- Original Message - From: -Eluze elu...@gmail.com To: lilypond-user@gnu.org Sent: Monday, January 02, 2012 2:50 PM Subject: Re: Bug squad - updated list Phil Holmes wrote: Thanks to Ralph, Marek and Eluze for volunteering to help with the Bug Squad. Based on their input, I believe this is a workable schedule. Monday:Ralph Tuesday:Eluze Wednesday: Brett Thursday: Ralph Friday: Marek Saturday:Brett Sunday: Phil Please could all squad members reply to confirm this is OK, and I'll update the CG. If there are other aspects of the CG that aren't clear, please let me know and I'll tackle those at the same time. i believe i've set up my email client correctly but i seem not to get any mails in the bug-answers folder unless i star issues - but i can't believe i have to star all the issues! what did i misunderstand?! Eluze -- View this message in context: http://old.nabble.com/Bug-squad---updated-list-tp32825412p33066294.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. I'm set up in a different way, but I believe you'll only get mails to this folder when someone updates a bug you've entered. It looks to me like you've reported 3 issues, and these each have one reply, so you should only have at most 3 mails in that folder. If you add more issues, you should see this more often. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax highlighting in the doc, call for testers
Hi Harm,
thanks for your feedback.
Your example let me notice that I forgot that R (upper case) is a note
as well, so I've updated the note_duration regexp.
Il 02/01/2012 15:58, Thomas Morley ha scritto:
I tested a file with a large scheme-definition.
In the attached file you may notice some inconsequences:
1. The scheme-functions of IR 4. Scheme functions aren't
high-lighted consistent:
ly:grob? isn't colored and ly: never.
2. In #(define (center-note-column grob) (let* ...
Some of the defined variables are colored some not.
Sory, that I can't do more than testing.
Scheme is the hardest part.
I don't have a solution for it. The problem is the conflict between
single and multiline blocks. I must put the multiline regexp before the
single line regexp, because the first has precedence. But I also need to
distinguish them: they cannot have the same start delimiter.
Single line blocks can be:
\once \override Tie #'staff-position = #3.5
tempoWholesPerMinute = #(ly:make-moment 120 4)
tagline = \markup { \override #'(box-padding . 1.0) }
Start: #' or #(
End: ) or end of line
In your example the multiline blocks start with #( so the single line
regexp applies.
I might define #( as a multiline start delimiter, but then the single
line instance (see tempoWholesPerMinute above) would break everything.
Also, tracking the end of that big block is not easy at all.
I think I've covered the most frequent and basic uses of scheme inside a
lilypond file. Large scheme definitions are quite difficult for me.
If any regexp guru has a good idea, please share it here.
HTH,
Harm
P.S. Great work so far!
Thanks!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
FOSDEM music notation gathering
Anyone planning to go to FOSDEM? http://fosdem.org/2012/ The largest open source developer gathering in Europe on Feb 4-5 in Brussels. The MuseScore team (Werner Schweer, Nicolas Froment, Thomas Bonte) will be there as well. Could be nice to have a music notation get together. -- View this message in context: http://old.nabble.com/FOSDEM-music-notation-gathering-tp33067767p33067767.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: FOSDEM music notation gathering
On Jan 2, 2012, at 8:06 PM, Thomas Bonte wrote: Anyone planning to go to FOSDEM? http://fosdem.org/2012/ The largest open source developer gathering in Europe on Feb 4-5 in Brussels. The MuseScore team (Werner Schweer, Nicolas Froment, Thomas Bonte) will be there as well. Could be nice to have a music notation get together. Do they have travel stipends? I didn't see anything on the site. I'm around that weekend, but the train ticket is outta my €€ range. Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bug squad - updated list
On Mon, Jan 02, 2012 at 03:15:45PM -, Phil Holmes wrote: - Original Message - From: -Eluze elu...@gmail.com To: lilypond-user@gnu.org Sent: Monday, January 02, 2012 2:50 PM Subject: Re: Bug squad - updated list i believe i've set up my email client correctly but i seem not to get any mails in the bug-answers folder unless i star issues - but i can't believe i have to star all the issues! what did i misunderstand?! I'm set up in a different way, but I believe you'll only get mails to this folder when someone updates a bug you've entered. It looks to me like you've reported 3 issues, and these each have one reply, so you should only have at most 3 mails in that folder. If you add more issues, you should see this more often. This is my understanding as well -- it's a bit unfortunate, but that's how it is. :( Eluze, could you suggest a change to the wording in the CG to clarify this point? Either James or Phil could push that directly to staging. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: FOSDEM music notation gathering
Interesting. If I find a affordable place to sleep maybe I will come. I am a Denemo dev and recently I'm working on my own Lilypond Frontend and it would be nice to meet other Linux Notation People. I am from Cologne, Germany, btw. If someone wants to travel with me (in my car, takes about 2 hours for me) it is more likely that I will come. Nils On Mon, 2 Jan 2012 11:06:52 -0800 (PST) Thomas Bonte thomas.bo...@gmail.com wrote: Anyone planning to go to FOSDEM? http://fosdem.org/2012/ The largest open source developer gathering in Europe on Feb 4-5 in Brussels. The MuseScore team (Werner Schweer, Nicolas Froment, Thomas Bonte) will be there as well. Could be nice to have a music notation get together. -- View this message in context: http://old.nabble.com/FOSDEM-music-notation-gathering-tp33067767p33067767.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: FOSDEM music notation gathering
Forgot about carpooling. There seem to be cheap-ish rides on covoiturage.fr - I'll keep ya'll posted. A few other lily developers going would tip the balance for me! ~Mike On Jan 2, 2012, at 10:40 PM, Nils wrote: Interesting. If I find a affordable place to sleep maybe I will come. I am a Denemo dev and recently I'm working on my own Lilypond Frontend and it would be nice to meet other Linux Notation People. I am from Cologne, Germany, btw. If someone wants to travel with me (in my car, takes about 2 hours for me) it is more likely that I will come. Nils On Mon, 2 Jan 2012 11:06:52 -0800 (PST) Thomas Bonte thomas.bo...@gmail.com wrote: Anyone planning to go to FOSDEM? http://fosdem.org/2012/ The largest open source developer gathering in Europe on Feb 4-5 in Brussels. The MuseScore team (Werner Schweer, Nicolas Froment, Thomas Bonte) will be there as well. Could be nice to have a music notation get together. -- View this message in context: http://old.nabble.com/FOSDEM-music-notation-gathering-tp33067767p33067767.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
NR 1.1.2, transpose: obscure sentence
I'm translating the Notation Reference and I found a sentence that I can't understand (I've never used \transpose). NR 1.1.2 Transpose, Known issues and warnings The relative conversion will not affect \transpose, \chordmode or \relative sections in its argument. To use relative mode within transposed music, an additional \relative must be placed inside \transpose. The second sentence is clear (it has been explained before). The first sentence not much to me. Can you make an example? Thanks, Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bug squad - updated list
Graham Percival-3 wrote: On Mon, Jan 02, 2012 at 03:15:45PM -, Phil Holmes wrote: - Original Message - From: -Eluze elu...@gmail.com To: lilypond-user@gnu.org Sent: Monday, January 02, 2012 2:50 PM Subject: Re: Bug squad - updated list i believe i've set up my email client correctly but i seem not to get any mails in the bug-answers folder unless i star issues - but i can't believe i have to star all the issues! what did i misunderstand?! I'm set up in a different way, but I believe you'll only get mails to this folder when someone updates a bug you've entered. It looks to me like you've reported 3 issues, and these each have one reply, so you should only have at most 3 mails in that folder. If you add more issues, you should see this more often. This is my understanding as well -- it's a bit unfortunate, but that's how it is. :( Eluze, could you suggest a change to the wording in the CG to clarify this point? Either James or Phil could push that directly to staging. maybe something like: you will automatically be considered/treated as stared if you enter a new issue. and: if you want to be acknowledged when other issues are changed you must star them yourself (otherwise they will only appear in the bug-ignore or bug-current folder) is this correct and does this make it clearer? thanks Eluze -- View this message in context: http://old.nabble.com/Bug-squad---updated-list-tp32825412p33068692.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
