> #(ly:context-pushpop-property context Tie-definition 'details)
>
> ...then Tie.details.stem-gap would get reverted, instead of
> Tie.details.ratio, since stem-gap was the most recent override.
>
> - Mark
--
Abel Cheung
New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E 01
operty? I can't get it to
> revert *nested* grob-properties. I get close, but then
> something always ends up wrong. I don't think it's strictly
> needed in my case, but I'd like to know if there is a way.
>
> - Mark
> ______
e LilyPond as web service.
Even for powerful machines, having 10 persons or so using it is
effectively a DoS on the machine. Not to mention one can create
snippets requiring HOURS to render (say, lyrics with Asian
characters). So it is very critical to restrict number of users, as
well as the conten
d with old LilyPond packages, and a potential
> >> new maintainer (Pedro Kroger) with his sponsor going mia.
> >
> > Who was going to sponsor him?
>
> I don't think Pedro told me that. Pedro?
>
> Jan.
>
--
Abel Cheung &l
ONDPREFIX),$(shell kpsexpand \$$TEXMF)}
>
> @@ -28,8 +30,6 @@ export DVIPSMAKEPK := mktexpk --destdir
> endif
>
>
> -# guile load path?
> -
> the-script-dir=$(wildcard $(script-dir))
>
>
> --
> Jan Nie
On 2005-02-07(Mon) 15:12:31 -0800, Graham Percival wrote:
>
> On 7-Feb-05, at 4:27 AM, Abel Cheung wrote:
> >2. And a more serious problem -- will lilypond support using DESTDIR
> >for
> > staged installation (i.e. install in another root dir)? This is very
> &g
very
common for packaging, say:
make install DESTDIR=/another/location
However, seems DESTDIR is only supported when installing info and
manpages. What's the direction here? Is complete support desired, or
just eliminate the incomplete support altogether?
Abel
--
A
