Lexer/Parser: Don't package location data in SCM_TOKEN semantic value (issue 45420044)
LGTM, from mere inspection. https://codereview.appspot.com/45420044/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Print semantic values for -ddebug-parser in display-lily-music style. (issue 40040046)
LGTM. https://codereview.appspot.com/40040046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Building Lilypond documentation
I've decided to get at least a little active in Lilypond development, and thought I should start with getting my development environment up and running. I get some weird errors when building the different doc targets, such as: make[4]: Entering directory `/lilydev/build/input/regression/lilypond-book' /lilydev/./input/regression/lilypond-book/GNUmakefile:24: warning: overriding commands for target `out-www/collated-files.list' /lilydev/./make/lysdoc-rules.make:6: warning: ignoring old commands for target `out-www/collated-files.list' make[4]: Circular out-www/collated-files.list <- suffix-tely.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-include-file.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-include-language-detection.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-language-detection.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-musicxml-file-options.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-musicxml-file.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-papersize-docs.tely dependency dropped. make[4]: Circular out-www/texinfo-include-file.texi <- texinfo-include-file.tely dependency dropped. make[4]: Circular out-www/texinfo-include-language-detection.texi <- texinfo-include-language-detection.tely dependency dropped. make[4]: Circular out-www/texinfo-language-detection.texi <- texinfo-language-detection.tely dependency dropped. make[4]: Circular out-www/texinfo-musicxml-file-options.texi <- texinfo-musicxml-file-options.tely dependency dropped. make[4]: Circular out-www/texinfo-musicxml-file.texi <- texinfo-musicxml-file.tely dependency dropped. make[4]: Circular out-www/texinfo-papersize-docs.texi <- texinfo-papersize-docs.tely dependency dropped. /lilydev/build/scripts/build/out/run-and-check "DEPTH=../../.. AJAX_SEARCH= TOP_SRC_DIR=/lilydev PERL_UNICODE=SD texi2html --error-limit=0 --I=/lilydev/input/regression/lilypond-book --I=./out-www --I=/lilydev/build/./out-www/xref-maps --init-file=/lilydev/Documentation/lilypond-texi2html.init --output=out-www/suffix-tely.html out-www/suffix-tely.texi" "suffix-tely.texilog.log" Please check the logfile suffix-tely.texilog.log for errors And "suffix-tely.texilog.log" contains "*** out-www/ not writable". Not sure which one of the many out-www folders that is referring to, but they are all writable as far as I can see. I am probably missing something simple here. I'd appreciate if someone can give me a hint. Thanks -- Sven Axelsson ++[>++>+++>++>++ ><-]>.+..>+.>+.<<-.>>+.>.<<. +++.>-.<<++.>>.<++.>>>++..>>.<. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
On Jan 2, 2014, at 1:29 PM, Sven Axelsson wrote: > I've decided to get at least a little active in Lilypond development, and > thought I should start with getting my development environment up and > running. I get some weird errors when building the different doc targets, > such as: > > Please check the logfile suffix-tely.texilog.log for errors > > And "suffix-tely.texilog.log" contains "*** out-www/ not writable". Not sure > which one of the many out-www folders that is referring to, but they are all > writable as far as I can see. > > I am probably missing something simple here. I'd appreciate if someone can > give me a hint. Try doing a recursive chmod (find . -name “a regular expression” | xargs chmod my-permissions-wishes) and/or running make in sudo. I do the latter whenever I build out of laziness - works for me. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
On 02/01/14 11:29, Sven Axelsson wrote: I've decided to get at least a little active in Lilypond development, and thought I should start with getting my development environment up and running. I get some weird errors when building the different doc targets, What does 'building the different doc targets' mean exactly? Does a 'make doc' work fundamentally? James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: CG: basic cleanup (issue 46120044)
On 01/01/14 21:35, David Kastrup wrote: Benkő Pál writes: 2014/1/1 : Janek, when people start with `git clone` do they also get a staging branch that tracks the one on savannah? I think we still want at least one mention of how to set up a 'staging' branch to track origin/staging, git checkout --track -b staging origin/staging you can set up any branch to track origin/staging (or origin/master or origin/dev/janek/fancy-feature or whatever) directly. I always set up my topic branches so. Don't track staging, or you'll end up pushing bad staging commits back into staging whenever staging has to be reset. And this should go into the CG too :) James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
AFAICS it will be complaining about the directory below where the logfile is found. -- Phil Holmes - Original Message - From: Sven Axelsson To: lilypond-devel@gnu.org Sent: Thursday, January 02, 2014 11:29 AM Subject: Building Lilypond documentation I've decided to get at least a little active in Lilypond development, and thought I should start with getting my development environment up and running. I get some weird errors when building the different doc targets, such as: make[4]: Entering directory `/lilydev/build/input/regression/lilypond-book' /lilydev/./input/regression/lilypond-book/GNUmakefile:24: warning: overriding commands for target `out-www/collated-files.list' /lilydev/./make/lysdoc-rules.make:6: warning: ignoring old commands for target `out-www/collated-files.list' make[4]: Circular out-www/collated-files.list <- suffix-tely.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-include-file.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-include-language-detection.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-language-detection.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-musicxml-file-options.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-musicxml-file.tely dependency dropped. make[4]: Circular out-www/collated-files.list <- texinfo-papersize-docs.tely dependency dropped. make[4]: Circular out-www/texinfo-include-file.texi <- texinfo-include-file.tely dependency dropped. make[4]: Circular out-www/texinfo-include-language-detection.texi <- texinfo-include-language-detection.tely dependency dropped. make[4]: Circular out-www/texinfo-language-detection.texi <- texinfo-language-detection.tely dependency dropped. make[4]: Circular out-www/texinfo-musicxml-file-options.texi <- texinfo-musicxml-file-options.tely dependency dropped. make[4]: Circular out-www/texinfo-musicxml-file.texi <- texinfo-musicxml-file.tely dependency dropped. make[4]: Circular out-www/texinfo-papersize-docs.texi <- texinfo-papersize-docs.tely dependency dropped. /lilydev/build/scripts/build/out/run-and-check "DEPTH=../../.. AJAX_SEARCH= TOP_SRC_DIR=/lilydev PERL_UNICODE=SD texi2html --error-limit=0 --I=/lilydev/input/regression/lilypond-book --I=./out-www --I=/lilydev/build/./out-www/xref-maps --init-file=/lilydev/Documentation/lilypond-texi2html.init --output=out-www/suffix-tely.html out-www/suffix-tely.texi" "suffix-tely.texilog.log" Please check the logfile suffix-tely.texilog.log for errors And "suffix-tely.texilog.log" contains "*** out-www/ not writable". Not sure which one of the many out-www folders that is referring to, but they are all writable as far as I can see. I am probably missing something simple here. I'd appreciate if someone can give me a hint. Thanks -- Sven Axelsson ++[>++>+++>++>++ ><-]>.+..>+.>+.<<-.>>+.>.<<. +++.>-.<<++.>>.<++.>>>++..>>.<. -- ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
On 2 January 2014 12:50, Phil Holmes wrote: > AFAICS it will be complaining about the directory below where the > logfile is found. > Thanks. Making that folder (./build/input/regression/lilypond-book/out-www) world writeable did the trick. Continuing the build now. We'll see if this is needed in more places. -- Sven Axelsson ++[>++>+++>++>++ ><-]>.+..>+.>+.<<-.>>+.>.<<. +++.>-.<<++.>>.<++.>>>++..>>.<. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Announcing 2.18.0 widely?
Apart from a note about the convert-ly accident, does anybody see a reason not to announce 2.18.0 presently to a wide audience? Or should we wait until 2.19.0 is out? I _think_ that the web site should be fine currently. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Announcing 2.18.0 widely?
On 02/01/14 14:54, David Kastrup wrote: Apart from a note about the convert-ly accident, does anybody see a reason not to announce 2.18.0 presently to a wide audience? Or should we wait until 2.19.0 is out? I _think_ that the web site should be fine currently. Are there any considerations from this: *https://code.google.com/p/lilypond/issues/detail?id=3768 James * ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Announcing 2.18.0 widely?
James writes: > On 02/01/14 14:54, David Kastrup wrote: >> Apart from a note about the convert-ly accident, does anybody see a >> reason not to announce 2.18.0 presently to a wide audience? Or should >> we wait until 2.19.0 is out? I _think_ that the web site should be fine >> currently. >> > Are there any considerations from this: > > *https://code.google.com/p/lilypond/issues/detail?id=3768 It does not sound like a regression, does it? At any rate, it's not fixable without a new build, so we would need to wait for any announcement until 2.18.1. I think it is a minor nuisance, and an old one at that. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
regtest for new glyphs necessary?
Hello list, happy new year to you all! I have drawn some new glyphs for LilyPond, namely 1) the double G clef, mentioned in http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00029.html 2) the varpercussion clef, mentiaoned in the same message 3) the tenor G clef, mentioned in http://lists.gnu.org/archive/html/lilypond-user/2013-11/msg00661.html 4) the alternate C clef, issue 693 http://code.google.com/p/lilypond/issues/detail?id=693 I am about to upload a patch for these four glyphs within the next days, but I wanted to ask whether a new (or enhanced expisting) regtest is necessary for this type of enhancement? Regards, Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Announcing 2.18.0 widely?
David Kastrup wrote Thursday, January 02, 2014 2:54 PM > Apart from a note about the convert-ly accident, does anybody see a > reason not to announce 2.18.0 presently to a wide audience? Or should > we wait until 2.19.0 is out? I _think_ that the web site should be fine > currently. I think it's pretty solid. In any case the expectation is that a .0 release will be quickly followed by a .1 release which fixes all the oversights. Go for it! BTW, are the number of downloads recorded anywhere? It would be interesting to track this for stable releases. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
It appears as if texi2html needs word-writeable folders to work. Thus I took the simple route of running make doc (and make test) under sudo. Is that how others does it too? -- Sven Axelsson ++[>++>+++>++>++ ><-]>.+..>+.>+.<<-.>>+.>.<<. +++.>-.<<++.>>.<++.>>>++..>>.<. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Announcing 2.18.0 widely?
- Original Message - From: "Trevor Daniels" To: "David Kastrup" ; Sent: Thursday, January 02, 2014 3:37 PM Subject: Re: Announcing 2.18.0 widely? BTW, are the number of downloads recorded anywhere? It would be interesting to track this for stable releases. Google analytics should track this. If you can persuade GP to log in and check -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
Sven Axelsson writes: > It appears as if texi2html needs word-writeable folders to work. No, it just needs writeable folders to work. > Thus I took the simple route of running make doc (and make test) under > sudo. Is that how others does it too? No, never. I think that if you do make sudo make install that _some_ directory is only created during make install, and thus getting rid of it again is a more-than-once nuisance. If you figure out what it is exactly, feel free to file a bug. It may also be in connection with make make doc sudo make install I don't remember it exactly. Some xref-thing or so. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
On 02/01/14 15:51, David Kastrup wrote: Sven Axelsson writes: It appears as if texi2html needs word-writeable folders to work. No, it just needs writeable folders to work. Thus I took the simple route of running make doc (and make test) under sudo. Is that how others does it too? No, never. I think that if you do make sudo make install that _some_ directory is only created during make install, and thus getting rid of it again is a more-than-once nuisance. And considering I make doc about 3-4 times a day most days with no problems and I am not AFAIK using 'sudo', which was why I was interested in what exactly is being done here step by step. Are you for instance doing/have done something as 'root' and then trying to run the make process as joe-user? If I take a quick peek in my LILYPOND_GIT all my dirs are owner/group 'jlowe jlowe' than root, or any other user. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LILY-GIT PITA
On Wed, Jan 1, 2014 at 10:12 AM, James wrote: > On 07/12/13 18:33, Carl Sorensen wrote: >> I've thought of some possible fixes: >> >> 1) Add an "expert mode" button that then would open up a listbox that >> would allow you to choose your branch. >> >> 2) Create a special, branch-unaware version of lily-git.tcl that would >> always work on the current branch. >> >> 3) Create some special shell commands that will do just what you want, and >> give them to you directly. >> >> At the moment, I'm leaning towards 3, as it's the least-effort way to go. >> >> What do you think? >> >> Thanks, >> >> Carl >> Just now seeing this (I don't think I was subscribed when Carl S. wrote this). After my recent experience with lily-git.tcl and submitting a patch, one thing I would request is that, if possible, some kind of automatic line wrapping be built into its processing of the commit message (i.e., if a line exceeds n characters, go back to the last space prior to the nth character and replace with a line break). This will avoid the issue of poorly wrapped lines, which both David K and Janek have messaged me about. I don't recall that particular point being discussed in the CG. While it is certainly better to line break by hand, this would at least provide some degree of a "fail safe" against what I did as an uninformed new contributor. Carl P. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
On 2 January 2014 17:10, James wrote: > On 02/01/14 15:51, David Kastrup wrote: > >> Sven Axelsson writes: >> >> It appears as if texi2html needs word-writeable folders to work. >>> >> No, it just needs writeable folders to work. >> >> Thus I took the simple route of running make doc (and make test) under >>> sudo. Is that how others does it too? >>> >> No, never. I think that if you do >> >> make >> sudo make install >> >> that _some_ directory is only created during make install, and thus >> getting rid of it again is a more-than-once nuisance. >> > And considering I make doc about 3-4 times a day most days with no > problems and I am not AFAIK using 'sudo', which was why I was interested in > what exactly is being done here step by step. > > Are you for instance doing/have done something as 'root' and then trying > to run the make process as joe-user? > > If I take a quick peek in my LILYPOND_GIT all my dirs are owner/group > 'jlowe jlowe' than root, or any other user. > > This is how I'm doing it. I have set up a virtual machine using Vagrant and my source directory is on the host machine, mounted using NFS. The default VirtualBox shared folder file system can't handle hard links, so that's the reason for the change. Make all works just fine without sudo. Make doc fails when texi2html wants to write in the out-www folders and the various subfolders (contributors, extending and the like). Other processes have created those folders and written to them, so the issue seems only to be with texi2html. I first thought that it may be an issue because the user that runs in the vm is not the same as the one that owns the folder on the host. But when I check the files and folders that were created, they all have the expected owner, i.e. the one that started the vm. This by the way also goes for files created by sudo on the guest. -- Sven Axelsson ++[>++>+++>++>++ ><-]>.+..>+.>+.<<-.>>+.>.<<. +++.>-.<<++.>>.<++.>>>++..>>.<. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
Sven Axelsson: > It appears as if texi2html needs word-writeable folders to work. Thus I > took the simple route of running make doc (and make test) under sudo. Is > that how others does it too? Nope, git clone, pull, ./autogen.sh, make all, make doc all as the same user, no problems like the one you state. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building Lilypond documentation
Here's my (very simple) Vagrant setup. Am I perhaps missing some dependencies? https://gist.github.com/svenax/8222686 -- Sven Axelsson ++[>++>+++>++>++ ><-]>.+..>+.>+.<<-.>>+.>.<<. +++.>-.<<++.>>.<++.>>>++..>>.<. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
auto two-column markup layout?
Hi all, Does anyone have a function to automatically lay out a list of markups in two columns? Bonus points for margin/width/gutter parameter control, and auto page-breaking. =) I’m doing it all manually right now, and it’s a bit frustrating… Thanks, Kieren. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
brainstorming \book and \bookpart (and more?)
Hello all, Riffing on some recent threads/discussions… I’d love to have a discussion about what can (and cannot) be done to take the current \book & \bookpart mechanism(s) to the goal line, and then come up with a list of specific feature requests (and possible bounties) to get us there. Here are some things to get the discussion started: 1. \bookpart or equivalent without page break (supporting e.g. midpage margin adjustments); 2. fully automatic page numbering intra- and inter-bookpart, with manual override capabilities. Thoughts? Other limitations or requests in this area? Cheers, Kieren. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: brainstorming \book and \bookpart (and more?)
Another discussion point: 3. \bookpartTitleMarkup (analogous to \bookTitleMarkup and \scoreTitleMarkup). Cheers, Kieren. On Jan 2, 2014, at 1:40 PM, Kieren MacMillan wrote: > Hello all, > > Riffing on some recent threads/discussions… I’d love to have a discussion > about what can (and cannot) be done to take the current \book & \bookpart > mechanism(s) to the goal line, and then come up with a list of specific > feature requests (and possible bounties) to get us there. > > Here are some things to get the discussion started: > > 1. \bookpart or equivalent without page break (supporting e.g. midpage margin > adjustments); > > 2. fully automatic page numbering intra- and inter-bookpart, with manual > override capabilities. > > Thoughts? Other limitations or requests in this area? > > Cheers, > Kieren. > ___ > lilypond-user mailing list > lilypond-u...@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Suggestion about input languages
Dear developers,
[tl;dr: how about ISO language codes for input language selection?]
some time ago, I suggested to add French ("français") to the list of
note-name languages as an alias to "italiano". This is the current
state, "español" was also added.
The discussion back then was about some inconsistencies:
- the language for commands is English, these keywords are in different
languages:
\language "deutsch"
^ English ^ German
- problem: "français" needs a utf8 char ç
- "espanol" is a valid note-name language, "francais" isn’t
*Summary*: special characters are needed for some languages to spell
them correctly, this is because no international system is used here
Now I have a new suggestion:
We could use ISO 639-1 language codes for the input language
specification: http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
Advantages:
- international standard
- widely adopted and known for language selection
- the user language doesn't matter (no need to decide between French and
français)
- no special characters (plain ascii)
- it is short
The current language names could be kept for backwards compatibility.
This would mean, the current alias list
scm/define-note-names.scm:968
would be extended like this:
- '((espanol español)
- (italiano français)))
+ '((espanol español)
+ (italiano français)
+ (nederlands nl)
+ (catalan ca)
+ (deutsch de)
+ (english en)
+ (espanol es)
+ (italiano fr)
+ (italiano it)
+ (norsk nb)
+ (norsk nn)
+ (portugues pt)
+ (suomi fi)
+ (svenska sv)
+ (vlaams vls))) ; unclear*
* I have no good proposition for vlaams as the language code is nl like
Dutch/nederlands. The ISO 639-2 code is vls, another option might be nl-BE?
What do you think?
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: regtest for new glyphs necessary?
Marc Hohl hohlart.de> writes: > I am about to upload a patch for these four glyphs within the next > days, but I wanted to ask whether a new (or enhanced existing) > regtest is necessary for this type of enhancement? They could conceivably be broken accidentally, by a mistaken change to our .mf files or a metafont bug, so a regression test is useful. LilyPond probably has too many tests, but you could add to 'clefs.ly' ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
