[EMAIL PROTECTED]:~/music/bigaglia/amin/bmin$ lilypond-book sonate.lytex
lilypond-book (GNU LilyPond) 2.11.57
Reading sonate.lytex...
Running latex...latex:
SNIP
Processing...
Running lilypond...GNU LilyPond 2.10.33
Fontconfig error: Cannot load default config file
Traceback (most recent
Hello,
I'm typesetting a goncerto grosso -sort of score. Tried to group
concertino and ripieni with 'system start delimiters'. Output is as
hoped with .32 but different (not as hoped) with .33
Greetings,
Tapio
Here is a short example of input file and two .png files of output:
\version 2.10.0
My fault indeed. source-file.cc should have lower_bound, not
binary_search.
2006-09-19 Joe Neeman [EMAIL PROTECTED]
* lily/source-file.cc (get_line): lower_bound, not
binary_search. Fixes problem where point-and-click would
always point to the first line.
+
+
Tapio Tuovila kirjoitti:
My fault indeed. source-file.cc should have lower_bound, not
binary_search.
2006-09-19 Joe Neeman [EMAIL PROTECTED]
* lily/source-file.cc (get_line): lower_bound, not
binary_search. Fixes problem where point-and-click would
always point
Bertalan Fodor kirjoitti:
May it have only changed? (I.e. the first line is numbered as 0?)
Bert
I think you are right. I tested adding one extra line in the beginning
of the .ly file after compiling, and ta-daa! then point-and-click worked
OK. So, how to fix this?
Tapio
Hello,
it seems that in 2.9.18 generated pdf files all the textedit URIs point
to the 1st row of the .ly code while in 2.9.17 these seemed to be OK.
Also the console error messages show the problematic spots of the code,
but insist that all the problems are located in the first row of the source.
Han-Wen Nienhuys kirjoitti:
Graham Percival wrote:
The code below produces a whole bunch of errors of this kind:
programming error: Inf or NaN encountered
continuing, cross fingers
programming error: Insane offset
continuing, cross fingers
That's not so serious, but there's also a
Hi,
as no one seems to be particularly interested in this 'point and click
-stuff' I decided to elaborate my message a little:
Seems like something happened to pc between 2.7.36 and 2.7.37. I have
tested both versions from the GUB -package with the following input:
\paper {
ragged-right =
Hello,
I tried the 2.7.28-1 GUB on SuSE 10.0
The install script seems to work well both for home directory or
system-wide installation. The problem here is that lily fails to convert
the .ps to .pdf, no matter if the installation is in ~/lilypond or in
/usr/local/lilypond.
The resulting .ps
Hi,
using 2.7.12 on Suse 9.3 suggestAccidentals collide with beam.
{\key f \major
\set suggestAccidentals = ##t
f'8 g' a' bes'! }
\layout{raggedright = ##t}
- my best,
Tapio
___
bug-lilypond mailing list
bug-lilypond@gnu.org
10 matches
Mail list logo
