Sorry, I don't know why this is on this thread. I'll resend.
james
James Lowe wrote:
Hello,
Going on from the 'curly quotes' problem that you resolved a couple of
days back in our documentation, I noticed in the NR while scanning
through another 'odd'
single quote mark after the hash (#) ch
Hi Joe!
Another bug involving the new vertical spacing system reported on
LilyPond French Users mailing list.
This one is concerning "before-title-spacing", which mess up with
automatic page breaks (systems run off the page).
Could you have a look at this, please?
BTW should I send this to bug-l
sorry, no joy:
cd ./out-www && @PDFLATEX@ suffix-latex.tex
/bin/sh: @PDFLATEX@: not found
make[4]: *** [out-www/suffix-latex.pdf] Error 127
gperc...@gperciva-desktop:/main/src/build-lilypond$ grep PDFLATEX *
config.make:PDFLATEX = @PDFLATEX@
http://codereview.appspot.com/1556043/show
__
On Wed, Jun 9, 2010 at 1:59 PM, wrote:
> sorry, no joy:
>
> cd ./out-www && @PDFLATEX@ suffix-latex.tex
> /bin/sh: @PDFLATEX@: not found
> make[4]: *** [out-www/suffix-latex.pdf] Error 127
Oh, I should add that I definitely have pdflatex installed:
gperc...@gperciva-desktop:~/src/lilypond$ which
Am Mittwoch, 9. Juni 2010, 14:59:29 schrieben Sie:
> sorry, no joy:
>
> cd ./out-www && @PDFLATEX@ suffix-latex.tex
> /bin/sh: @PDFLATEX@: not found
> make[4]: *** [out-www/suffix-latex.pdf] Error 127
Did you run ./autogen.sh before? That is required so the check for pdflatex
and dblatex is actu
Hello,
Going on from the 'curly quotes' problem that was resolved a couple of
days back in our documentation, I noticed in the NR while scanning
through another 'odd' single quote mark after the hash (#) character.
\override #`(direction . ,UP)
instead of
\override #'(direction . ,UP)
See att
On Wed, Jun 9, 2010 at 6:34 AM, James Lowe wrote:
> I wondered if anyone can tell me if this is a mistake or what the
> significance of the back-quote is vs the standard singe quote?
It is intentional. Look up scheme's quasiquote and unquote functions.
-Jay
_
pkx166h wrote:
>
> Hello,
>
> Going on from the 'curly quotes' problem that was resolved a couple of
> days back in our documentation, I noticed in the NR while scanning
> through another 'odd' single quote mark after the hash (#) character.
>
> \override #`(direction . ,UP)
>
> instead of
>
Thanks Jay.
Jay Anderson wrote:
On Wed, Jun 9, 2010 at 6:34 AM, James Lowe wrote:
I wondered if anyone can tell me if this is a mistake or what the
significance of the back-quote is vs the standard singe quote?
It is intentional. Look up scheme's quasiquote and unquote functions.
-Jay
On Wed, Jun 9, 2010 at 5:00 AM, wrote:
> Having gotten approval from Graham and Neil, and having responded to
> Neil's comments, I'll go ahead and push. I'll also post the set that
> I'm pushing for completeness.
Wow, the CG looks *really* helpful now. Kudos!
Cheers,
Valentin
On Wed, 2010-06-09 at 12:26 +0200, Xavier Scheuer wrote:
> Hi Joe!
>
> Another bug involving the new vertical spacing system reported on
> LilyPond French Users mailing list.
>
> This one is concerning "before-title-spacing", which mess up with
> automatic page breaks (systems run off the page).
On Wed, Jun 9, 2010 at 2:34 PM, Reinhold Kainhofer
wrote:
> Am Mittwoch, 9. Juni 2010, 14:59:29 schrieben Sie:
>> sorry, no joy:
>
> Did you run ./autogen.sh before? That is required so the check for pdflatex
> and dblatex is actually done...
Ah, sorry. I ran ./configure, but not ./autogen.sh.
Hey!
>: (
;)
Valentin Villenave wrote:
On Wed, Jun 9, 2010 at 5:00 AM, wrote:
Having gotten approval from Graham and Neil, and having responded to
Neil's comments, I'll go ahead and push. I'll also post the set that
I'm pushing for completeness.
Wow, the CG looks *really* helpful now. Ku
Warning: @warning{} is a macro, and thus cannot handle blank lines.
Certain output formats might handle it, but it is *not* guaranteed to
work, and in fact it *doesn't* work in all output formats. (I think
that pdf is the difficult one)
if you really, really, really want multiple paragraphs in th
On 6/9/10 7:34 AM, "James Lowe" wrote:
> Hello,
>
> Going on from the 'curly quotes' problem that was resolved a couple of
> days back in our documentation, I noticed in the NR while scanning
> through another 'odd' single quote mark after the hash (#) character.
>
> \override #`(direction .
Thanks Xavier,
I opened Bug 1112. I have been fixing bugs and implementing new
features in the area of page breaking for some past while, so in all
probability I'll end up being the one fixing this, too -- because it is
the kind of bug which is likely to affect our book here, too.
BTW sho
Carl Sorensen writes:
> On 6/9/10 7:34 AM, "James Lowe" wrote:
>
>> Hello,
>>
>> Going on from the 'curly quotes' problem that was resolved a couple of
>> days back in our documentation, I noticed in the NR while scanning
>> through another 'odd' single quote mark after the hash (#) character.
On 6/9/10 9:40 AM, "Graham Percival" wrote:
> Warning: @warning{} is a macro, and thus cannot handle blank lines.
> Certain output formats might handle it, but it is *not* guaranteed to
> work, and in fact it *doesn't* work in all output formats. (I think
> that pdf is the difficult one)
>
Tha
2010/6/9 Boris Shingarov :
> Thanks Xavier,
Hi Boris.
You're welcome!
Reporting bugs is so little compared to the joy of using LilyPond or
compared to the work you all do in LilyPond development.
Actually I am the one that should say thanks. :D
> I opened Bug 1112. I have been fixing bugs an
On Wed, Jun 9, 2010 at 4:40 PM, James Lowe wrote:
> Hey!
>
>>: (
(I meant, compared to what *I* wrote, of course :)
Cheers,
V.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Op maandag 07-06-2010 om 16:44 uur [tijdzone +], schreef
n.putt...@gmail.com:
Hi Neil,
> I've just been testing this patch, and have stumbled upon a problem with
> chords. With this snippet,
Thanks for looking into this! I've added a fix for this; it appears
that a pango font (which specifi
21 matches
Mail list logo
