Op dinsdag 07-04-2009 om 15:28 uur [tijdzone -0600], schreef Carl D.
Sorensen:
> LilyPond programming standards call for no tabs in the files.
Not so. http://www.gnu.org/prep/standards/html_node/index.html
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mittwoch, 8. April 2009 06:39:48 Mark Polesky wrote:
> On this page:
> http://lilypond.org/doc/v2.13/input/lsr/lilypond-snippets/index
>
> scroll down to the Staff notation of the navigation bar, and
> hover over some links. There are some errors he
On Wed, Apr 08, 2009 at 11:22:42AM +0200, Reinhold Kainhofer
wrote:
> The only solution I can see is to copy each of the multiply
> included snippets and change their node name so that each file
> is included only once and each node appears only once.
Ouch, and I also can't think of any other sol
On Tue, Apr 7, 2009, Mark Polesky said:
> Short version: I made some changes to output-ps.scm
> that can safely reduce the file size of ps files. In
> a simple experiment, I was able to reduce non-binary
> ps-code by up to 10%.
PS code is notorious for being voluminous. Most of the time the st
Han-Wen Nienhuys wrote:
> The ly:format routine was created as a C++ one because we had
> significant memory blowup due to the use of format routines that ran
> in Scheme. You may want to submit a simple patch to make it strip
> trailing zeroes from decimals; then you get a simple reduction in f
On Wed, Apr 8, 2009, Mark Polesky said:
Would reducing ps excess reduce compilation
> time? Or would the difference be negligible?
PS code is not usually compiled, it is transmitted, parsed, and executed.
Adobes manuals make it clear that the defined operators are deliberatly
given long spelle
On Wed, Apr 8, 2009 at 12:40 PM, Mark Polesky wrote:
>> A significant reduction in actual code can be had with careful use of a
>> private dictionary, sometimes just using shorter names for common
>> operators can help a lot (eg, mt for moveto), but also creating new
>> operators for common opera
Hi,
Currently left-broken line spanners and hairpins are removed
automatically if they end on the first note. Though this is usually
appropriate for trills, glissandi and hairpins, there are situations
where it would be useful to override this default behaviour, for
example when using text spans.
lgtm
http://codereview.appspot.com/32142
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
One minor comment, otherwise lgtm
http://codereview.appspot.com/32148/diff/1/7
File lily/spanner.cc (right):
http://codereview.appspot.com/32148/diff/1/7#newcode426
Line 426: Spanner::after_line_breaking (SCM grob)
Can you think of a name that describes what the function actually does?
Like Spa
On Tue, Apr 7, 2009 at 8:18 PM, Carl D. Sorensen wrote:
>> As to LY not accepting tabs, thats a shame, tabs should be treated as
>> white space, along with and other now-disused
>> characters from the days of teletypes which sometimes find their way into
>> ascii files from odd unix and dos s
11 matches
Mail list logo
