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: SVG backend: On-the-fly conversion of Emmentaler/Aybabtu glyphs to paths

On Sat, Jul 25, 2009 at 7:03 PM, wrote: > On 2009/07/24 23:30:00, Patrick McCarty wrote: > >> The new code uses a generalized regular expression that will match a >> element with attributes in any order. >> The code is slower now, I think due to the complexity of the new regular >> expression.  I

Re: Contrib Guide not built

Hi Jon, On Sat, Jul 25, 2009 at 5:57 PM, Jonathan Kulp wrote: > After pulling the latest changes, the contributor guide pdf version is not > building.  The html big-page and all other docs are built properly with > their new names. I looked through the build log and can't find any errors > saying

Re: SVG backend: On-the-fly conversion of Emmentaler/Aybabtu glyphs to paths

It seems as though rietveld wants to send my code-comments and my reply-to-comments comments in two separate emails. Sorry for the noise. http://codereview.appspot.com/96083/diff/1015/20 File lily/pango-font.cc (right): http://codereview.appspot.com/96083/diff/1015/20#newcode354 Line 354: bool

Re: SVG backend: On-the-fly conversion of Emmentaler/Aybabtu glyphs to paths

On 2009/07/24 23:30:00, Patrick McCarty wrote: On 2009/07/21 18:43:10, joeneeman wrote: > I think it would be helpful if you gave an example or 2 of the sort of string > you expect to match here. I'm a bit worried also about the fact that you require > the attributes to be in a specific order

Contrib Guide not built

After pulling the latest changes, the contributor guide pdf version is not building. The html big-page and all other docs are built properly with their new names. I looked through the build log and can't find any errors saying why the CG pdf wouldn't get built. Jon -- Jonathan Kulp http://www.j

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

Re: RFC: new vertical layout engine

Kieren MacMillan wrote Saturday, July 25, 2009 6:30 PM Thanks for the reference — for subsequent thread-followers, I also recommend Indeed, I just see that @frenchspacing is only used for French and Japanese (the latter only partially).

Re: ppppp but no fffff

2009/7/25 Jonathan Wilkes : > There's something in NR 3.5.5 that describes how to control MIDI behavior > for (custom) dynamics.  But if I just use make-dynamic-script to print out > "ff" or "z" in the score, and I don't use any other dynamics, > it gets softer when the custom dynamic is u

Re: Docs and new web site reorganization steps

On Sat, Jul 25, 2009 at 1:16 PM, Patrick McCarty wrote: > On Sat, Jul 25, 2009 at 1:05 PM, Patrick McCarty wrote: >> On Sat, Jul 25, 2009 at 09:25:01PM +0200, John Mandereau wrote: >>> Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit : >>> > Step 1) Move all Texinfo documentation i

Re: [PATCH] IR 3 Backend: More auto-sorting.

2009/7/25 Mark Polesky : > In the meantime, I'll wait for someone to verify the > revised patch. + (sort (map symbol->string (hashq-ref iface->grob-table

Re: Docs and new web site reorganization steps

On Sat, Jul 25, 2009 at 1:05 PM, Patrick McCarty wrote: > On Sat, Jul 25, 2009 at 09:25:01PM +0200, John Mandereau wrote: >> Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit : >> > Step 1) Move all Texinfo documentation in user/ and topdocs/ one >> > directory higher (done in my wo

Re: Docs and new web site reorganization steps

On Sat, Jul 25, 2009 at 09:25:01PM +0200, John Mandereau wrote: > Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit : > > Step 1) Move all Texinfo documentation in user/ and topdocs/ one > > directory higher (done in my working tree), in translations too. > > > > Step 2) Update all

Re: tabs vs. spaces in source code

Le samedi 25 juillet 2009 à 09:58 -0700, Mark Polesky a écrit : > But even in such cases, as long as my tab-width matches the > tab-widths in the source, tabs2spaces should be fine. Is it > correct to say that git (or savannah) translates all tabs to 8 > spaces without exception? Git doesn't trans

Re: RFC: new vertical layout engine

>> 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... >> Seconder? Opposed? Abstentions? > > Don't we want to be following the GNU Coding Standards?

Re: RFC: new vertical layout engine

