Re: LSR update adds whitespace
At 18:07 on 28 Nov 2009, Graham Percival wrote: On Sat, Nov 28, 2009 at 04:58:01PM +, Neil Puttock wrote: 2009/11/27 Graham Percival gra...@percival-music.ca: or whether Neil automatically stripped out the extra whitespace when committing LSR updates I strip all the trailing whitespace with sed after downloading the LSR tarball. Ok. Could we get this added to makelsr.py ? I'd be surprised if it takes more than 1 line of python to strip all trailing whitespace. line = line.rstrip() -- Mark Knoop ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Detailed instructions for jail mode
Hi, for the LilyPond Google Wave plugin, to ease hosting LilyPond services, I created detailed instructions about how to set up a good chroot jail. Could it be (worth) linked in the doc somehow? http://code.google.com/p/lilypondy/wiki/LilyPondInJail Thanks, Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Italic font on OSX 10.5
I have apparently lost my italic fonts in LilyPond on OSX 10.5. Musical instructions such as Allegro are now in an upright font. I believe this means that my FontConfig or something like that is messed up. I remember this issue being raised on the list some time ago, but I couldn't find it in the archives. Any recommendations for what I can do to fix things? Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority-Regression policy
On 2009-11-30, Graham Percival wrote: On Sun, Nov 29, 2009 at 07:34:37PM -0800, Patrick McCarty wrote: On 2009-11-29, Graham Percival wrote: What's the feeling amongst developers about what should be ranked as priority-Regression (and thus stop a release) ? In particular, should *everything* that used to work -- even if it was by accident? -- be ranked a Regression? Maybe we could add labels indicating which release an issue blocks? The previous policy, which I assume stands, is that anything ranked Priority-Regression is a release blocker. IIRC, at one point this even blocked unstable releases. Ah, okay. Just as long as we decide not to block unstable releases, I'm fine with it. That's asking a little too much. :-) I don't particularly mind which way we decide, but I'd like it to be consistent, and I'm going to insist that if something is Priority-Regression, it blocks a release. IMO, regressions from 2.13 should get first priority and should block 2.14, but other regressions should be considered on a case-by-case basis. I'm not opposed to this, although if we want to go this route, I propose *removing* the Priority-Regression label. We could then use High, Medium, Low, Postponed. Regressions would then be High-priority by default, but developers could lower it if the regression was due to an architecture change, or if it only worked by accident originally. What if we use Type: Regression instead of Priority: Regression, and then label each with a priority of either High, Medium, Low, or Postponed (assuming we decide to go this route)? Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Detailed instructions for jail mode
On Tue, Dec 01, 2009 at 04:54:59PM +0100, Bertalan Fodor (LilyPondTool) wrote: for the LilyPond Google Wave plugin, to ease hosting LilyPond services, I created detailed instructions about how to set up a good chroot jail. Could it be (worth) linked in the doc somehow? Dunno what the wave thing is all about, but I'm totally fine with better jail instructions. It would go in Usage 1.7 Jail, or Security issues, or Running as a web service, or something like that. As long as the patch compiles, and doesn't touch other areas (other than possibly adding a link from 1.2 to it), I'm not going to be too picky about it. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [frogs] Frog's Lament
On Mon, Nov 30, 2009 at 11:25:46AM -0500, Chris Snyder wrote:
Graham Percival wrote:
On Thu, Nov 26, 2009 at 11:12:26PM +0100, David Kastrup wrote:
We are not talking about explaining concepts to potential contributors
in private. We are talking about explanations happening on the
developer list. Those can be skimmed off into documentation, without
requiring all too much advance knowledge, because they were written for
the sake of people without all too much knowledge.
I agree COMPLETELY. Are you volunteering?
Perhaps it would be worth of another task master just to tick any such
article with the potential more useful than existing docs into a list,
I agree COMPLETELY. Are you volunteering?
It seems to me that such a list would best be maintained in a
bug-tracker of some sort (though IMHO not the official issue tracker due
to the noise it would generate).
Despite my agreements to both paragraphs above, I agree more with
the first than the second. Namely, I don't see the point of
keeping a list of stuff to add to the docs; that's a recipe for
not getting anything done.
Add stuff directly to the CG. If you really can't figure out what
somebody talking about, just add something like
-
Han-Wen wrote something about contexts and accessing property
data? @uref{http://lilypond-user-mailist/01234123.html}
-
to the docs. But get it into the actual docs, not yet another
random webpage or issue list.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Detailed instructions for jail mode
On Tue, Dec 01, 2009 at 04:54:59PM +0100, Bertalan Fodor (LilyPondTool) wrote: for the LilyPond Google Wave plugin, to ease hosting LilyPond services, I created detailed instructions about how to set up a good chroot jail. Could it be (worth) linked in the doc somehow? Dunno what the wave thing is all about, but I'm totally fine with better jail instructions. It would go in Usage 1.7 Jail, or Security issues, or Running as a web service, or something like that. As long as the patch compiles, and doesn't touch other areas (other than possibly adding a link from 1.2 to it), I'm not going to be too picky about it. Cheers, - Graham Would you prefer providing compact instructions in the lilypond doc and an external link to the details, or detailed instructions in the lilypond doc and external link to the reference web service implementation. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
