Re: Applies scheme indentation according to the GNU guidelines (issue 6814080)

Marc Hohl writes: Am 10.11.2012 14:59, schrieb janek.lilyp...@gmail.com: I've looked a bit at one random file. Looks mostly good to me. http://codereview.appspot.com/6814080/diff/1/scm/define-music-display-methods.scm File scm/define-music-display-methods.scm (right): http://coderevi

Re: Add LilyPond Report #28 to news (issue 6828049)

LGTM exactly as-is. https://codereview.appspot.com/6828049/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Applies scheme indentation according to the GNU guidelines (issue 6814080)

Some people (notably Jan) were quite vocal about wanting to use "whatever emacs does" literally, regardless of bugs. I support this view; the important thing is consistent indentation. However, I don't see any fixscm.sh in this patch. Also, I'd like to get the fixes to clip-region added, regard

Re: Adds documentation for optional octavation clef syntax (issue 6830043)

LGTM https://codereview.appspot.com/6830043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Applies scheme indentation according to the GNU guidelines (issue 6814080)

Am 11.11.2012 13:45, schrieb gra...@percival-music.ca: Some people (notably Jan) were quite vocal about wanting to use "whatever emacs does" literally, regardless of bugs. I support this view; the important thing is consistent indentation. However, I don't see any fixscm.sh in this patch. I do

Re: [talk] suggestion: redesign "sponsoring" page.

Am 10.11.2012 15:44, schrieb Phil Holmes: - Original Message - From: "Graham Percival" To: "David Kastrup" Cc: "Benjamin CL" ; "LilyPond Developmet Team" Sent: Friday, November 09, 2012 7:26 PM Subject: Re: [talk] suggestion: redesign "sponsoring" page. On Fri, Nov 09, 2012 at 07

Uses single algorithm for side-position spacing. (issue 6827072)

http://codereview.appspot.com/6827072/diff/1/lily/side-position-interface.cc File lily/side-position-interface.cc (right): http://codereview.appspot.com/6827072/diff/1/lily/side-position-interface.cc#newcode85 lily/side-position-interface.cc:85: Position next to support, taking into account my o

Re: User-poll about lily-syntax: results - [Was: [GLISS] basics]

Am 15.10.2012 11:55, schrieb Francisco Vila: 2012/10/15 Marc Hohl : But anyway, are there results from user-polls on other lists? Yes, there are a few ones. They are mainly generic complaints, not specific syntax related. I will make a summary. I don't want to be too pushy, but Harm's poll res

Re: [talk] suggestion: redesign "sponsoring" page.

Marc Hohl writes: > Am 10.11.2012 15:44, schrieb Phil Holmes: >> - Original Message - From: "Graham Percival" >> >> To: "David Kastrup" >> Cc: "Benjamin CL" ; "LilyPond Developmet >> Team" >> Sent: Friday, November 09, 2012 7:26 PM >> Subject: Re: [talk] suggestion: redesign "sponsorin

Re: Uses single algorithm for side-position spacing. (issue 6827072)

On 11 nov. 2012, at 14:50, d...@gnu.org wrote: > > http://codereview.appspot.com/6827072/diff/1/lily/side-position-interface.cc > File lily/side-position-interface.cc (right): > > http://codereview.appspot.com/6827072/diff/1/lily/side-position-interface.cc#newcode85 > lily/side-position-interfa

Re: Uses single algorithm for side-position spacing. (issue 6827072)

On 2012/11/11 15:26:48, mike7 wrote: To be clear, I have no problem implementing a LilyPond documentation and commenting policy to move towards the establishment of an API. This sounds like a worthwhile yet difficult task. I would start talking about this separately from any one patch.

Re: User-poll about lily-syntax: results - [Was: [GLISS] basics]

2012/11/11 Marc Hohl : > Am 15.10.2012 11:55, schrieb Francisco Vila: > >> 2012/10/15 Marc Hohl : >>> >>> But anyway, are there results from user-polls on other lists? >> >> Yes, there are a few ones. They are mainly generic complaints, not >> specific syntax related. I will make a summary. > > I d

Re: Uses single algorithm for side-position spacing. (issue 6827072)

To make it short: a function needs documentation that tells its purpose in the overall scheme of things (for what purpose is it used), its outline (what does it do), its input and output. A "policy" may describe how they are formatted and whether or not they are used as Scheme documentation strin

Re: [talk] suggestion: redesign "sponsoring" page.

Hi, I agree with David that volunteering work is important and we should ask for volunteers as much (or more) as for money. However, we have lilypond.org/help-us.html for this. I definitely agree that it's the interested devs who should maintain their respective blurbs. What i was suggesting wa

Busy Developer's Summary 5: discussions about sponsoring

Hi, 2.16.1 (updated stable version) was released. http://lilypond.org/download.html There were some discussions regarding supporting LilyPond development financially: "Supporting LilyPond development financially" http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00204.html I suggested s

Re: Busy Developer's Summary 5: discussions about sponsoring

One more thing: Joram Berger shared with us a very nice Lilypond cheat sheet: http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00131.html There's a suggestion of linking to this cheat sheet as well as Reinhold's one (http://www.edition-kainhofer.com/en/lilypond-en/511/lilypond-cheatshee

Re: Applies scheme indentation according to the GNU guidelines (issue 6814080)

On Sun, Nov 11, 2012 at 02:22:30PM +0100, Marc Hohl wrote: > Am 11.11.2012 13:45, schrieb gra...@percival-music.ca: > >Some people (notably Jan) were quite vocal about wanting to use > >"whatever emacs does" literally, regardless of bugs. I support this > >view; the important thing is consistent i

Re: Uses single algorithm for side-position spacing. (issue 6827072)

On 11 nov. 2012, at 20:57, d...@gnu.org wrote: > To make it short: a function needs documentation that tells its purpose > in the overall scheme of things (for what purpose is it used), its > outline (what does it do), its input and output. > This sounds great. > A "policy" may describe how th

Patchy report

22:58:01 (UTC) Begin LilyPond compile, previous commit at 19033189f6f38fbd5dac798f151ede79fcad657e 22:58:30 Merged staging, now at:19033189f6f38fbd5dac798f151ede79fcad657e 22:58:33Success:sudo -u lilybuild ./autogen.sh --noconfigure 22:59:11Success:

PATCH: Countdown to 20121113

For 20:00 MST Tuesday November 13 Documentation: Issue 2591 : NR: repeat slurs and glissando workaround - R 6814115 Cheers, Colin -- I stay cool and dig all jive, That's the way I stay alive. M

GSoC doc sprint summit

In case this gets repeated next year (which I think so), maybe active LilyPond documenters are interested in participation: https://sites.google.com/site/docsprintsummitv2/ Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://l

Re: Doc: Add example of extending glissandi over repeats (2591) (issue 6814115)

LGTM http://codereview.appspot.com/6814115/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel