Re: music-function madness (help!)
Trevor Daniels wrote: > Look up layers in the Notation Reference index. The > relevant sentence there is "The order of printing objects > with the same value of 'layer is indeterminate." > > Setting 'layer explicitly may solve your problem. Trevor, Amazing. Now it works. Mystery solved. Thanks for such a speedy solution. - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directory name of aux is invalid
John Mandereau Tuesday, January 06, 2009 12:06 AM Le lundi 05 janvier 2009 à 15:32 +, Trevor Daniels a écrit : I have a git problem with your recent commit c553fc2251b508befebd1dc297c4baa898463f34 to clean up the build scripts. The reason is that aux is a reserved word in Windows, along with a few others like com, lpt1, nul, prn, Lpt4, and no directory can be given these names. The effect is that I can't update my git repository from origin/master, which in turn means I can't push. Aargh. This commit also implies creation of scripts/aux/. I don't enjoy so much saying this, but the limitation we hit is worthwhile: Windows sucks, I wish there were only Unix OSes. :-) I can't really apologise for Windows, and I wasn't aware of this limitation until I hit this problem and investigated, but I'm sorry this has caused you extra work. Do you have any suggestions to get round this? What about replacing aux/ with auxiliar/ or helper/? "auxiliar" is the Spanish for "to aid", it's only one character shorter than "auxiliary", but it's nicer than ugly abbreviations longer than "aux" like "auxi" or "auxil". Well, this is kind of urgent for you Trevor, so let's not discuss too long: I'm renaming "aux" to "auxiliar". The precise name is not very important. I was worried I might not be able to get past the commit when I updated my local repository, thinking git might still try to create /aux before renaming it, but a reset hard to the new head seems to have been effective. Looks like I'm back in business! Many thanks, John! And my apologies again for the trouble. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
New German PO file for 'lilypond' (version 2.12.0)
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the German team of translators. The file is available at: http://translationproject.org/latest/lilypond/de.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) All other PO files for your package are available in: http://translationproject.org/latest/lilypond/ Please consider including all of these in your next release, whether official or a pretest. Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context. The following HTML page has been updated: http://translationproject.org/domain/lilypond.html If any question arises, please contact the translation coordinator. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LM master?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Sonntag, 4. Januar 2009 13:16:02 schrieb Trevor Daniels: > Clicking on (for example) Snippets: Section "Pitches" in Snippets > on page 2 of the NR takes you to the pitches snippet list, but > then clicking on the link back to Pitches at the top of that > snippet list, "These snippets illustrate Section "Pitches" in > Notation Reference", fails with a "file cannot be found error". > There is then no way back to the NR. You are using a self-compiled local version, right? That link goes to input/lsr/index, which on the server redirects to the documentation index... http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/ The redirect is also there in out-www/offline-root/input/lsr/lilypond- snippets/index.html It does not work in input/lsr/out-www/lilypond-snippets/index.html, though, because "make web" needs to shift several files around and fix cross-links (since the snippets page is in a different directory structure than the rest of the docs). You might also notice that the link in the NR does not work either if you look at the files in Documentation/user/out-www/lilypond/index.html ... > As a workaround you can choose to open the snippet list in a > new window. How about your Browser's back button? Cheers, Reinhold - -- - -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJY6rOTqjEwhXvPN0RAu/ZAJ4txUZ6eiGd5ZV+UIFmVOqbN3VfHQCfZEAZ JyR16B/scmpPVBYX00r3Paw= =koRI -END PGP SIGNATURE- ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directory name of aux is invalid
In message , Trevor Daniels writes Aargh. This commit also implies creation of scripts/aux/. I don't enjoy so much saying this, but the limitation we hit is worthwhile: Windows sucks, I wish there were only Unix OSes. :-) I can't really apologise for Windows, and I wasn't aware of this limitation until I hit this problem and investigated, but I'm sorry this has caused you extra work. It's a dos limitation that has carried into Windows. And it bites professionals. I recently had to teach my fellow (experienced!) programmers that certain file names weren't permitted... (I think a user typed CON into our program as data - only snag is the program used that data as a file name and promptly fell over ...) Cheers, Wol -- Anthony W. Youngman - anth...@thewolery.demon.co.uk ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directory name of aux is invalid
Anthony W. Youngman wrote Tuesday, January 06, 2009 7:09 PM In message , Trevor Daniels writes Aargh. This commit also implies creation of scripts/aux/. I don't enjoy so much saying this, but the limitation we hit is worthwhile: Windows sucks, I wish there were only Unix OSes. :-) I can't really apologise for Windows, and I wasn't aware of this limitation until I hit this problem and investigated, but I'm sorry this has caused you extra work. It's a dos limitation that has carried into Windows. And it bites professionals. I recently had to teach my fellow (experienced!) programmers that certain file names weren't permitted... For future reference, the complete list is: CLOCK$, AUX, CON, NUL, PRN, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9 These are all device names in all Windows OSes. The names are case-insensitive, and they cannot be used as directory names or the first part of a filename (the bit before the dot). Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directory name of aux is invalid
On Tue, Jan 6, 2009, Trevor Daniels said: > The names are case-insensitive, and they cannot be > used as directory names or the first part of a > filename (the bit before the dot). please note, in DOS (and many of its contemporary file systems), what users think of as the filename is not actually a ten character field but in fact two seperate entitys, the name (6 characters), and a 3 character extension. -- Dana Emery ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LM master?
Reinhold, you wrote Tuesday, January 06, 2009 7:02 PM
Am Sonntag, 4. Januar 2009 13:16:02 schrieb Trevor Daniels:
Clicking on (for example) Snippets: Section "Pitches" in Snippets
on page 2 of the NR takes you to the pitches snippet list, but
then clicking on the link back to Pitches at the top of that
snippet list, "These snippets illustrate Section "Pitches" in
Notation Reference", fails with a "file cannot be found error".
There is then no way back to the NR.
You are using a self-compiled local version, right?
No, I'm using pdfs downloaded from either your server
or lilypond.org (I can't remember which) into the same
directory. Using Windows I have no means of compiling
them myself.
That link goes to
input/lsr/index, which on the server redirects to the documentation
index...
http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/
The redirect is also there in out-www/offline-root/input/lsr/lilypond-
snippets/index.html
It does not work in input/lsr/out-www/lilypond-snippets/index.html,
though,
because "make web" needs to shift several files around and fix cross-links
(since the snippets page is in a different directory structure than the
rest
of the docs).
You might also notice that the link in the NR does not work either if you
look
at the files in Documentation/user/out-www/lilypond/index.html ...
As a workaround you can choose to open the snippet list in a
new window.
How about your Browser's back button?
They are not being viewed in a browser - these are pdfs being
viewed locally using Adobe Reader - we're talking about pdf
links here. If you look at my email again you'll see it was a
response to Graham saying:
As long as the pdf files are in the same directory, @rlsr{} should
produce working links in pdf as well. At least, it works in xpdf
and IIRC apple's Preview app. I'm not certain about adobe reader,
but I'd be surprised if it didn't work there too.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: release note translations
Hi, adding to this old thread: Was there already discussion on translating also the NEWS part of the documentation? It might not be really used by many people when 2.12 has become normality but for the moment it might be interesting since it also has a direct link from the news entry on lilypond.org. In other words: I suppose we would provide more updated 2.12 versions, especially with updated translations. In one of them it might also be nice to have the NEWS page integrated. Greetings Till John Mandereau schrieb: Le samedi 27 décembre 2008 à 14:58 -0800, Graham Percival a écrit : Translators: please send your translated versions of the release notes to John so that we can add them to the website. And/or commit directly to the web branch in git. Our messages almost crossed each other ;-) I found a bunch of translations on the wiki, but I'm not certain which ones are up-to-date. Previous emails on -devel make me think they are. But they are not in HTML, and they miss translation of Thanks titles. Typo for John to fix (in English): "Happy music typestting!" Oops, fixed. Best, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directory name of aux is invalid
2009/1/6 Trevor Daniels : >> It's a dos limitation that has carried into Windows. And it bites >> professionals. I recently had to teach my fellow (experienced!) programmers >> that certain file names weren't permitted... I recently had to run Windows Vista (for the only good reason one can think of: just to play GTA IV :-) and I was puzzled to see that folder names could not contain (or begin with) dots. I succesfully copied my .jedit/ and .ssh/ folder from my /home partition; but whenever I tried to create any other folder starting with a dot, it refused to do so (it also appears I have no write access to my own User directory, which does not make any sense, but that's another story). Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Patch to fix `make all'
Hello, I can't do a `make all' on the current git master, and this patch fixes the problem. Can someone apply it? Thanks, Patrick From ab347e3e065dc69c4630be331d52aaa1db905ec0 Mon Sep 17 00:00:00 2001 From: Patrick McCarty Date: Tue, 6 Jan 2009 14:20:51 -0800 Subject: [PATCH] Fix compile Signed-off-by: Patrick McCarty --- scripts/etf2ly.py |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/scripts/etf2ly.py b/scripts/etf2ly.py index 26fd2e0..54daa94 100644 --- a/scripts/etf2ly.py +++ b/scripts/etf2ly.py @@ -1116,7 +1116,8 @@ class Etf_file: while c and c.number <> endno: -thread.append (c) c = c.next +thread.append (c) +c = c.next if c: thread.append (c) -- 1.6.1 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch to fix `make all'
2009/1/6 Patrick McCarty : > I can't do a `make all' on the current git master, and this patch > fixes the problem. Can someone apply it? Thanks, applied. Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Frog git question
Carl, when you are working on something, do you commit your changes to your local repository every day? Would my final patch become a single commit even if I made the changes in several small commits locally? (I'm trying to avoid commit clutter on the Savannah repo.) How often do you re-sync with Savannah? Also, I think I have 7 out of 8 doc strings done, but the acciaccatura doesn't use define-music-function, so I will try to grep those definitions and find out where the doc string should go. Andrew ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frog mailing list discussion
2009/1/5 Carl D. Sorensen : > I'd recommend establishing a dual boot system with a Linux partition that > you use for building LilyPond. It was lots easier for me. The easiest solution for a Windows user being without a doubt http://wubi-installer.org/ (no partitioning needed) Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frog mailing list discussion
On 1/5/09 10:19 AM, "Valentin Villenave" wrote: > 2009/1/5 Carl D. Sorensen : > >> I'd recommend establishing a dual boot system with a Linux partition that >> you use for building LilyPond. It was lots easier for me. > > The easiest solution for a Windows user being without a doubt > http://wubi-installer.org/ This looks really cool! Andrew, could you try this out, since you want to compile on a Windows box? T Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frog mailing list discussion
I'm installing it now. If this works it will be fabulous and I'll be removing the cygwin installation. I'm going out in about 20 mins, hopefully it will be installed when I get back. I'll let you know how it get on. andrew 2009/1/5 Carl D. Sorensen > > > > On 1/5/09 10:19 AM, "Valentin Villenave" wrote: > > > 2009/1/5 Carl D. Sorensen : > > > >> I'd recommend establishing a dual boot system with a Linux partition > that > >> you use for building LilyPond. It was lots easier for me. > > > > The easiest solution for a Windows user being without a doubt > > http://wubi-installer.org/ > > This looks really cool! Andrew, could you try this out, since you want to > compile on a Windows box? > T > Thanks, > > Carl > > ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frogs: oldaddlyrics in music-functions-init.ly
Ian, On 1/5/09 3:40 PM, "Ian Hulin" wrote: > Hi Carl, > \oladdlyrics is on my to-do list of undocumented functions. > \oldaddlyrics is the deprecated version of \addlyrics. > Should I remove the oldaddlyrics entry and add in one for \addlyrics so > this one is included in the docs, or just put a note that oldaddlyrics > is retained only in order to retain backwards compatibility? I'd recommend that you keep the oldaddlyrics entry, and make sure it mentions that it is deprecated. Hmm -- I don't know why addlyrics is not included. Could you do some sleuthing on addlyrics and see where it is? It may be that it isn't a music function anymore; this documentation process is only for music functions, IIRC. > > How do I commit my changes to git once I've finished them if I'm working > on a Windows-only system? Do I need to add dual-boot for Linux to my > machine to do this? (I'm downloading Wubi now.) > First, you need to understand that you will only commit to your local repository. You don't have access to commit to the savannah repository. To commit, you will need to use whatever version of git commit works on your machine. On mine, (Mac OSX) and on Linux, I type git commit -a which opens up an editor window (in vim, by default). I type an i to get vim in insert mode, then type the commit message for the commit. When I'm done with the commit message, I type followed by :wq, which writes the changes and exits the editor. The commit is then made by git. It is also possible to put the commit message on the git command line, and avoid the whole editor thing. You can see this possibility by Googling for git commit. Once you've committed the changes, you can get a patch with the command git format patch You do not need to add dual-boot to use git to make patches. The reason that Andrew needed Linux was because he wanted to be able to compile LilyPond. The compilation tools are all built on Linux and work easiest from there. For changes only to .ly files or .scm files, it is not necessary to compile LilyPond. All those files are loaded at runtime. Thanks for the question. It's a good one. Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frogs: oldaddlyrics in music-functions-init.ly
HI Carl, You keep saying that we don't need to build because the lily files and the scheme files are interpreted and are loaded at runtime. If we're working in a copy of the GIT repository then it won't have a binary to run. If we work in a downloaded binary distribution then the changes aren't going to be in the GIT working directory and we'll have to produce the patch ourselves or try to remember everything we changed and port it into the GIT working folder. Am I missing something fundamental? It's just that it seems to me that not having a buildable copy of the source is likely to involve an awful lot of faffing about. andrew 2009/1/5 Carl D. Sorensen > Ian, > > > > On 1/5/09 3:40 PM, "Ian Hulin" wrote: > > > Hi Carl, > > \oladdlyrics is on my to-do list of undocumented functions. > > \oldaddlyrics is the deprecated version of \addlyrics. > > Should I remove the oldaddlyrics entry and add in one for \addlyrics so > > this one is included in the docs, or just put a note that oldaddlyrics > > is retained only in order to retain backwards compatibility? > > I'd recommend that you keep the oldaddlyrics entry, and make sure it > mentions that it is deprecated. > > Hmm -- I don't know why addlyrics is not included. Could you do some > sleuthing on addlyrics and see where it is? It may be that it isn't a > music function anymore; this documentation process is only for music > functions, IIRC. > > > > > How do I commit my changes to git once I've finished them if I'm working > > on a Windows-only system? Do I need to add dual-boot for Linux to my > > machine to do this? (I'm downloading Wubi now.) > > > > First, you need to understand that you will only commit to your local > repository. You don't have access to commit to the savannah repository. > > To commit, you will need to use whatever version of git commit works on > your > machine. > > On mine, (Mac OSX) and on Linux, I type > > git commit -a > > which opens up an editor window (in vim, by default). > > I type an i to get vim in insert mode, then type the commit message > for the commit. > > When I'm done with the commit message, I type followed by :wq, which > writes the changes and exits the editor. The commit is then made by git. > > It is also possible to put the commit message on the git command line, and > avoid the whole editor thing. You can see this possibility by Googling for > git commit. > > Once you've committed the changes, you can get a patch with the command > > git format patch > > You do not need to add dual-boot to use git to make patches. The reason > that Andrew needed Linux was because he wanted to be able to compile > LilyPond. The compilation tools are all built on Linux and work easiest > from there. > > For changes only to .ly files or .scm files, it is not necessary to compile > LilyPond. All those files are loaded at runtime. > > Thanks for the question. It's a good one. > > Carl > > ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frogs: oldaddlyrics in music-functions-init.ly
On 1/5/09 5:16 PM, "Andrew Wilson" wrote: > HI Carl, > > You keep saying that we don't need to build because > the lily files and the scheme files are interpreted and > are loaded at runtime. If we're working in a copy of > the GIT repository then it won't have a binary to run. > If we work in a downloaded binary distribution then > the changes aren't going to be in the GIT working > directory and we'll have to produce the patch > ourselves or try to remember everything we changed > and port it into the GIT working folder. Am I missing > something fundamental? It's just that it seems to > me that not having a buildable copy of the source is > likely to involve an awful lot of faffing about. > andrew First of all, I think that the easiest way to develop LilyPond is to have a buildable source tree, and I'd recommend it for anybody who's willing to go to the effort to get it. But with a little bit of directory magic, you can work without it. Just go into your main lilypond directory for the binary, and move out the ly/, scm/, and input/ directories to some safe place. (e.g. a folder called binary-dist). Then you create a symbolic link in the main binary lilypond directory to the ly/, scm/ and input/ directories from your git repository. Now, although the directories are actually in your git repository, they appear to the binary to be in the binary directory. And everything works just as if you had built it from your git repository. You can even create a batch file to copy out the binary distro files and create the symbolic links, and another to delete the symbolic links and copy back the binary distro files, if you want to make it easy to switch from binary distro to git repo. I'm certainly not trying to discourage anyone from building from source; that's my preferred way. But I don't want people who can't get build from source working to think that they can't contribute to changes in .ly files and .scm files. Please let me know if this isn't clear. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frogs: oldaddlyrics in music-functions-init.ly
Seems pretty clear to me. Thanks. andrew 2009/1/6 Carl D. Sorensen > First of all, I think that the easiest way to develop LilyPond is to have a > buildable source tree, and I'd recommend it for anybody who's willing to go > to the effort to get it. > > But with a little bit of directory magic, you can work without it. Just go > into your main lilypond directory for the binary, and move out the ly/, > scm/, and input/ directories to some safe place. (e.g. a folder called > binary-dist). > > Then you create a symbolic link in the main binary lilypond directory to > the > ly/, scm/ and input/ directories from your git repository. Now, although > the directories are actually in your git repository, they appear to the > binary to be in the binary directory. And everything works just as if you > had built it from your git repository. > > You can even create a batch file to copy out the binary distro files and > create the symbolic links, and another to delete the symbolic links and > copy > back the binary distro files, if you want to make it easy to switch from > binary distro to git repo. > > I'm certainly not trying to discourage anyone from building from source; > that's my preferred way. But I don't want people who can't get build from > source working to think that they can't contribute to changes in .ly files > and .scm files. > > Please let me know if this isn't clear. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frog git question
On 1/6/09 6:57 PM, "Andrew Hawryluk" wrote: > Carl, when you are working on something, do you commit your changes to > your local repository every day? Would my final patch become a single > commit even if I made the changes in several small commits locally? > (I'm trying to avoid commit clutter on the Savannah repo.) I'm copying this to all the frogs because they should/will have the same question. You can feel free to commit as many times as you want. It creates commit clutter on your local repo, but that's not really a problem. I don't work on the master branch very often. I check out master from Savannah, then create my own branch on which to work: git checkout -b mybranch Then I do the work on mybranch. I can commit as many patches as I want. When I'm done with my work, I compress all my patches into one by using the command git rebase -i where I run gitk and click on the initial commit that I got from master, then copy the SHA1 ID and paste it into my terminal. This will open an editor window that lists all of the commits you've made. You leave the first commit with pick as the first word. The remaining commits you change the "pick" to "squash". Then you leave the editor (:wq). A new editor window pops up, and you create the final commit message that you want to keep. You exit the editor with :wq and then all of your nitpicky commits are merged into one, production quality commit. You don't have push access, so you can't push to Savannah. You can create a mirror on repo.or.cz, and you will have push access there. It's a great place to learn. Since you don't have push access, you'll use git format-patch to create a patch that covers your commit. I'll apply the patch to my frogs branch, and when I'm ready to push to Savannah, I'll rebase my frogs branch, then push. One thing that I found out is that if I make changes, then pull, then commit, I can avoid a merge commit on Savannah. But sometimes a merge is necessary, because I have to commit before I pull if there are changes in master to a file I've changed locally. Anyway, I hope this is helpful. > > How often do you re-sync with Savannah? Just before each push. > > Also, I think I have 7 out of 8 doc strings done, but the acciaccatura > doesn't use define-music-function, so I will try to grep those > definitions and find out where the doc string should go. > Good for you. If you can't figure it out, give a shout to Neil. He warned me about 3 functions that don't use define-music-function. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frogs: oldaddlyrics in music-functions-init.ly
2009/1/6 Carl D. Sorensen : > Then you create a symbolic link in the main binary lilypond directory to the > ly/, scm/ and input/ directories from your git repository. Now, although > the directories are actually in your git repository, they appear to the > binary to be in the binary directory. And everything works just as if you > had built it from your git repository. Hm. Does Windows have symlinks now? Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frogs: oldaddlyrics in music-functions-init.ly
On 1/6/09 9:32 PM, "Valentin Villenave" wrote: > 2009/1/6 Carl D. Sorensen : > >> Then you create a symbolic link in the main binary lilypond directory to the >> ly/, scm/ and input/ directories from your git repository. Now, although >> the directories are actually in your git repository, they appear to the >> binary to be in the binary directory. And everything works just as if you >> had built it from your git repository. > > Hm. Does Windows have symlinks now? cygwin does, which is where I used them. According to Wikipedia, Vista supports sym links, and XP supports junctions, which only work with directories, but that's what we need to do for this bit of magic. http://en.wikipedia.org/wiki/Symbolic_link Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
copyright year update script issue
Jan, can you add a list of exceptions to your copyright year update script? Some files like the mf2pt1 stuff are contributed and should stay as-is. I've fixed that manually in the git, but an automatic process would be better. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
