Re: indexing : tweaks & question

Remember that @funindex prints entries automatically formatted in @code. Also remember that @cindex is for concepts, not exact lilypond commands or property names. Also also remember that a lot of the pre-GDP docs don't follow these (and other) new policies. Finally, if you seriously want proper

Re: Proposal of helper script

On 2008/10/21 14:10 +0200, Francisco Vila wrote: > I'd find useful a tool that, given a language: > > - searches itely files for @lilypondfile blocks of LSR snippets > - gathers the name of the filename argument > - looks in input/lsr if this file does exist (some of them don't) > - if one exists,

Re: indexing : tweaks & question

Hi Ralph I actually quite like properties indexed in a different way to other things, but for consistency maybe we should remove the @code{ }. Just to be sure though I'll copy to -dev for comment. Trevor - Original Message - From: "Ralph Palmer" <[EMAIL PROTECTED]> To: "Trevor Dan

[PATCH] Break figured bass extenders if a figure has a different augmentation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So far, an extender line was only broken when a figure had a different alteration (+,-,!), but not if it had a different augmentation (\\, \+ or /). This patch also stores the state of the other modifiers and breaks the extender if they change. http

Proposal of helper script

I'd find useful a tool that, given a language: - searches itely files for @lilypondfile blocks of LSR snippets - gathers the name of the filename argument - looks in input/lsr if this file does exist (some of them don't) - if one exists, look in input/texidocs for a filename with the .texidoc suff

Re: Oyseaux, two proposals

Francisco, you wrote Monday, October 20, 2008 7:42 PM 2008/10/20 Valentin Villenave <[EMAIL PROTECTED]>: 2008/10/20 Till Rettig <[EMAIL PROTECTED]>: Great work, thank you! I like both ;-)... maybe the first a bit more... I'd go for the first one too (though I like the end so much...) beca

Re: showFirstLength

2008/10/15 Jonathan Kulp <[EMAIL PROTECTED]>: > So is the "showFirstLength" feature available in the next version? This > will be a very useful feature for me. Thanks for creating it :) I think it will be available in 2.11.63. Thanks for encouraging me :-) Cheers, Valentin ___

Re: showFirstLength

OK. I have eventually left the skiptypesetting-show-last regtest, and added two more regtests (skiptypesetting-show-first, skiptypesetting-show-first-and-last). Since I have your LGTM, I pushed the commit. http://codereview.appspot.com/7317/diff/7/8 File input/regression/skiptypesetting-show-la