Don't blindly issue the warning

Don't blindly issue the warning
"lilypond-book: warning: Unable to auto-detect default page settings:"

Also remove the .aux file left over by lilypond-book.

[Graham Percival, 2011-12-14 14:56:33]

LGTM, but I'm not confident enough about this patch to circumvent our review
process, so please wait for it to go through a normal countdown.

If a tex guru (like David, Werner, or Reinhold) says it's good, I'm willing to
push it to staging directly.

[Reinhold, 2011-12-14 16:04:05]

LGTM. 
In particular, it's a good idea to call communicate() before checking the
returncode, because communicate ensures that the returncode is set...

[Julien Rioux, 2011-12-20 14:12:24]

Final patch ready to push.

http://code.google.com/p/lilypond/issues/detail?id=2105

[Graham Percival, 2011-12-20 15:49:01]

Thanks, pushed.  You're responsible for closing the issue.

Cheers,
- Graham

On Tue, Dec 20, 2011 at 03:12:24PM +0100, Julien Rioux wrote:
> Final patch ready to push.
> 
> http://code.google.com/p/lilypond/issues/detail?id=2105

[Julien Rioux, 2011-12-20 16:06:49]

On Tue, Dec 20, 2011 at 4:49 PM, Graham Percival
<graham@percival-music.ca> wrote:
> Thanks, pushed.  You're responsible for closing the issue.

The google issue or the rietveld issue or both?
Thanks,
Julien

[Graham Percival, 2011-12-20 16:11:52]

On Tue, Dec 20, 2011 at 05:06:49PM +0100, Julien Rioux wrote:
> On Tue, Dec 20, 2011 at 4:49 PM, Graham Percival
> <graham@percival-music.ca> wrote:
> > Thanks, pushed.  You're responsible for closing the issue.
> 
> The google issue or the rietveld issue or both?

Both, but most importantly the google issue.

google issue: a pointer
rietveld: memory.  Very occasionally we'll look at open patches
in rietveld from people we know to see how many patches we've
lost, so closing that as well could reduce some confusion in the
future.

Cheers,
- Graham