Patch review for fret diagrams

Carl D. Sorensen byu.edu> writes: > > Happy new year, all! > > I've completed a major patch of fret diagrams, adding a new orientation and > cleaning up a bunch of ugly stuff in the code. > > Please review the patch at > http://codereview.appspot.com/11857/diff/1/3 > > Thanks, > > Carl > I

Re: ideas for Google Summer of Code

Anne Ghisla gmail.com> writes: > > Hello all, > > I started working with LilyPond some time ago and I am impressed of its high > quality output and richness of features. > I was wondering if I could propose a project for Google Summer of Code [1], > since I have participated last year and it

Re: [PATCH] Add chordChanges capability to FretBoard grobs

I have a new patch available. I responded to all comments, plus added a NEWS entry and put a snippet in the docs. Please comment: Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists

Re: Suggestion for diatonic chordRootNames function

Johannes Asal gmx.de> writes: > > What do you think about that as a first step: > > (define-public (note-name-≥roman-markup pitch root) > "Return roman markup for PITCH relative to ROOT." > (make-line-markup >(list > (make-simple-markup > (vector-ref #("I" "II" "III" "IV" "V" "

Re: Debugging/showing internal stuff?

Nicolas Sceaux free.fr> writes: > > - test.ly - > #(display (current-module)) > #(top-repl) > --- > > ==> > > # > guile> (current-module) > # > guile> > > So after invoking (top-repl), we are not the same module as the one > used in the input file. That's why `parser'

Re: Bug or feature?

David Kastrup gnu.org> writes: > When typesetting the following, in the transposed variant > some chord diagrams are pretty, some chord diagrams are absurd. Fixed in git. Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.g

Re: Debugging/showing internal stuff?

Nicolas Sceaux free.fr> writes: > you can try that: > > -foo.ly- > #(module-define! (resolve-module '(guile-user)) 'lilypond-module > (current-module)) > #(top-repl) > > > guile> (set-current-module lilypond-module) > # > guile> parser > #) > > > guile> (display-schem

Re: PATCH -- Dashed Slurs

Carl D. Sorensen byu.edu> writes: > > Please review my patch for dashed slurs on rietveld: > > http://codereview.appspot.com/40122/show > I've revised my patch to eliminate some debug garbage that was left in the files, and to make the bezier subdivide routine work for any degree of bezier cu

Re: [PATCH] Markup commands \left-brace and \right-brace

Neil Puttock gmail.com> writes: > > Hi, > > Please review this patch here: > > http://codereview.appspot.com/8874/show Looks good! Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-deve

Re: 2.14 release plans

Graham Percival percival-music.ca> writes: > > Progress has been slow for the past month. I'd like to be able to > claim that I'll be getting more done in the next few weeks, but in > all honesty I doubt it. If anything, I'll be engaged in *more* > household projects, not less. > > With that

Re: [PATCH]: -- Revised tablature implementation

Carl D. Sorensen byu.edu> writes: > > Please review Mark Hohl's patch for improved tablature. > > It's available at > > > This is a second request for feedback on Marc's patch. Tablature users are anxious for this to become part of LilyPond. Thanks,

Snippets in doc compile different from stand-alone

I'm trying to finish up the revisions to the autobeaming code. I've got it working just fine when I compile from the command line. But when snippets are included in the docs, they seem to compile different than from the command line. I'll take a snippet that's in the docs (not one that's include

Re: Snippets in doc compile different from stand-alone

On 7/10/09 3:58 PM, "Carl Sorensen" wrote: > > > > On 7/10/09 3:43 PM, "Graham Percival" wrote: > >> On Fri, Jul 10, 2009 at 03:37:36PM -0600, Carl Sorensen wrote: >>> Is there a different version of LilyPond called when make doc is

Re: [PATCH] Improvements for the SVG backend

On 7/10/09 3:33 PM, "Patrick McCarty" wrote: > On Mon, Jul 6, 2009 at 9:41 PM, Patrick McCarty wrote: >> Hello, >> >> I have posted another patch to Rietveld: >> >> http://codereview.appspot.com/91075/show >> >> It addresses all of the "Bugs with solutions" listed on the wiki page: >> >> h

Re: improving NR B.6 "The Feta Font"

On 7/10/09 1:51 PM, "Mark Polesky" wrote: > I was having trouble finding glyphs in NR B.6, so I reorganized > things. I'm not saying I used the best approach, but I think this > would be an improvement. Any comments or suggestions? A better > approach? See the attached file. I like it a lot.

Re: Snippets in doc compile different from stand-alone

On 7/10/09 4:13 PM, "Graham Percival" wrote: > On Fri, Jul 10, 2009 at 03:58:29PM -0600, Carl Sorensen wrote: >> >> When run from the command line, the output that results is attached as >> FromCommandLine.png. > > Are you running > lilypond foo.

Re: Snippets in doc compile different from stand-alone

On 7/10/09 4:58 PM, "John Mandereau" wrote: > 2009/7/11 Carl Sorensen : >> Ahh -- there is a clue here that I hadn't noticed before.  The comments in >> the code are different in the snippet from  rhythms.itely and the doc >> output. >> >> That

Re: [PATCH] Improvements for the SVG backend

On 7/10/09 5:32 PM, "Graham Percival" wrote: > On Fri, Jul 10, 2009 at 04:25:00PM -0700, Patrick McCarty wrote: >> On Fri, Jul 10, 2009 at 4:19 PM, Graham >> Percival wrote: >>> And by "could you produce instructions", Carl means "could you >>> patch AU 3.2.2, since evidently the instructions

Re: [PATCH] Improvements for the SVG backend

On 7/10/09 5:52 PM, "Patrick McCarty" wrote: > On Fri, Jul 10, 2009 at 4:47 PM, Carl Sorensen wrote: >> >> On 7/10/09 5:32 PM, "Graham Percival" wrote: >> >>> On Fri, Jul 10, 2009 at 04:25:00PM -0700, Patrick McCarty wrote: >>>&g

Re: improving NR B.6 "The Feta Font"

here. You find every last > little mistake, even in the most complicated situations. It's > great. > > Carl Sorensen wrote: >> I like it a lot. >> >> Could the appendix be replaced with multiple snippets, each of >> which includes the main .ly you'

Obsolete snippets

What does one do when a snippet that is in the docs becomes obsolete? The docs tag can be removed from the LSR. The snippet reference can be removed from the English .itely file. Does one then go and remove the snippet reference from the translated .itely files as well? Thanks, Carl ___

Re: Snippets in doc compile different from stand-alone

On 7/10/09 6:38 PM, "John Mandereau" wrote: > 2009/7/11 Graham Percival : >> Similiar stuff has happened to me, but since it involves the build >> process, I never bothered trying to track down the problem.  I >> just do a make clean, make web-clean (that's probably doc-clean >> now), and rege

Re: improving NR B.6 "The Feta Font"

On 7/11/09 12:29 PM, "Mark Polesky" wrote: > > > Carl Sorensen wrote: > >> @subsection Shaped Notes >> >> @lilypond >> \include font-table.ly >> #(display-font-table 'shape-notes) >> @end lilypond >> >> @subse

Re: proposal for doc+web sources

On 7/11/09 4:21 AM, "Graham Percival" wrote: > Here's my proposal for the source/makefile view of documentation. > (this is the big argument one) > In general, I think these proposals are reasonable. > > My understanding is that linking between texinfo manuals is easier > if the main files

Re: [PATCH] Improvements for the SVG backend

On 7/11/09 3:08 PM, "Patrick McCarty" wrote: > On Fri, Jul 10, 2009 at 5:19 PM, Carl Sorensen wrote: >> >> On 7/10/09 5:52 PM, "Patrick McCarty" wrote: >>> >>> This is what I do (on Linux): >>> >>> 1.) Move all of the

Syntax changes in translated documentation

OK, so I'm making syntax changes in autobeaming for LilyPond. I've worked through rhythms.itely and input/lsr (and I'll soon work through input/regression). Now my make doc is failing because of snippets in /de/user/rhythms.itely that use the old syntax and have, in many cases, been removed from

PATCH: Consolidate autobeaming to one property that controls it

At *long* last I have completed my changes to the autobeaming rules. The rietveld patch set is available at: http://codereview.appspot.com/88155 The objective is to get all information that affects autobeaming in a single place, so a single override will adjust the autobeam settings. Autobeam

Re: PATCH: Consolidate autobeaming to one property that controls it

On 7/11/09 6:07 PM, "Jonathan Kulp" wrote: > Carl Sorensen wrote: >> At *long* last I have completed my changes to the autobeaming rules. >> >> The rietveld patch set is available at: >> >> http://codereview.appspot.com/88155 >> >>

Re: New format for autobeaming rules

On 7/12/09 11:13 AM, "n.putt...@gmail.com" wrote: > > > http://codereview.appspot.com/88155/diff/43/1044 > File Documentation/user/rhythms.itely (right): > > http://codereview.appspot.com/88155/diff/43/1044#newcode1662 > Line 1662: of the beam, e.g. @code{#'(1 . 16)}, or @code{#'*} to > ind

Re: PATCH: Consolidate autobeaming to one property that controls it

On 7/12/09 9:43 AM, "Neil Puttock" wrote: > 2009/7/12 Carl Sorensen : > >> I've created a second patch set with the whitespace removed (along with >> automatic removal of whitespace from the lines of the files that weren't >> part of the patch)

Re: New format for autobeaming rules

On 7/12/09 11:13 AM, "n.putt...@gmail.com" wrote: > > http://codereview.appspot.com/88155/diff/43/1045 > File > input/lsr/automatic-beams-two-per-two-in-4-4-or-2-2-time-signature.ly > (right): > > http://codereview.appspot.com/88155/diff/43/1045#newcode1 > Line 1: %% Do not edit this file;

Re: New format for autobeaming rules

On 7/12/09 11:13 AM, "n.putt...@gmail.com" wrote: > > http://codereview.appspot.com/88155/diff/43/1045 > File > input/lsr/automatic-beams-two-per-two-in-4-4-or-2-2-time-signature.ly > (right): > > http://codereview.appspot.com/88155/diff/43/1045#newcode1 > Line 1: %% Do not edit this file;

Re: Obsolete snippets

On 7/12/09 11:21 AM, "Neil Puttock" wrote: > 2009/7/11 Carl Sorensen : > >> Does one then go and remove the snippet reference from the translated .itely >> files as well? > > This is what I've always done, otherwise you're left with broken >

Broken make

So I've worked on all the translations of rhythms.itely (english, es, fr, de) for the new changes to autobeaming. I ran make doc, and everything worked OK until we got to mass-link.py. Given the error message, it appears there's something wrong with the makefile. cp -u is called, and there is no

Re: Broken make

On 7/13/09 10:55 PM, "Matthias Kilian" wrote: > On Mon, Jul 13, 2009 at 09:18:58PM -0700, Patrick McCarty wrote: >> I found this interesting link: >> >> https://savannah.cern.ch/bugs/?35556 >> >> It looks like "cp -u" will only work under Linux. John added the "-u" >> flag earlier this mont

Re: Snippets in doc compile different from stand-alone

On 7/10/09 3:37 PM, "Carl Sorensen" wrote: > I'm trying to finish up the revisions to the autobeaming code. > > I've got it working just fine when I compile from the command line. > > But when snippets are included in the docs, they seem to compile dif

Re: New format for autobeaming rules

I've posted a new patch set on Rietveld which I think is a release candidate. It has changes in all the translated rhythms.itely files so that all of the docs build properly. It has the revised snippets in input/new added to the repository. It has cleaned up all of the issues that Neil identifie

Re: Adding note color handling to musicxml2ly

On 7/13/09 1:35 AM, "Bret Aarden" wrote: > > > I've written a music search tool that exports MusicXML and colors the > matching notes, and I'd like those colors to show up in LilyPond > typesetting. > > There is no doubt a much more elegant way to do this, but the included > patch works for

Re: Broken make

On 7/14/09 3:33 PM, "John Mandereau" wrote: > Please junk (without blindly reverting) those -u flags I added. I've > started offline cleaning up translated docs generation, one planned > feature is HTML and PDF output of translations directly in > Documentation/user, so this multiple css file

Re: accessing accidentals with \tweak

On 7/14/09 2:15 PM, "Mark Polesky" wrote: > > > In NR 5.3.4 "The \tweak command", it says this: > > Notably the \tweak command cannot be used to modify stems, beams > or accidentals, since these are generated later by note heads, > rather than by music elements in the input stream. > > htt

Re: Snippets in doc compile different from stand-alone

On 7/14/09 4:11 PM, "Neil Puttock" wrote: > 2009/7/14 Carl Sorensen : > >> Can we get something in the CG about this problem, and how to run >> update-snippets.py to fix things, or at least a statement about the easiest >> way to solve the problem? >

Re: PATCH: Consolidate autobeaming to one property that controls it

On 7/14/09 4:08 PM, "Neil Puttock" wrote: > 2009/7/12 Carl Sorensen : > >> I don't know.  I didn't write displayLilyMusic; that was Nicolas IIRC.  I do >> know that \time 3/4 executes those functions.  It's really easy to go >> forward in t

Re: New format for autobeaming rules

On 7/14/09 3:57 PM, "n.putt...@gmail.com" wrote: > Carl, I haven't commenting on them directly, but there are quite a few > indentation errors in the .scm files. Thanks for noticing. I went through and fixed them up. > > > http://codereview.appspot.com/88155/diff/95/1147 > File Documentat

Re: New format for autobeaming rules

On 7/15/09 9:30 AM, "John Mandereau" wrote: > Le mercredi 15 juillet 2009 à 07:43 -0600, Carl Sorensen a écrit : >> On 7/14/09 3:57 PM, "n.putt...@gmail.com" wrote: >>> http://codereview.appspot.com/88155/diff/95/1147#newcode69 >>> Line 69: se

Re: New format for autobeaming rules

On 7/15/09 3:45 PM, "n.putt...@gmail.com" wrote: > > > http://codereview.appspot.com/88155/diff/2005/3086 > File scm/music-functions.scm (right): > > http://codereview.appspot.com/88155/diff/2005/3086#newcode519 > Line 519: (make-simultaneous-music output) > This breaks all the Festival reg

Re: Obsolete snippets

On 7/15/09 6:30 PM, "Francisco Vila" wrote: > 2009/7/15 John Mandereau : >> Le lundi 13 juillet 2009 à 06:07 -0600, Carl Sorensen a écrit : >>> So, in order to not have broken documentation, I need to eliminate old file >>> referenes, and old in-line snippe

Re: Snippets in doc compile different from stand-alone

On 7/15/09 9:48 AM, "John Mandereau" wrote: > Le mardi 14 juillet 2009 à 16:21 -0600, Carl Sorensen a écrit : >> Hmm -- I read through the CG and missed it. Now that I know what I'm >> looking for, I see where it is. I'll add something to the CG. >

Re: Snippets in doc compile different from stand-alone

On 7/16/09 9:31 AM, "John Mandereau" wrote: > >> So, just to make sure I'm clear on this, I'd like to propose the following >> for addition to the CG: >> >> When a snippet is changed or deleted from the english documentation, the >> same change (or deletion) should be applied to all translat

PATCH: Improved tablature support

Marc Hohl has completed a patch for improved tablature support. It is available for review at: http://codereview.appspot.com/95059 Please review and comment. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/

Regression test information

I'd like permission to move the information on regression testing from make test-baseline and make check from the AU to the CG (There's a placeholder there already; section 7). Any concerns about doing this? Carl ___ lilypond-devel mailing list lily

Re: PATCH: Improved tablature support

On 7/16/09 4:00 PM, "Jonathan Kulp" wrote: > Carl Sorensen wrote: >> Marc Hohl has completed a patch for improved tablature support. It is >> available for review at: >> >> http://codereview.appspot.com/95059 >> >> Please review and commen

Re: PATCH: Improved tablature support

On 7/16/09 9:56 AM, "Carl Sorensen" wrote: > Marc Hohl has completed a patch for improved tablature support. It is > available for review at: > > http://codereview.appspot.com/95059 > > Please review and comment. > > Thanks, Marc, Here are some comment

Re: PATCH: Improved tablature support

On 7/16/09 5:54 PM, "Jonathan Kulp" wrote: > Carl Sorensen wrote: >> >> So, while I asked Marc to provide documentation, I didn't require it. I >> did, however, require regtests. >> >> As soon as we get the patch applied, we can ask one of

Re: Regression test information

On 7/17/09 12:57 AM, "Graham Percival" wrote: > On Thu, Jul 16, 2009 at 10:11:50AM -0600, Carl Sorensen wrote: >> I'd like permission to move the information on regression testing from make >> test-baseline and make check from the AU to the CG (There's a pl

Re: PATCH: Improved tablature support

On 7/17/09 2:13 AM, "Marc Hohl" wrote: > Carl Sorensen schrieb: >> >> On 7/16/09 9:56 AM, "Carl Sorensen" wrote: >> >> >> 3) Is it necessary (or desirable) to have both \deadNote and >> \deadNoteOn..\deadNoteOff? Unless a wh

Re: accessing accidentals with \tweak

On 7/15/09 4:19 PM, "Mark Polesky" wrote: > Mark Polesky wrote: > > Okay, I figured out a way around this -- by passing an property-alist to > the 'before-line-breaking tweak, I was able to get all the accidental > modifications done in one tweak (see "modify-accidental" below). I've > also i

Re: PATCH: Improved tablature support

On 7/17/09 10:16 AM, "Marc Hohl" wrote: > Carl Sorensen schrieb: >> >> Right, so we *must* have the function mode. Do we need the setting mode as >> well? I don't feel strongly about eliminating it, but I don't feel strongly >> about keep

Size of test output binaries has doubled

In preparing information on regression testing for the Contributors' Guide, I happened to check the downloadable regression test results at http://lilypond.org/download/binaries/test-output/ I noticed that prior to 2.13.2 the test results were approximately 70-80 MB. For 2.13.2 and 2.13.3, the r

Re: Understanding the processing model

On 7/19/09 12:58 PM, "Graham Percival" wrote: > On Sun, Jul 19, 2009 at 08:31:59AM -0700, Mark Polesky wrote: >> >> (forwarded from -user) >> >> Martin Hosken wrote: >>> Is there any documentation that explains more of the internal workings >>> of lilypond. I'm looking for something that exp

Re: PATCH: Improved tablature support

On 7/20/09 3:09 PM, "Mark Polesky" wrote: > > > Marc Hohl wrote: >> Hm, sounds kind of morbid to me, calling a note "dead", but since >> I am not a native english speaker, I cannot judge this from a neutral >> point of view. >> Do you think that there will arise big problems with these comma

Re: PATCH: Improved tablature support

On 7/20/09 3:09 PM, "Mark Polesky" wrote: > > > Marc Hohl wrote: >> Hm, sounds kind of morbid to me, calling a note "dead", but since >> I am not a native english speaker, I cannot judge this from a neutral >> point of view. >> Do you think that there will arise big problems with these comma

PATCH: Re: New format for autobeaming rules

I'm getting ready to push the new autobeaming code. Are there any more comments before I do so? http://codereview.appspot.com/88155 Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond

Re: Size of test output binaries has doubled

On 7/19/09 3:07 AM, "Graham Percival" wrote: > On Sat, Jul 18, 2009 at 09:14:40PM -0600, Carl Sorensen wrote: >> In preparing information on regression testing for the Contributors' Guide, >> I happened to check the downloadable regression test results at >&

inverse of unsmob_context

I'm trying to avoid code duplication as I work with fixing the beam-grouping code. I'm defining some procedures that can be called both from c++ and scheme to get grouping rules from the context property. In order to call from scheme, I need to have context be a smob. In my call from c++, I have

Re: inverse of unsmob_context

Carl Sorensen byu.edu> writes: > > SCM my_context = smob_context(Context *context) > > Does this function exist? Sorry for the noise -- I found context->self-scm() which does what I need. Thanks, Carl ___ lilypond-

Broken build on my system

Somehow I've broken the build on my system. It used to work, but now it fails when it tries to build the lexer. I've used git to go back to known-good source trees, e.g. git checkout 062046e74d6995b99bb7669e4cd6490ba8b18656 which I have built before. But now, make clean make exits with the

Re: Broken build on my system -- SOLVED -- MAC OSX problem

Carl Sorensen byu.edu> writes: > > Somehow I've broken the build on my system. It used to work, but > now it > fails when it tries to build the lexer. > It turns out that somehow my config.make got rebuilt. When that happened, the FLEXLEXER_FILE variable wen

Please remove docs tags from snippets

Dear LSR editors (Neil or Valentin, IIRC), Please remove the docs tags from the following snippets: Specifying context with beatGrouping Using beatLength and beatGrouping They will be obsolete for 2.13.4 and cause problems in making documentation. This shows a very interesting problem. We onl

Re: Please remove docs tags from snippets

On 7/23/09 9:47 PM, "Graham Percival" wrote: > On Thu, Jul 23, 2009 at 08:55:21PM -0600, Carl Sorensen wrote: >> Please remove the docs tags from the following snippets: >> >> Specifying context with beatGrouping >> >> Using beatLength and beat

Re: New format for autobeaming rules

On 7/22/09 4:15 PM, "joenee...@gmail.com" wrote: > I think this is pretty much ready to commit > > > http://codereview.appspot.com/88155/diff/3101/4032 > File lily/beam-scheme.cc (right): > > http://codereview.appspot.com/88155/diff/3101/4032#newcode2 > Line 2: beam-scheme.cc -- Retrieving

Re: tabs vs. spaces in source code

On 7/24/09 11:32 PM, "Mark Polesky" wrote: > > > Graham Percival wrote: > >> On Fri, Jul 24, 2009 at 06:15:31PM -0700, Mark Polesky wrote: >>> Thanks, Neil. My editor does confusing things with tabs. >>> I hate them. Who would object if I just started running >>> tabs->spaces on the source

Re: tabs vs. spaces in source code

On 7/25/09 10:58 AM, "Mark Polesky" wrote: > > > ...tabs in the source code... > > Werner Lemberg wrote: >> I dislike them, too, but there are many editors which handle >> them just fine. I don't see a problem here. > > But would you

Re: tabs vs. spaces in source code

On 7/25/09 11:47 AM, "Mark Polesky" wrote: > > > Carl Sorensen wrote: >> No, Jan was not in favor of it unless it became a standard for >> GNU coding. Hence the comment on "first making it a standard" >> (i.e., a GNU standard) and "

Re: RFC: new vertical layout engine

On 7/25/09 12:01 PM, "Mark Polesky" wrote: > > > Kieren MacMillan wrote: >> Excellent! >> Then I nominate @frenchspacing (i.e., single-spaced sentences) >> be used for the English docs, consistent with the overwhelming >> majority of modern English typographic style guides and >> practice...

Weird make error

I'm trying to build lilypond after doing a "make distclean". make runs through the creation of the .o and the executable. It finishes the fonts, then when it starts compiling the snippets it ends with: make PACKAGE=LILYPOND package=lilypond -C J.S.Bach all && make PACKAGE=LILYPOND package=lilyp

How can I use git to help me merge a patch with the new directory structure

As you're aware, I've been working on a patch for autobeaming. It affects c++, scheme, and documentation files. Now I want to apply the patch to master. But the problem is that all of the documentation files have moved to Documentation/ISOLANG/notation instead of Documentation/ISOLANG/user So

Re: Feature request: 'line' articulation

On 7/26/09 1:33 AM, "Maximilian Albert" wrote: > 2009/7/25 Werner LEMBERG : > >> I don't object to add it to the font, so please add it as a feature >> request. I think that Werner was saying the feature request is to add a glyph to the font. But while we wait for that to happen, to add a d

Re: Weird make error

On 7/26/09 9:51 AM, "John Mandereau" wrote: > Hi Carl, > Le samedi 25 juillet 2009 à 18:14 -0600, Carl Sorensen a écrit : >> make runs through the creation of the .o and the executable. It finishes >> the fonts, then when it starts compiling the snippets it

Re: How can I use git to help me merge a patch with the new directory structure

On 7/26/09 11:35 AM, "Johannes Schindelin" wrote: > Hi, > > On Sat, 25 Jul 2009, Carl Sorensen wrote: > >> As you're aware, I've been working on a patch for autobeaming. >> >> It affects c++, scheme, and documentation files. >> >

Re: How can I use git to help me merge a patch with the new directory structure

On 7/26/09 11:35 AM, "John Mandereau" wrote: > Le samedi 25 juillet 2009 à 22:37 -0600, Carl Sorensen a écrit : >> Any git gurus out there who have an idea of how I can do this without having >> to manually apply patches made between the files in the differen

Re: How can I use git to help me merge a patch with the new directory structure

On 7/27/09 2:45 AM, "Johannes Schindelin" wrote: > Hi, > > On Sun, 26 Jul 2009, Carl Sorensen wrote: > >> On 7/26/09 11:35 AM, "Johannes Schindelin" >> wrote: >> >>> On Sat, 25 Jul 2009, Carl Sorensen wrote: >>>

Re: Lilypond Syntax Development and 3.0

On 7/27/09 4:22 AM, "Graham Percival" wrote: > I was going to hold off introducing this until the 3-4 major > development issues had been sorted out, but the third time I found > myself writing "yes, I have a plan for this, but I'm going to wait > a bit before discussing it", I decided I was b

Make broken on master

Thanks to all who helped me get git working for the autobeam patches. I think I've got everything merged properly. When I tried make, it got through rhythms.itely (which was were all the doc changes I made were located). But it failed later on: Compiling /Users/Carl/lilypond-working/Documenta

Re: Make broken on master

On 7/27/09 8:15 AM, "John Mandereau" wrote: > Le lundi 27 juillet 2009 à 07:36 -0600, Carl Sorensen a écrit : >> When I tried make, it got through rhythms.itely (which was were all the doc >> changes I made were located). But it failed later on: > > Whi

Re: the "separate, but integrated" website proposal

On 8/4/09 4:00 AM, "John Mandereau" wrote: > Le mardi 04 août 2009 à 01:12 -0700, Graham Percival a écrit : > > > Yes, even power users could run lilypond and output-distance on entire > input file directories and detect changes in formatting. This is a goal > for 2.14, or more reasonnably

Re: Problem with VerticalAlignment

On 8/4/09 5:49 AM, "Graham Percival" wrote: > On Tue, Aug 04, 2009 at 09:13:40PM +1000, Cameron Horsburgh wrote: >> I'm having trouble with a brand new clone of the git repo. Running >> lilypond on even the simplest of files generates this error: > >> | programming error: no VerticalAlignment

Re: Problem with VerticalAlignment

On 8/4/09 8:02 PM, "Joe Neeman" wrote: > On Tue, 2009-08-04 at 19:02 -0600, Carl Sorensen wrote: >> >> >> On 8/4/09 5:49 AM, "Graham Percival" wrote: >> >>> On Tue, Aug 04, 2009 at 09:13:40PM +1000, Cameron Horsburgh wrote: >&g

Re: PATCH: Improved tablature support

On 8/5/09 2:44 AM, "Trevor Daniels" wrote: > Carl, Marc > > After the long discussion about naming the > new cross-head function and associated predefs > I see you have retained deadNote as the base > name. > > I thought the outcome of the discussion > was to use xHead or crossHead for the b

Re: PATCH: Improved tablature support

On 8/5/09 7:22 AM, "Trevor Daniels" wrote: >> >> In the meantime, we can move forward on tablature. >> >> As I see it, the current decision causes problems only if we were >> to change >> to xHead in the future and eliminate deadNote. And I see no plans >> in the >> future to eliminate dead

Regression in docs: Output-suffix does not work as documented in AU 3.2.1

> I am top posting. This is an example of something that should be sent to lilypond-devel, rather than to the frogs list. There are many developers who are not on the frogs list. Therefore, I've forwarded this to the -devel list. Thanks, Carl Sorensen On 8/5/09 5:12 PM, "Ian

Re: PATCH: Improved tablature support

On 8/5/09 7:19 AM, "Trevor Daniels" wrote: > > > Carl Sorensen wrote Wednesday, August 05, 2009 1:42 PM > >> If we decide to use this same function for the general case of >> switching to >> a cross-shaped notehead, then we will redefine it to eith

Re: the "r" in "git pull -r"

On 8/7/09 8:45 PM, "Patrick McCarty" wrote: > On Fri, Aug 07, 2009 at 07:34:01PM -0700, Mark Polesky wrote: >> >> Regarding CG 1.2.2: >> http://kainhofer.com/~lilypond/Documentation/contributor/Update-command.html >> >> What does "-r" do in "git pull -r"? I don't see "-r" >> listed as an opt

Re: Automatic accidentals: voice/staff should be set separately

Frederic, On 8/8/09 12:01 PM, "Frédéric Bron" wrote: > Hi folks, > > I refer to that portion of the documentation: > http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Displaying-pitches#A > utomatic-accidentals > > I think that the fact that automatic accidentals should apply at voice

Re: Changing autobeaming for 4/4 time

On 8/9/09 1:56 PM, "Trevor Daniels" wrote: > > > Patrick McCarty wrote Sunday, August 09, 2009 3:36 AM > > >> On Sat, Aug 08, 2009 at 07:21:42PM -0700, Patrick McCarty wrote: >>> >> >> Hmm, I just realized that the inconsistency still exists, even >> with my >> patch. Here's an example:

Re: the "r" in "git pull -r"

On 8/9/09 3:45 PM, "John Mandereau" wrote: > Le samedi 08 août 2009 à 13:55 -0600, Carl Sorensen a écrit : >> As a practical matter, -r first applies the changes that were made on origin >> (since your branch was checked out), then applies your changes on top of th

Re: the "r" in "git pull -r"

On 8/9/09 4:27 PM, "John Mandereau" wrote: > Le dimanche 09 août 2009 à 16:21 -0600, Carl Sorensen a écrit : >> Perfect! I hope I didn't mess up the translated docs too badly with my >> recent merge. > > The only risk to mess up translated docs checking

Re: parser variables persist beyond { } scope

On 8/9/09 4:23 PM, "John Mandereau" wrote: > Sorry for my initial reply to this, it was not enough to the point, I'm > trying again :-) > > Le jeudi 06 août 2009 à 09:55 -0700, Mark Polesky a écrit : >> Well, now I think we're pretty much back at Han-Wen's original >> suggestion, which was to

Re: Changing autobeaming for 4/4 time

On 8/10/09 9:14 AM, "Trevor Daniels" wrote: > > > Trevor Daniels wrote Monday, August 10, 2009 8:49 AM >> >> Neil Puttock wrote Monday, August 10, 2009 12:31 AM >> >> 2009/8/10 Patrick McCarty : >> >>> I wonder why we are seeing different beaming patterns? I think >>> all of >>> your manu

Re: Changing autobeaming for 4/4 time

OK, I've found a setting that works *pretty well*, with one bad case: \relative c'' { \overrideBeamSettings #'Score #'(4 . 4) #'end #'((* . (1 1 1 1)) ((1 . 8) . (4 4))) a8 a a a a a a a | % OK \break a16 a a8 a a a a16 a a8 a | % OK now, was wrong, should be ... a16[ a a8] a a a[

improving layout of ly-grammar.txtlocalhost/

Pushed to git. Also, during this work I was able to improve the backslash handling; I think all of the backslashes are now handled correctly. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/l

  1   2   3   4   5   6   7   8   9   10   >