All of this is absolutely devastatingly horrible code that is not
reconcilable with sane per-session semantics and tampers with LilyPond
internals in a way that has bleed-over effects into future files in the
same command line.
In addition, the interfaces into the exposed internals are absolutely
On 24 déc. 2012, at 01:10, d...@gnu.org wrote:
> All of this is absolutely devastatingly horrible code that is not
> reconcilable with sane per-session semantics and tampers with LilyPond
> internals in a way that has bleed-over effects into future files in the
> same command line.
>
> In additio
On 2012/12/24 07:28:17, mike7 wrote:
On 24 déc. 2012, at 01:10, mailto:d...@gnu.org wrote:
> All of this is absolutely devastatingly horrible code that is not
> reconcilable with sane per-session semantics and tampers with
LilyPond
> internals in a way that has bleed-over effects into futur
On 2012/12/24 08:10:25, marc wrote:
On 2012/12/24 07:28:17, mike7 wrote:
> So what I need from you, if you're willing to help me out, are
explanations of
> how this causes bleedover effects.
IIRC, the functions define-session and define-session-public were
created for that very reason, so
On 2012/12/24 07:28:17, mike7 wrote:
So what I need from you, if you're willing to help me out, are
explanations of
how this causes bleedover effects.
IIRC, the functions define-session and define-session-public were
created for that very reason, so perhaps they are what you're after?
Just
On 24 déc. 2012, at 10:10, m...@hohlart.de wrote:
> On 2012/12/24 07:28:17, mike7 wrote:
>
>> So what I need from you, if you're willing to help me out, are
> explanations of
>> how this causes bleedover effects.
>
> IIRC, the functions define-session and define-session-public were
> created fo
On 24 déc. 2012, at 10:36, d...@gnu.org wrote:
> On 2012/12/24 07:28:17, mike7 wrote:
>
>> On 24 déc. 2012, at 01:10, mailto:d...@gnu.org wrote:
>
>> > All of this is absolutely devastatingly horrible code that is not
>> > reconcilable with sane per-session semantics and tampers with
> LilyPond
On Mon, Dec 24, 2012 at 7:22 AM, m...@mikesolomon.org
wrote:
> On 24 déc. 2012, at 10:36, d...@gnu.org wrote:
>
> On 2012/12/24 07:28:17, mike7 wrote:
>
> On 24 déc. 2012, at 01:10, mailto:d...@gnu.org wrote:
>
>
>> All of this is absolutely devastatingly horrible code that is not
>> reconcilable
>> It is just wires sticking out, and it is wires to something that
>> was never intended to be shorted.
>
> Let the wires stick out and let people experiment! Us, users, et
> cetera. That is, in my opinion, the best way for things to move
> forward. What I'm interested in fixing are the bleed
On 24 déc. 2012, at 15:55, David Nalesnik wrote:
> On Mon, Dec 24, 2012 at 7:22 AM, m...@mikesolomon.org
> wrote:
>> On 24 déc. 2012, at 10:36, d...@gnu.org wrote:
>>
>> On 2012/12/24 07:28:17, mike7 wrote:
>>
>> On 24 déc. 2012, at 01:10, mailto:d...@gnu.org wrote:
>>
>>
>>> All of this is
10 matches
Mail list logo
