Re: Markup parsing question

"Bertalan Fodor (LilyPondTool)" writes: > Thank you David, this explains me what I didn't understand. > It turned out that somehow I was looking at a bad parser.yy. Interesting. Where did you get it? -- David Kastrup ___ lilypond-devel mailing li

Re: Markup parsing question

Thank you David, this explains me what I didn't understand. It turned out that somehow I was looking at a bad parser.yy. Actually I'm not running/debugging the C code, but instead only reading it (and porting some of the parsing code to Java). Bertalan On Wed, Oct 26, 2011 at 7:26 AM, David Kast

Re: damn small lilypond

mkdir $HOME/lilypond mount none -t tmpfs $HOME/lilypond cd $HOME/lilypond wget /url/of/lilypond.sh ./lilypond.sh Figure out what packages you don't need, delete them and the .sh package, and copy everything else into a different, non-tmpfs directory in your home folder. On Oct 25, 2011 5:45 PM, "Fe

Re: Markup parsing question

"Bertalan Fodor (LilyPondTool)" writes: > Dear LilyPond devs, > > I have a problem with the LilyPond markup parsing, which prevents me > to finish my new release of LilyPondTool. > Could you help me a bit on that? > > I have this ly file > -- > dot = \markup { >   "q" \musicglyph

Re: PATCH: Countdown to 20111027

On Wed, Oct 26, 2011 at 06:26:01AM +0200, m...@apollinemike.com wrote: >Procedural question - fixes for 1990 and 1992 are in dev/staging and may >or may not be in master (I haven't checked yet this morning). If they're in staging, then that means that you want them pushed immediately. The

Re: PATCH: Countdown to 20111027

On Oct 26, 2011, at 6:20 AM, Colin Campbell wrote: > For 23:00 MDT Thursday October 27 > > Issue 1980: Patch: Sketch for in-notes. - R 5293053 > > Issue 1981: Patch: Adds Scheme function for spring constructor. - R 5306050 > > Issue 1989: Patch: Website: use external $LILYPOND_WEB_MEDIA_GIT - R

PATCH: Countdown to 20111027

For 23:00 MDT Thursday October 27 Issue 1980 : Patch: Sketch for in-notes. - R5293053 Issue 1981 : Patch: Adds Scheme function for spring

damn small lilypond

What would you do if you had to install lilypond v2.14.2 on computers running Ubuntu 10.04 (where lilypond is still v2.12), with the following limitations: - only the standard packages distributed by Ubuntu can be installed on / - the maximum space available in each /home directory is 50 MB Li

Markup parsing question

Dear LilyPond devs, I have a problem with the LilyPond markup parsing, which prevents me to finish my new release of LilyPondTool. Could you help me a bit on that? I have this ly file -- dot = \markup { "q" \musicglyph #"accordion.dot" } { c^\dot } -- When the

Re: lily-guile updates and CG: "Scheme->C interface" section. (issue 4917044)

bordage.bertr...@gmail.com writes: > Hi David, > > Could you make your own patch for the doc changes? Pushed. I have enough pending reviews, commits and patches that I don't have the nerve to do yet another hoop-jumping exercise in parallel. > And, as you mentionned, the unused function should

Re: Doc: NR Added new node for Custom Footnotes (issue 5315053)

Thanks for your work on this James! Cheers, MS http://codereview.appspot.com/5315053/diff/1/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/5315053/diff/1/Documentation/notation/input.itely#newcode1025 Documentation/notation/inp

Doc: NR Added new node for Custom Footnotes (issue 5315053)

Reviewers: , Message: There are a few non-standard indents to show more clearly the footnote syntax in the @lilypond examples. Description: Doc: NR Added new node for Custom Footnotes This is for Tracker issue 1567 Please review this at http://codereview.appspot.com/5315053/ Affected files:

Re: lily-guile updates and CG: "Scheme->C interface" section. (issue 4917044)

Hi David, Could you make your own patch for the doc changes? And, as you mentionned, the unused function should be removed. Do you want me to commit this change? Bertrand http://codereview.appspot.com/4917044/ ___ lilypond-devel mailing list lilypon

Re: Get rid of most of the insane string-tunings API (issue 5318046)

Reviewers: carl.d.sorensen_gmail.com, http://codereview.appspot.com/5318046/diff/12002/input/regression/tablature-letter.ly File input/regression/tablature-letter.ly (right): http://codereview.appspot.com/5318046/diff/12002/input/regression/tablature-letter.ly#newcode32 input/regression/tablatu

Re: Fixes all duplicate declarations of Flag #'transparent (issue 5312056)

On Oct 25, 2011, at 5:51 PM, David Kastrup wrote: > "m...@apollinemike.com" writes: > >> Re-hay Graham, >> >> None of these changes apply on top of dev/staging. I'm not sure why, >> but to not lose time, I'm doing a full doc build on master right now >> with the patch applied. If it goes thro

Get rid of most of the insane string-tunings API (issue 5318046)

LGTM. Thanks, David. Nicely done. Carl http://codereview.appspot.com/5318046/diff/12002/input/regression/tablature-letter.ly File input/regression/tablature-letter.ly (right): http://codereview.appspot.com/5318046/diff/12002/input/regression/tablature-letter.ly#newcode32 input/regression/ta

Re: Fixes all duplicate declarations of Flag #'transparent (issue 5312056)

"m...@apollinemike.com" writes: > Re-hay Graham, > > None of these changes apply on top of dev/staging. I'm not sure why, > but to not lose time, I'm doing a full doc build on master right now > with the patch applied. If it goes through, do you want me to push > the patch? Otherwise, I'll res

Re: Fixes all duplicate declarations of Flag #'transparent (issue 5312056)

On Oct 25, 2011, at 2:17 PM, m...@apollinemike.com wrote: > On Oct 25, 2011, at 2:11 PM, percival.music...@gmail.com wrote: > >> remove the version number change to 2.15.11, then please push. >> >> >> http://codereview.appspot.com/5312056/diff/1/Documentation/snippets/new/guitar-slides.ly >> Fi

Re: the latest convert-ly fiasco

David Kastrup writes: > Graham Percival writes: > >> I've lost track of where we are with convert-ly. >> >> I have just ran update-with-convert-ly. I saw a flag change from >> 2.15.10. I have pushed that. >> >> I know that there are other syntax changes that people want to >> make. Somebody m

Re: convert-ly rules to destencil Flags

"m...@apollinemike.com" writes: > On Oct 25, 2011, at 3:46 PM, David Kastrup wrote: >> >> Well, my .git/config has >> [remote "origin"] >> fetch = +refs/heads/*:refs/remotes/origin/* >> url = ssh://git.sv.gnu.org/srv/git/lilypond.git >> fetch = +refs/heads/dev/staging:refs/remotes

Re: convert-ly rules to destencil Flags

On Oct 25, 2011, at 3:46 PM, David Kastrup wrote: > "m...@apollinemike.com" writes: > >> On Oct 25, 2011, at 3:36 PM, David Kastrup wrote: >> >>"m...@apollinemike.com" writes: >> >>And now I have two extra branches (staging/HEAD and >>origin/dev/staging/HEAD) that I can't

Re: convert-ly rules to destencil Flags

"m...@apollinemike.com" writes: > On Oct 25, 2011, at 3:36 PM, David Kastrup wrote: > > "m...@apollinemike.com" writes: > > And now I have two extra branches (staging/HEAD and > origin/dev/staging/HEAD) that I can't seem to get rid of.  Any > suggestions? >

Re: convert-ly rules to destencil Flags

On Oct 25, 2011, at 3:36 PM, David Kastrup wrote: > "m...@apollinemike.com" writes: > >> And now I have two extra branches (staging/HEAD and origin/dev/staging/HEAD) >> that I can't seem to get rid of. Any suggestions? > > Use an editor on .git/config to clean up, and find and delete those >

Re: convert-ly rules to destencil Flags

"m...@apollinemike.com" writes: > And now I have two extra branches (staging/HEAD and origin/dev/staging/HEAD) > that I can't seem to get rid of. Any suggestions? Use an editor on .git/config to clean up, and find and delete those files from .git/refs that represent the bad branches. Sometime

Re: convert-ly rules to destencil Flags

On Oct 25, 2011, at 3:12 PM, David Kastrup wrote: > "m...@apollinemike.com" writes: > >> On Oct 25, 2011, at 3:06 PM, Colin Campbell wrote: >> >>> On 11-10-25 05:40 AM, m...@apollinemike.com wrote: Hey all, I tried: git remote add -ft dev/staging -m dev/staging stagin

Re: convert-ly rules to destencil Flags

"m...@apollinemike.com" writes: > On Oct 25, 2011, at 3:06 PM, Colin Campbell wrote: > >> On 11-10-25 05:40 AM, m...@apollinemike.com wrote: >>> Hey all, >>> >>> I tried: >>> >>> git remote add -ft dev/staging -m dev/staging staging >>> git://git.sv.gnu.org/lilypond.git/ That adds a separate r

Re: convert-ly rules to destencil Flags

On Oct 25, 2011, at 3:06 PM, Colin Campbell wrote: > On 11-10-25 05:40 AM, m...@apollinemike.com wrote: >> Hey all, >> >> I tried: >> >> git remote add -ft dev/staging -m dev/staging staging >> git://git.sv.gnu.org/lilypond.git/ >> >> And then >> >> git branch foo staging/dev/staging >> git c

Re: convert-ly rules to destencil Flags

On 11-10-25 05:40 AM, m...@apollinemike.com wrote: Hey all, I tried: git remote add -ft dev/staging -m dev/staging staging git://git.sv.gnu.org/lilypond.git/ And then git branch foo staging/dev/staging git checkout foo git apply foo.diff (where foo.diff are all of my changes) git commit -a

Re: the latest convert-ly fiasco

On 11-10-25 05:44 AM, David Kastrup wrote: There are several independent ones. Since their respective pushability depends on the order in which they will get applied, I don't see that changing their status to Patch-push or Patch-countdown would be appropriate. You vetoed using dev/staging for p

Re: Horizontal spacing change between 2.15.9 and 2.15.10 (regression?)

On Mon, Oct 24, 2011 at 10:13:14PM +0200, m...@apollinemike.com wrote: > If you use git bisect, you can track it down to an individual > commit. This'll help us figure out how to fix the problem. +1 instructions in the CG. - Graham ___ lilypond-devel

Re: Fixes all duplicate declarations of Flag #'transparent (issue 5312056)

On Oct 25, 2011, at 2:11 PM, percival.music...@gmail.com wrote: > remove the version number change to 2.15.11, then please push. > > > http://codereview.appspot.com/5312056/diff/1/Documentation/snippets/new/guitar-slides.ly > File Documentation/snippets/new/guitar-slides.ly (right): > > http://

Fixes all duplicate declarations of Flag #'transparent (issue 5312056)

remove the version number change to 2.15.11, then please push. http://codereview.appspot.com/5312056/diff/1/Documentation/snippets/new/guitar-slides.ly File Documentation/snippets/new/guitar-slides.ly (right): http://codereview.appspot.com/5312056/diff/1/Documentation/snippets/new/guitar-slides

Re: the latest convert-ly fiasco

Graham Percival writes: > On Tue, Oct 25, 2011 at 01:44:46PM +0200, David Kastrup wrote: >> Graham Percival writes: >> >> > I have just ran update-with-convert-ly. I saw a flag change from >> > 2.15.10. I have pushed that. >> >> There is a bunch of duplicate Flag overrides/reverts now. > > R

Re: the latest convert-ly fiasco

On Tue, Oct 25, 2011 at 01:44:46PM +0200, David Kastrup wrote: > Graham Percival writes: > > > I have just ran update-with-convert-ly. I saw a flag change from > > 2.15.10. I have pushed that. > > There is a bunch of duplicate Flag overrides/reverts now. Really? huh. I glanced at the patch

Re: the latest convert-ly fiasco

Graham Percival writes: > I've lost track of where we are with convert-ly. > > I have just ran update-with-convert-ly. I saw a flag change from > 2.15.10. I have pushed that. > > I know that there are other syntax changes that people want to > make. Somebody make a patch with all those changes

Re: the latest convert-ly fiasco

Graham Percival writes: > I've lost track of where we are with convert-ly. > > I have just ran update-with-convert-ly. I saw a flag change from > 2.15.10. I have pushed that. There is a bunch of duplicate Flag overrides/reverts now. I suppose Mike and/or translators will have to clean those u

Re: convert-ly rules to destencil Flags

On Tue, 25 Oct 2011 11:49:58 +0200, David Kastrup wrote: Graham Percival writes: On Tue, Oct 25, 2011 at 10:56:23AM +0200, David Kastrup wrote: "m...@apollinemike.com" writes: > git mikesol@mikesol-laptop:~/lilypond-git$ git rebase origin/dev/staging > fatal: Needed a single revision > in

Re: the latest convert-ly fiasco

On Tue, 25 Oct 2011 12:25:56 +0100, Graham Percival wrote: I've lost track of where we are with convert-ly. I have just ran update-with-convert-ly. I saw a flag change from 2.15.10. I have pushed that. I know that there are other syntax changes that people want to make. Somebody make a patch

Re: Patch-needs_work vs. others

On Tue, Oct 25, 2011 at 01:20:33PM +0200, David Kastrup wrote: > Graham Percival writes: > > > convenient). It should only contain patches that have completed a > > countdown, and/or patches that the author wishes to skip the > > review process. > > Shrug. That means to me that this patch is d

the latest convert-ly fiasco

I've lost track of where we are with convert-ly. I have just ran update-with-convert-ly. I saw a flag change from 2.15.10. I have pushed that. I know that there are other syntax changes that people want to make. Somebody make a patch with all those changes, for version 2.15.16. Once that patc

Patch-needs_work vs. others

On Tue, Oct 25, 2011 at 10:08:34AM +, lilyp...@googlecode.com wrote: > I think that "Needs-evidence" is sufficient for indicating the need > for discussion. The patch status would remain Patch-review (meaning > that the patch may or may not be acceptable in his current form but > is not going

Re: Uses convert-ly to update changes stemming from the creation of a Flag grob. (issue 5309059)

"m...@apollinemike.com" writes: > On Oct 24, 2011, at 11:41 PM, d...@gnu.org wrote: > >> Seems like my suggestion to update the version numbers of files with >> manual fixes (in a separate commit) in order not to get them updated >> again got lost, as well as the bit about rereading the diff for

Re: convert-ly rules to destencil Flags

Graham Percival writes: > On Tue, Oct 25, 2011 at 10:56:23AM +0200, David Kastrup wrote: >> "m...@apollinemike.com" writes: >> >> > git mikesol@mikesol-laptop:~/lilypond-git$ git rebase origin/dev/staging >> > fatal: Needed a single revision >> > invalid upstream origin/dev/staging >> >> git b

Re: convert-ly rules to destencil Flags

On Tue, Oct 25, 2011 at 10:56:23AM +0200, David Kastrup wrote: > "m...@apollinemike.com" writes: > > > git mikesol@mikesol-laptop:~/lilypond-git$ git rebase origin/dev/staging > > fatal: Needed a single revision > > invalid upstream origin/dev/staging > > git branch -r lists nothing? Anyhow: I

Re: convert-ly rules to destencil Flags

"m...@apollinemike.com" writes: > On Oct 25, 2011, at 8:36 AM, David Kastrup wrote: > >> "m...@apollinemike.com" writes: >> >>> On Oct 25, 2011, at 7:08 AM, David Kastrup wrote: >>> "m...@apollinemike.com" writes: > On Oct 24, 2011, at 5:12 PM, David Kastrup wrote: > >

Re: convert-ly rules to destencil Flags

On Oct 25, 2011, at 8:36 AM, David Kastrup wrote: > "m...@apollinemike.com" writes: > >> On Oct 25, 2011, at 7:08 AM, David Kastrup wrote: >> >>> "m...@apollinemike.com" writes: >>> On Oct 24, 2011, at 5:12 PM, David Kastrup wrote: > git fetch > git rebase origin/dev/stagin

Re: Fixes slope errors from incorrect X extents in Beam::print. (issue 5293060)

On Mon, 24 Oct 2011 22:19:41 -0700, m...@apollinemike.com wrote: Before this patch, the x_span of beams was only ever calculated between the first normal stem and last normal stem of a beam (omitting any trailing beamage on the left or right coming from breaks and/or stemlets). If it has a