Re: MacOS X Preview+lilypond warning
On 11-Aug-05, at 2:39 AM, Hans Aberg wrote: If you haven't verified it on Mac OS 10.4.2, you can send me a PDF file, telling which pages to print. I will then send the result back to you, or wherever you want. Thanks. I can now confirm that the problem also exists on 10.4. Don't use Preview to extract certain pages from a long document. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
ec-fonts in 2.6, was: convert-ly problem
... You're welcome to reinstate the ec fonts as your private defaults, though. Well, this (I mean reinstating the ec fonts as my private defaults) is what I would like to do, and also asked how this could be done in this list three weeks ago. I got, however, no answer. Could you, or someone else explain how to do it? I believe in the above code Times New Roman, Helvetica, Courier stand for the serif, sans-serif and fixed width fonts respectively. What should I replace them with to have the ec-fonts as defaults? Imruska Hello list, I am also interested in an explanation (for Windows/Cygwin). Thanks in advance, Thomas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tie a tremolando - tremolo tied to chord
Thanks for the hint, I've added a version of it to the manual.
/Mats
Steve D wrote:
A while back I asked about the possibility of, and then sponsored, a
feature to tie grace note and other arpeggios to a following chord.
Han-Wen created the
\set tieWaitForNote = ##t (or ##f, as the case may require)
feature as a result, which greatly simplified the piano score I was
notating at the time.
I have found another real-world practical use for the tieWaitForNote
feature: tieing a tremolando (tremolo) chord to a following chord. The
following bit of lilypond code for the upper staff of a piano score:
\set tieWaitForNote = ##t \repeat tremolo 12 { ef'32~ ef,~ }
ef' ef,4 \set tieWaitForNote = ##f df df,4 c c,4
produces the result shown in the PNG image attached to this email
(tied-tremolando-example.png).
Thank you so much for this feature Han-Wen.
-sd
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OSX and Text Editors
Stephan Moss wrote: When Lilypond reads the .ly file, what is it looking for in terms of format (line endings, etc)? Line endings are treated like any other white space (spaces and tabs), so you can write your input on a single line if you like. I took a file that worked from the built in editor to Text Wrangler and then back again and it generated lots of errors (Unexpected #end, if I remember right). I wound up re-entering it in the built in editor. I'm assuming that Text Wrangler (from the people who make Bbedit) mangled the file in such a way that the parser didn't like it anymore. My guess is that it didn't output a plain text file but added some extra control characters somewhere. An alternative is that it didn't use UNIX style line endings but the old-style Mac line endings or used the wrong character encoding. I don't know anything about this particular editor, but usually it's possible to specify what format the file is saved in. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
vim mode
Hi everyone, I am switching my default editor back to vim (from emacs). I want to make sure that I am getting the best possible results with the syntax highlighting. I have a dir - ~./vim/syntax with one file 'lilypond.vim'. This file has a date of 2002 (in the first few lines). I note that there are quite a few *.vim files in the /usr/share/lilypond/2.4.5/vim/ directories. Do I need to do anything to the various files or are they picked up automatically by y lilypond.vim file? Thanks for any tips in advance, Sterling MacNay ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: font finding problem
Hi, after having wasted a real lot of hours trying to install 2.6.3 which got me deep into package dependency hell and forced me to update at least a dozen other programs as well, I finally had to give up and try 2.4.4 instead, for which there is an RPM from SuSE 9.3. After having been able to install that with all dependencies working, I got the same error as Johan and wonder if there is a solution, because I also do have the font on my system. As I say, installing 2.6.3 is not an option for me at this time, because it would in fact force me to upgrade my whole system (running SuSE 9.1), which I can't do in the near future. There must be a possibility to tell Lilypond where the font is - it's in its own directory tree, after all. Any help would be greatly appreciated, especially because I am new to Lilypond and would really like to try it out. Thomas -- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Mac OSX and Text Editors
So, Unix endings utf-8 encoding is best? That's what the built in editor spits out? -Original Message- From: Mats Bengtsson [mailto:[EMAIL PROTECTED] Sent: Friday, August 12, 2005 6:52 AM To: Stephan Moss Cc: lilypond-user@gnu.org Subject: Re: Mac OSX and Text Editors Stephan Moss wrote: When Lilypond reads the .ly file, what is it looking for in terms of format (line endings, etc)? Line endings are treated like any other white space (spaces and tabs), so you can write your input on a single line if you like. I took a file that worked from the built in editor to Text Wrangler and then back again and it generated lots of errors (Unexpected #end, if I remember right). I wound up re-entering it in the built in editor. I'm assuming that Text Wrangler (from the people who make Bbedit) mangled the file in such a way that the parser didn't like it anymore. My guess is that it didn't output a plain text file but added some extra control characters somewhere. An alternative is that it didn't use UNIX style line endings but the old-style Mac line endings or used the wrong character encoding. I don't know anything about this particular editor, but usually it's possible to specify what format the file is saved in. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OSX and Text Editors
On Friday 12 August 2005 15.51, Mats Bengtsson wrote: Stephan Moss wrote: When Lilypond reads the .ly file, what is it looking for in terms of format (line endings, etc)? Line endings are treated like any other white space (spaces and tabs), so you can write your input on a single line if you like. I took a file that worked from the built in editor to Text Wrangler and then back again and it generated lots of errors (Unexpected #end, if I remember right). I wound up re-entering it in the built in editor. I'm assuming that Text Wrangler (from the people who make Bbedit) mangled the file in such a way that the parser didn't like it anymore. My guess is that it didn't output a plain text file but added some extra control characters somewhere. An alternative is that it didn't use UNIX style line endings but the old-style Mac line endings or used the wrong character encoding. I don't know anything about this particular editor, but usually it's possible to specify what format the file is saved in. I have experienced the same error message after copypasting from messages in kmail. Due to a kmail bug, some illegal characters were sometimes inserted in the beginning of lines. In my case, I could spot which the invalid characters were, by viewing it in less. Erik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Markup in TextSpanner edge-text
Hello, I'm trying: \override TextSpanner #'edge-text = #'( \markup rit . ) \override TextSpanner #'edge-text = #'( (markup rit) . ) \override TextSpanner #'edge-text = #'( (make-simple-markup rit) . ) But none of them works: all of them writes nothing. Can you provide any help achieving this? Thanks, Bert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OSX and Text Editors
I have used TextWrangler with Lilypond on OS X Panther for some time. Stephan, I think that Mats is right that TextWrangler is probably using Mac line endings in your files. I set Default Line Breaks to UNIX when I installed Text Wrangler and use UTF-8 encoding and have not had any problems with Lilypond files. Go to Preferences Text Files: Saving to set up the UNIX line endings and default encoding. Kris Shaffer On Fri, 12 Aug 2005 09:51:56 -0400, Mats Bengtsson [EMAIL PROTECTED] wrote: Stephan Moss wrote: When Lilypond reads the .ly file, what is it looking for in terms of format (line endings, etc)? Line endings are treated like any other white space (spaces and tabs), so you can write your input on a single line if you like. I took a file that worked from the built in editor to Text Wrangler and then back again and it generated lots of errors (Unexpected #end, if I remember right). I wound up re-entering it in the built in editor. I'm assuming that Text Wrangler (from the people who make Bbedit) mangled the file in such a way that the parser didn't like it anymore. My guess is that it didn't output a plain text file but added some extra control characters somewhere. An alternative is that it didn't use UNIX style line endings but the old-style Mac line endings or used the wrong character encoding. I don't know anything about this particular editor, but usually it's possible to specify what format the file is saved in. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re:
1 - How to substitute a notehead of an eigthnote to a notehead of a halfnote? I came up with this solution: \once \override Voice.NoteHead #'print-function = #Text_interface::print \once \override Voice.NoteHead #'text = #(make-musicglyph-markup noteheads.s1) c8 2 - How to obtain a key signature that have, simultaneously, the notes b-flat a f-sharp? See: http://lilypond.org/doc/v2.6/input/regression/out-www/collated-files.html#key-signature-scordatura.ly For advanced tricks looking at regression tests is always helpful. Bert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re:
1 - How to substitute a notehead of an eigthnote to a notehead of a halfnote? I've found another (perhaps better), but also interesting (for me who now's going to understand Scheme and LilyPond better): \once \override Voice.NoteHead #'glyph-name-procedure = #(lambda (a b) 1 ) The number is from the end of noteheads.s1, see the Feta font in the manual. The (a b) is the parameters that is needed for the glyph-name-procedure. I found by trial that it needs 2 parameters. Bert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: vim mode
On 12-Aug-05, at 8:14 AM, Sterling Sympatico wrote: I have a dir - ~./vim/syntax with one file 'lilypond.vim'. This file has a date of 2002 (in the first few lines). I note that there are quite a few *.vim files in the /usr/share/lilypond/2.4.5/vim/ directories. Do I need to do anything to the various files or are they picked up automatically by y lilypond.vim file? Here's what I have: spark:~ gperciva$ more ~/.vimrc set encoding=utf-8 set fileencodings=utf-8,latin1 set fileencoding=utf-8 set termencoding=utf-8 set runtimepath+=~/usr/pkg/lilypond/share/lilypond/2.7.5/vim/ syntax on spark:~ gperciva$ more ~/.vim/filetype.vim if exists(did_load_filetypes) finish endif augroup filetypedetect au! BufNewFile,BufRead *.ly setf lilypond augroup END (no other files in ~/.vim/) I don't know if it's all necessary, but this setup works in both vim 6.2 and 6.3. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Markup in TextSpanner edge-text
On 12-Aug-05, at 11:07 AM, Bertalan Fodor wrote: But none of them works: all of them writes nothing. This happened to come up on lily-devel a few days ago: \override TextSpanner #'edge-text = #(cons (markup #:italic rit ) ) I updated Text Markup (but a new version hasn't come out yet), but I should update Text Spanners as well. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