>> Indeed, I just see that @frenchspacing is only used for French and >> Japanese (the latter only partially). It should be activated for all >> languages except, perhaps, English. Note that I don't care what you >> native speakers actually decide for English > > Excellent! Then I nominate @fre

Re: how to view console on Windows?

Jonathan Kulp wrote: >>You can run it from the dos cmd prompt. Just do "lilypond >>foobar.ly" and it should work. Yes it does... thank you, that helps. But shouldn't the output be sent to the log file? I wish it were. Does anyone know how to do that? Thanks. - Mark _

Re: ppppp but no fffff

> http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00417.html Oh, I haven't played around with make-dynamic-script yet. I guess it's not necessary to have a pre-defined command for "pp" and the like, since it's so easy to add these extreme dynamics as needed. Thanks for the l

Re: how to view console on Windows?

You can run it from the dos cmd prompt. Just do "lilypond foobar.ly" and it should work. Jon On Sat, Jul 25, 2009 at 2:02 PM, Mark Polesky wrote: > > This was never resolved: > http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00434.html > > I'm on Windows, and I can see the console

Re: [PATCH] IR 3 Backend: More auto-sorting.

2009/7/25 Mark Polesky : > 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 docs? I think we should have > a strict no-tabs rule. And I'm in good company: > http://lists.gnu.org/archive/html/lilypond-deve

Re: Docs and new web site reorganization steps

Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit : > Step 1) Move all Texinfo documentation in user/ and topdocs/ one > directory higher (done in my working tree), in translations too. > > Step 2) Update all build and maintenance scripts and the CG. > At the end of this step docs

Re: Feature request: 'line' articulation

2009/7/24 Werner LEMBERG : > I don't object to add it to the font, so please add it as a feature > request. Here goes: http://code.google.com/p/lilypond/issues/detail?id=822 Regards, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http

how to view console on Windows?

This was never resolved: http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00434.html I'm on Windows, and I can see the console with the help of LilyPondTool. But how do I view console output without a gui? It's not in the log file. Anyone? - Mark

Re: RFC: new vertical layout engine

Hi Carl (et al.), Two spaces after a full stop allows the emacs sentence detection code to work properly. @frenchspacing eliminates the extra space after the full stop at the end of the sentence. Then it's settled — excellent! Thanks, Kieren. __

Re: RFC: new vertical layout engine

Carl Sorensen wrote: > Two spaces after a full stop allows the emacs sentence detection code to > work properly. > > @frenchspacing eliminates the extra space after the full stop at the end of > the sentence. > > Aren't we glad we use typesetting software instead of WYSIWYG word > processors?

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...

Re: RFC: new vertical layout engine

On Sat, Jul 25, 2009 at 11:01:44AM -0700, 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

Re: markup?/markup-list? -> ly:markup?/ly:markup-list?

Le 25 juil. 09 à 20:19, Mark Polesky a écrit : So, is there any reason that it's "markup?" and not "ly:markup?". Ditto with "markup-list?". The ly: prefix was supposed to be used for functions defined in the C++ part, which markup? and markup-list? are not. Nicolas

Re: RFC: new vertical layout engine

In message <20090725.163011.184567355...@gnu.org>, Werner LEMBERG writes Indeed, I just see that @frenchspacing is only used for French and Japanese (the latter only partially). It should be activated for all languages except, perhaps, English. Note that I don't care what you native speakers a

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 "sending a patch to emacs-devel". >> >> The current standard

markup?/markup-list? -> ly:markup?/ly:markup-list?

I used to make the mistake of typing ly:markup? when using define-markup-command. Then I would scratch my head when I got Unbound variable: ly:markup? I would run over to IR 4, and think, it's not here, where did it go? So, is there any reason that it's "markup?" and not "ly:markup?". Ditto wit

Re: RFC: new vertical layout engine

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... Seconder? Opposed? Abstentions? Seconder. http://www.chica

Re: tabs vs. spaces in source code

On 25 Jul 2009, at 19:39, Patrick McCarty wrote: One thing you could do right now, without awaiting approval, is to check for lines that have tabs *after* spaces at the beginning. These should be converted to tabs *followed* by spaces. This is not correct, as if tabs are set to 8 spaces, 2 sp

Re: tabs vs. spaces in source code

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 "sending a patch to emacs-devel". > > The current standard is to let tabs and spaces be handled as > emacs handles them

