On Sun, 2005-02-13 at 13:26 +0100, Nicolas Sceaux wrote:
> Sorry for not being very reactive since then.
> I'm about to commit a `define-safe-public' macro, used where
> appropriate.
> make web runs fine.
Safety is (I think) the only remaining technical problem. This week-end,
after swearing a lo
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> >
>> > This should not be a big problem. In this case, I solved it by adding
>> > begin-of-line-invisible to safe-lily.scm. However, we should probably
>> > have some Scheme
[EMAIL PROTECTED] writes:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> >
> > This should not be a big problem. In this case, I solved it by adding
> > begin-of-line-invisible to safe-lily.scm. However, we should probably
> > have some Scheme level macro support for tagging a definition as
> > "
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> This should not be a big problem. In this case, I solved it by adding
> begin-of-line-invisible to safe-lily.scm. However, we should probably
> have some Scheme level macro support for tagging a definition as
> "safe", ie.
>
> (define-safe-public (b
[EMAIL PROTECTED] writes:
> > * Maybe it would be a good idea to have separate snippet DB for each
> > branch (ie. a 2.4 and 2.6 database.). It is possible to run
> > multiple versions of Lily alongside eachother. If you can't make
> > it work, that is a serious bug, and I will gladly
On Monday 31 January 2005 06.38, Graham Percival wrote:
> On 30-Jan-05, at 7:38 AM, Han-Wen Nienhuys wrote:
> > * Maybe it would be a good idea to have separate snippet DB for each
> > branch (ie. a 2.4 and 2.6 database.). It is possible to run
> > multiple versions of Lily alongside each
On 30-Jan-05, at 7:38 AM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
*** The Lilypond Snippet Repository ***
Essentially this is input/test/ done properly? Sounds great! :)
* Perhaps you can work together with Graham to copy snippets from
the manual. If the LSR is a success, we can d
On Sunday 30 January 2005 17.29, Sebastiano Vigna wrote:
> On Sun, 2005-01-30 at 16:38 +0100, Han-Wen Nienhuys wrote:
> > This is so incredibly way way cool!
I totally agree on this.
> > I fully support this initiative,
> > and will gladly work to make running lily on your server as flawless
>
On Mon, 2005-01-31 at 01:30 +0100, Erik Sandberg wrote:
> I would very much welcome a system like the one Han-Wen suggested; where you
> can submit a bug report snippet with tag "Not verified". For example, I could
> review it, isolate it, add it to the cvs database, and then tag it "added to
>
[EMAIL PROTECTED] writes:
> > * I suspect that you could import the input/{test,regression}/
> > directory wholesale.
>
> Well, I thought about that, but many regressions show that lily does the
> right thing when writing stuff normally, so they're not a good candidate
> for explaining how
On Sun, 2005-01-30 at 16:38 +0100, Han-Wen Nienhuys wrote:
> This is so incredibly way way cool! I fully support this initiative,
> and will gladly work to make running lily on your server as flawless
> as possible.
I hoped so!
> * Perhaps you can work together with Graham to copy snippets from
*** The Lilypond Snippet Repository ***
I would like to invite the user community of Lilypond (and developers,
if they think it's useful) to join a project: to build a consistent
searchable set of Lilypond snippets that solve common problems.
In the last weeks I've realised that Lilypond has all
[EMAIL PROTECTED] writes:
> > * I suspect that you could import the input/{test,regression}/
> > directory wholesale.
>
> Well, I thought about that, but many regressions show that lily does the
> right thing when writing stuff normally, so they're not a good candidate
> for explaining how t
[continuing on lp-devel]
[EMAIL PROTECTED] writes:
> *** The Lilypond Snippet Repository ***
>
> I would like to invite the user community of Lilypond (and developers,
> if they think it's useful) to join a project: to build a consistent
> searchable set of Lilypond snippets that solve common pr
Wow! I find it more useful than the Tips&Tricks/Regression tests
document. I'll be happy to contribute some snippets.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
15 matches
Mail list logo