From 118a19e41bf8cbced3dff8aab4ed6ea0698d1f0f Mon Sep 17 00:00:00 2001 From: Han-Wen Nienhuys Date: Sun, 24 Jul 2005 19:37:47 +0000 Subject: [PATCH] (Invoking lilypond): add LILYPOND_GC_YIELD documentation. --- ChangeLog | 3 ++ Documentation/user/invoking.itely | 58 ++++--------------------------- 2 files changed, 10 insertions(+), 51 deletions(-) diff --git a/ChangeLog b/ChangeLog index 228a0cba17..8a2e6912b9 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,8 @@ 2005-07-24 Han-Wen Nienhuys + * Documentation/user/invoking.itely (Invoking lilypond): add + LILYPOND_GC_YIELD documentation. + * lily/*: cleanups: use scm_from_int iso. scm_int2num. Idem for scm_from_real / scm_make_real. diff --git a/Documentation/user/invoking.itely b/Documentation/user/invoking.itely index 7e8780ffc0..08f1523644 100644 --- a/Documentation/user/invoking.itely +++ b/Documentation/user/invoking.itely @@ -270,57 +270,6 @@ Show the warranty with which GNU LilyPond comes. (It comes with @section Environment variables -@ignore -For processing both the @TeX{} and the PostScript output, the -appropriate environment variables must be set. The following scripts -do this: - -@itemize @bullet -@item @file{buildscripts/@/out/@/lilypond@/-profile} -(for SH shells) -@item @file{buildscripts/@/out/@/lilypond@/-login} (for C-shells) -@end itemize - -They should normally be sourced as part of the login process. If these -scripts are not run from the system wide login process, then you must -run them yourself. - -@cindex installing LilyPond - -If you use sh, bash, or a similar shell, then add the following to -your @file{.profile}: -@example -. @var{/the/path/to/}lilypond-profile -@end example - -If you use csh, tcsh or a similar shell, then add the following to -your @file{~/.login}: -@example -source @var{/the/path/to/}lilypond-login -@end example - -Of course, in both cases, you should substitute the proper location of -either script. - -These scripts set the following variables: -@table @code -@item TEXMF -To make sure that @TeX{} and lilypond find data files (among -others @file{.tex}, @file{.mf}, and @file{.tfm}), -you have to set @code{TEXMF} to point to the lilypond data -file tree. A typical setting would be -@example -@{/usr/share/lilypond/2.4.0,@{!!/usr/share/texmf@}@} -@end example - -@end table - -@cindex PostScript -@cindex TEXMF -@cindex printing postscript - -@end ignore - @cindex LANG @cindex LILYPONDPREFIX @@ -334,6 +283,13 @@ subdirectories called @file{ly/}, @file{ps/}, @file{tex/}, etc. @item LANG This selects the language for the warning messages. + +@item LILYPOND_GC_YIELD +With this variable the memory footprint and performance can be +adjusted. It is a percentage tunes memory management behavior. With +higher values, the program uses more memory, with smaller values, it +uses more CPU time. The default value is @code{70}. + @end table -- 2.39.5