Mats Bengtsson wrote:
Graham, I hope you have seen my previous reply in this thread.
Sorry, I missed it! :(
Thanks as always Mats. Sorry about this mix-up, Hernan. This bug has
been added as:
http://code.google.com/p/lilypond/issues/detail?id=349
Cheers,
- Graham
_
Graham, I hope you have seen my previous reply in this thread.
Here's a minimal version of Hernan's example.
\version "2.10.0"
\new TabStaff {
e4 c4 e,2 | % ok
% following C note is out of the range of the guitar
% This makes LilyPond crash. Commenting the following
% line produces normal output
hernan gonzalez wrote:
Perhaps some trouble with non-ascii chars or long lines...
Here it goes again, below. I also uploaded it here:
http://hjg.com.ar/ghibli/musica/testcase3.ly
Please test it with 2.10.20 or .21. I cannot compile your example in
.21; I suspect that the problem is your neste
Perhaps some trouble with non-ascii chars or long lines...
Here it goes again, below. I also uploaded it here:
http://hjg.com.ar/ghibli/musica/testcase3.ly
Cheers
--
Hernán J. González
http://hjg.com.ar/
%%%
\version "2.8.0"
\include "english.ly"
% test case:
I'm having trouble compiling your example. Could you please create a
minimal example? See
http://lilypond.org/web/devel/participating/bugs
for some tips.
Cheers,
- Graham
hernan gonzalez wrote:
Perhaps not really a bug, but an inconvenience anyway:
When the TabStaff finds a note that is ou
Perhaps not really a bug, but an inconvenience anyway:
When the TabStaff finds a note that is out of the range of the
instrument, it dies with an ugly and cryptic "low level" error
message, with no indication about the measure or line where the error
is found (or even what the problem is about).
