Re: Texinfo help, please

On Fri, Jul 13, 2012 at 08:01:52AM +0200, David Kastrup wrote: > Graham Percival writes: > > > Sorry, I should have specified "absolutely no way to get --- > > without any mixing of content and layout commands". I think we > > should minimize any layout-specific commands in our docs. > > It's n

Re: Fixes all black bars in NR (issue 6345088)

Werner LEMBERG writes: >> Hmm, that brings to mind a different possible solution: >> >> @macro lilyfile{\FILENAME\} >> @/@file{\FILENAME\} >> @end macro >> >> if there's no way to automate our desired behaviour (assuming we >> can agree on a desired formatting in the output!), this might be >>

Re: Texinfo help, please

Graham Percival writes: > On Wed, Jul 11, 2012 at 10:45:24PM +0200, David Kastrup wrote: >> Graham Percival writes: >> >> > Hmm. So there's absolutely no way to get >> > >> > --- linewidth -- >> > from some kind of >> > emergency-stretch-tweak >> > --- linewidth -- >> >

PATCH: Countdown to 20120715

For 20:00 MDT Sunday July 15 Documentation: Issue 2322 : Document use of property-setting music in output definitions - R 6345086 Issue 2650

Re: gub branch denemo

On Thu, Jul 12, 2012 at 09:44:41AM -0500, Jeremiah Benham wrote: > I want to know if I could have write access to lilyponds git. Would > I need an account on the server? Do I submit my ssh key somewhere? https://github.com/gperciva/gub > I want to push my changes into a branch called denemo. I pl

Re: Texinfo help, please

On Wed, Jul 11, 2012 at 10:45:24PM +0200, David Kastrup wrote: > Graham Percival writes: > > > Hmm. So there's absolutely no way to get > > > > --- linewidth -- > > from some kind of > > emergency-stretch-tweak > > --- linewidth -- > > > > ? that's a shame. > > If you w

Re: Fixes all black bars in NR (issue 6345088)

On Thu, Jul 12, 2012 at 02:07:39AM +0200, Werner LEMBERG wrote: > > It is very unfortunate that we can't upgrade to the current > texinfo.tex file; it contains a lot of improvements, including a very > flexible URL command. Why can't we do this? Do we just have to many custom hacks in our existi

Re: web: Linux => GNU/Linux. English only. (issue 6374060)

What about the "Linux" in the links here? http://lilypond.org/unix.html I'm fine with having just a plain -linux- in the filename, but the link text should be changed to GNU. Try grepping for "Linux" in scripts/ http://codereview.appspot.com/6374060/ ___

Re: web: Linux => GNU/Linux. English only. (issue 6374060)

2012/7/12 : > On 2012/07/12 12:47:46, janek wrote: >> >> Also, i didn't touch translations (btw, is there a complete list of >> Translation Meisters somewhere? didn't find in CG...). Do you mean 'translators'? > The change will appear with a "check-translation" when master will be > merged in tr

gub branch denemo

I am one of the maintainers for GNU Denemo. I have successfully compiled Denemo for mingw using gub. http://denemo.org/downloads/denemo-0.9.5rc1.exe (This was produced inside VirtualBox OSE and LIlydev) I want to know if I could have write access to lilyponds git. Would I need an account on th

Re: web: Linux => GNU/Linux. English only. (issue 6374060)

On Thu, Jul 12, 2012 at 3:35 PM, wrote: > The change will appear with a "check-translation" when master will be > merged in translation, or a special "view" on Documentation/ in gitk. Cool! I didn't know that, thanks. Janek ___ lilypond-devel mailing

Re: GOP-PROP 2-1: LilyPond is part of GNU

On Thu, Jul 12, 2012 at 3:20 PM, David Kastrup wrote: > Janek Warchoł writes: > >> 3.4 - trigraphs in C code >> wtf? > > You can say that again. The following is valid C: > > ??=include > > int main(int ac, char *av??(??)) > ??< > printf ("%s??/n", ac>1 ? av??(1??) : "No argument."); >

