Re: Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

2012-12-24 Thread dak
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 future

Re: Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

2012-12-24 Thread dak
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

Re: Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

2012-12-24 Thread marc
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

Re: Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

2012-12-24 Thread m...@mikesolomon.org
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 for that

Re: Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

2012-12-24 Thread m...@mikesolomon.org
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 internals

Re: Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

2012-12-24 Thread David Nalesnik
On Mon, Dec 24, 2012 at 7:22 AM, m...@mikesolomon.org 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

git-problem fatal: read error: Connection reset by peer

2012-12-24 Thread Thomas Morley
Hi, trying ~/lilypond-git (dev/local_working)$ git pull -r returns: fatal: read error: Connection reset by peer What's wrong? -Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

2012-12-24 Thread Werner LEMBERG
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-over

Re: git-problem fatal: read error: Connection reset by peer

2012-12-24 Thread Thomas Morley
2012/12/24 Thomas Morley thomasmorle...@googlemail.com: Hi, trying ~/lilypond-git (dev/local_working)$ git pull -r returns: fatal: read error: Connection reset by peer What's wrong? -Harm After rebooting LilyDev, it works again. -Harm

Re: Doc: NR Moved Appendix C to CG (issue 6948070)

2012-12-24 Thread pkx166h
Reviewers: Trevor Daniels, https://codereview.appspot.com/6948070/diff/1/Documentation/contributor.texi File Documentation/contributor.texi (right): https://codereview.appspot.com/6948070/diff/1/Documentation/contributor.texi#newcode74 Documentation/contributor.texi:74: @verbatiminclude