Re: RFC: new vertical layout engine

On Sat, Jul 25, 2009 at 01:30:45PM -0400, 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... > Seconder? Oppo

Re: tabs vs. spaces in source code

On Sat, Jul 25, 2009 at 09:58:26AM -0700, Mark Polesky wrote: > > Also, can we list all of the possible situations where we need to > retain tabs? Ian mentioned .make files; the last time this came up > Patrick McCarty mentioned something about demarcating syllables in > lyrics, which I don't thin

Re: ppppp but no fffff

Jonathan Wilkes wrote: > I don't know if this needs an additional command, but in > Tchaikovsky's 6th symphony there is a "pp" (6 p's) during > the clarinet solo at the end of the exposition. Yes, and I mentioned the on the last page of book 2 of the Ligeti etudes. Graham proposed a

Re: RFC: new vertical layout engine

Hi Werner, To cite the texinfo info pages: Thanks for the reference — for subsequent thread-followers, I also recommend Indeed, I just see that @frenchspacing is only used for French and Japanese (the latter only partially). It shoul

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 be *opposed* to a strict no-tab rule? > > Carl Sorense

Re: tabs vs. spaces in source code

Joe Neeman wrote: > I like spaces just fine, but I'd prefer it if you could hold off > on this for a little while. I have a big patch that I'd like to > merge and I'm not so keen on resolving a bunch of whitespace > conflicts... Okay, I'll make a note: I'll wait for Han-Wen, Jan, and Joe. Thanks

Re: ppppp but no fffff

I don't know if this needs an additional command, but in Tchaikovsky's 6th symphony there is a "pp" (6 p's) during the clarinet solo at the end of the exposition. What's funny is that he only uses "ff" at the beginning of the next section, which is one of the loudest orchestral moments I k

Re: tabs vs. spaces in source code

On Sat, 2009-07-25 at 09:58 -0700, 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 be *opposed* to a strict no-tab rule? I like spaces

Re: percussion and midi

Marc, Thanks a million for pointing me at the articulation and MIDI discussion. I now have a pretty good idea of where to go from here, and I'm almost done with the first item on my todo list. Thanks again. On Tue, Jul 14, 2009 at 2:23 AM, Marc Hohl wrote: > Hello Alan, > > Alan Szlosek schrie

Re: tabs vs. spaces in source code

...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 be *opposed* to a strict no-tab rule? Carl Sorensen wrote: > The last communication we had about it, Han-Wen was > cond

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: RFC: new vertical layout engine

> "The view at CMOS is that there is no reason for two spaces after a > period in published work." Ok, whatever :-) Look up references to TeX and LaTeX for more on this topic. > However, the PDF (e.g., the NR) *appears* to preserve double-space > sentence separations — where (e.g., some > specif

Re: RFC: new vertical layout engine

Hi Werner, It really depends. IIRC, the Chicaco manual of style recommended this. "The view at CMOS is that there is no reason for two spaces after a period in published work." Also see page 28 of Robert Bri

Re: RFC: new vertical layout engine

>> Please use two spaces after a full stop in documentation strings for >> consistence. > > Since this is incorrect typographical practice, It really depends. IIRC, the Chicaco manual of style recommended this. > and Lilypond prides itself on beautiful typography, I'm surprised > this is the s

Re: tabs vs. spaces in source code

>> Thanks, Neil. My editor does confusing things with tabs. Then use a different editor. >> I hate them. I dislike them, too, but there are many editors which handle them just fine. I don't see a problem here. Werner ___ lilypond-devel mailing

Re: RFC: new vertical layout engine

Hi Werner (et al,), Please use two spaces after a full stop in documentation strings for consistence. Since this is incorrect typographical practice, and Lilypond prides itself on beautiful typography, I'm surprised this is the standard in the docs — why/how was this decision made? Chee

feature request (\cueNotes)

I really would be glad, if there was a possibility to make notes (including heads, stems, beams, flags, slurs, clefs, accidentals, ...) smaller. Unfortunately the \small, \tiny, \set fontSize commands don't affect all parts of notes (beams, ... are not affected). Something like \cueNotes or just

Re: tabs vs. spaces in source code

Hi Graham, 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 docs? I think we should have a strict no-tabs rule. And I'm