Re: web: Linux => GNU/Linux. English only. (issue 6374060)

On 2012/07/12 12:47:46, janek wrote: Also, i didn't touch translations (btw, is there a complete list of Translation Meisters somewhere? didn't find in CG...). The change will appear with a "check-translation" when master will be merged in translation, or a special "view" on Documentation/ in

Re: GOP-PROP 2-1: LilyPond is part of GNU

Janek Warchoł writes: > 3.4 - trigraphs in C code > wtf? You can say that again. The following is valid C: ??=include int main(int ac, char *av??(??)) ??< printf ("%s??/n", ac>1 ? av??(1??) : "No argument."); return 0; ??> We don't need to check this explicitly: gcc refuses

Re: GOP-PROP 2-1: LilyPond is part of GNU

Hi Graham (+1 for Graham!) & all (+1 for everybody!), let's try to summarize (can you update http://lilypond.org/~graham/gop/gop_2.html, Graham?) The numbers given are from GNU policies, see above. --required 6.3 - list authors check (git does this) 6.5 - copyright n

web: Linux => GNU/Linux. English only. (issue 6374060)

Reviewers: , Message: Please review. I don't feel like changing the names of download files, they seem hard-coded in the build/release system :/ Also, i didn't touch translations (btw, is there a complete list of Translation Meisters somewhere? didn't find in CG...). Finally, there are loads o

Patchy email

12:02:02 (UTC) Begin LilyPond compile, previous commit at e8fc7813b17822c138150807484197ef8d4e7c21 12:02:08 *** FAILED STEP *** merge from staging Command 'git branch test-master-lock origin/master' returned non-zero exit status 128 fatal: A branch named 'test-master-loc

Re: Doc: Update changing context default settings (2322) (issue 6345086)

On 2012/07/12 10:53:19, dak wrote: I am not happy with all those fine distinctions and almost, but not quite, similar syntax for property manipulations in different contexts I've done a lot of LP documentation in the past, and find it is frequently the case that attempts to write down precise

Re: Doc: Update changing context default settings (2322) (issue 6345086)

On 2012/07/12 10:44:04, Trevor Daniels wrote: On 2012/07/12 10:20:01, dak wrote: > Uhm, wrong? [etc] Thanks David - that's the explanation I needed :) I am not happy with all those fine distinctions and almost, but not quite, similar syntax for property manipulations in different contexts

Re: Doc: Update changing context default settings (2322) (issue 6345086)

On 2012/07/12 10:20:01, dak wrote: Uhm, wrong? [etc] Thanks David - that's the explanation I needed :) I'll make amendments and post a new patch-set. Trevor http://codereview.appspot.com/6345086/ ___ lilypond-devel mailing list lilypond-devel@gn

Re: Doc: Update changing context default settings (2322) (issue 6345086)

On 2012/07/12 09:52:35, t.daniels_treda.co.uk wrote: wrote Thursday, July 12, 2012 10:35 AM > On 2012/07/12 09:31:40, Trevor Daniels wrote: > http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely#newcode844 >> Documentation/not

Re: Doc: Update changing context default settings (2322) (issue 6345086)

wrote Thursday, July 12, 2012 10:35 AM > On 2012/07/12 09:31:40, Trevor Daniels wrote: > http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely#newcode844 >> Documentation/notation/changing-defaults.itely:844: \override Stem > #'thickness = #4.0 >> On 201

Re: Doc: Update changing context default settings (2322) (issue 6345086)

On 2012/07/12 09:31:40, Trevor Daniels wrote: http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely File Documentation/notation/changing-defaults.itely (right): http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.it

Re: Doc: Update changing context default settings (2322) (issue 6345086)

http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely File Documentation/notation/changing-defaults.itely (right): http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely#newcode844 Documentation/notation/changing-de