Re: critical issues

m...@apollinemike.com m...@apollinemike.com writes: On Jan 5, 2012, at 1:20 AM, Janek Warchoł wrote: Correct me if i'm wrong, but my impression is that there is no particular direction in which we are going. I'm sure that other people have their pet projects as well. The ensemble of these

Re: critical issues

On Jan 5, 2012, at 9:14 AM, David Kastrup wrote: m...@apollinemike.com m...@apollinemike.com writes: On Jan 5, 2012, at 1:20 AM, Janek Warchoł wrote: Correct me if i'm wrong, but my impression is that there is no particular direction in which we are going. I'm sure that other people

Re: critical issues

m...@apollinemike.com m...@apollinemike.com writes: On Jan 5, 2012, at 9:14 AM, David Kastrup wrote: m...@apollinemike.com m...@apollinemike.com writes: On Jan 5, 2012, at 1:20 AM, Janek Warchoł wrote: Correct me if i'm wrong, but my impression is that there is no particular direction

Re: Segfault 2.15.23 Span_bar_stub_engraver

On Jan 5, 2012, at 7:51 AM, David Kastrup wrote: Grob::get_vertical_axis_group is not protected against the case where g has an axis group interface but no Y_AXIs parent. I thought it was. If g has no Y_AXIS parent, then when get_vertical_axis_group (g-get_parent (Y_AXIS)); is called, the

Re: Segfault 2.15.23 Span_bar_stub_engraver

m...@apollinemike.com writes: On Jan 5, 2012, at 7:51 AM, David Kastrup wrote: Grob::get_vertical_axis_group is not protected against the case where g has an axis group interface but no Y_AXIs parent. I thought it was. If g has no Y_AXIS parent, then when get_vertical_axis_group

Re: Segfault 2.15.23 Span_bar_stub_engraver

On Jan 5, 2012, at 11:24 AM, David Kastrup wrote: m...@apollinemike.com writes: On Jan 5, 2012, at 7:51 AM, David Kastrup wrote: Grob::get_vertical_axis_group is not protected against the case where g has an axis group interface but no Y_AXIs parent. I thought it was. If g has no

Re: Segfault 2.15.23 Span_bar_stub_engraver

m...@apollinemike.com m...@apollinemike.com writes: On Jan 5, 2012, at 11:24 AM, David Kastrup wrote: m...@apollinemike.com writes: On Jan 5, 2012, at 7:51 AM, David Kastrup wrote: Grob::get_vertical_axis_group is not protected against the case where g has an axis group interface but no

Re: (was) Some drum notation questions - (now) problem with noteheads in doc?

Am 04.01.2012 19:59, schrieb James: On 4 January 2012 18:55, Jamespkx1...@gmail.com wrote: Hello, On 4 January 2012 18:32, Vaylor Trucksvay...@gmail.com wrote: I have been using lilypond for years for my own projects and have recently introduced it to a friend of mine. He is a drum

include music-function

Dear lily-list-members, first of all: A happy new year! In my projects I often combine several files, each containing one piece, to a book. In fact, I store the music in a scheme-based structure to instantiate it later. The included files shall intentionally not create a PDF, so that

Re: include music-function

Jan-Peter Voigt jp.vo...@gmx.de writes: I am compiling this file directly: --snip-- #(define-public includeLocal (define-music-function (parser location file)(string?) (let ((outname (format ~A.ly (ly:parser-output-name parser))) (locname (car (ly:input-file-line-char-column

@rlsrnamed{Name,Translation} translates also the name in the URI

Issue 1721 reported that @rlsr{Name} keeps the text in english but translates the link in the translated manuals (no idea where the translation comes from). So it recommends to use @rlsrnamed{Name,Translation} instead. But it looks like @rlsrnamed is affected by the same bug. Looking through

Re: include music-function

Hello David, Any reason you don't just do #{ \include #file #} here? yes there is: --snip-- \version 2.15.21 #(define-public includeLocal (define-music-function (parser location file)(string?) (let ((outname (format ~A.ly (ly:parser-output-name parser))) (locname (car

Re: include music-function

Jan-Peter Voigt jp.vo...@gmx.de writes: Hello David, Any reason you don't just do #{ \include #file #} here? yes there is: --snip-- \version 2.15.21 #(define-public includeLocal (define-music-function (parser location file)(string?) (let ((outname (format ~A.ly

Re: include music-function

Hello David, Am 05.01.2012 13:50, schrieb David Kastrup: Ah yes. ly:parse-file does not help either? yes it does, thanks ... but ... --snip-- #(define-public includeLoc (define-music-function (parser location file)(string?) (let ((outname (format ~A.ly (ly:parser-output-name

Re: include music-function

Jan-Peter Voigt jp.vo...@gmx.de writes: This does not work ... the var music is not known in the file included with ly:parse-file. There has been a function ly:parser-parse-file in 2.12 - and if my memory doesn't trick me, there has been discussion on devel why and how to remove it. This

Re: include music-function

Jan-Peter Voigt jp.vo...@gmx.de writes: #(define-public includeLocal (define-music-function (parser location file)(string?) (let ((outname (format ~A.ly (ly:parser-output-name parser))) (locname (car (ly:input-file-line-char-column location (if (or (string=?

PATCH: Countdown to 20120108

For Sunday January 8th Issue 2170 http://code.google.com/p/lilypond/issues/detail?id=2170: Patch: Updates makelsr to point to lilypond exe - R5489134 http://codereview.appspot.com/5489134/ Some syntax comments from Graham, but they shouldn't hold up the countdown. Cheers, Colin -- I've

Implements DOM-id property for grobs. (issue 5504106)

LGTM https://codereview.appspot.com/5504106/diff/1/scm/output-ps.scm File scm/output-ps.scm (right): https://codereview.appspot.com/5504106/diff/1/scm/output-ps.scm#newcode258 scm/output-ps.scm:258: (define (open-node n) n) I don't see this procedure used anywhere...