Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities
Comment #16 on issue 1555 by k-ohara5...@oco.net: Multiple warnings concerning staff-affinities http://code.google.com/p/lilypond/issues/detail?id=1555 The existing warning makes no sense at all to me. The warning should indicate that the problem is has to do with vertical spacing LilyPond is making a guess on how to fix it for you and be printed just once per inconsistency in the input file. warning: adjacent non-staff lines have incompatible settings for vertical spacing; changing staff-affinity. Proposed patch at http://codereview.appspot.com/4278058 The collision aspect of this report (comment 2, item 2) has been split-off into issue 1564. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond v2.13.54
hello, On 17 Mar 2011, at 17:53, -Eluze elu...@gmail.com wrote: Phil Holmes-2 wrote: -Eluze elu...@gmail.com wrote in message news:31173816.p...@talk.nabble.com... Phil Holmes-2 wrote: I've rechecked my system and found an odd feature. Lilypond 13.54 is in the PATH shown in the Windows System Properties Environment Variables. But it's not there if I type PATH in a command window! Could you check what your system has? it's in both! Did you uninstall the previous versions before installing LP, or modify the PATH? I'm just wondering whether the install checks whether a work like lilypond is already in the path, and doesn't do an update if it exists? this time i uninstalled - usually i just delete or move the latest version to an external drive - then i cleaned the path (8 times c:\program files\lilypond\usr\bin) and then i installed lilypond (without creating a shortcut) - and the path was ok again, i.e. with 1 lilypond record. lilypond certainly does not check the path or clean up when installing or uninstalling. --- The installer must do something. Else you'd either never have LilyPond in you PATH or you'd have dozens of them as it concatenated the PATH every time you installed new. @Ming Can you tell us if you run add/remove programs before you install a later version? and if so what version did you have installed before 2.13.54? James ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly
[Please keep the cc to the bug-lilypond list, so that others may help.] On 18 Mar 2011, at 02:58, Isambard Khroustaliov wrote: Thanks for this, running otool I get: Zeit-2:~ zeit$ otool -arch i386 -L /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so: /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.10.0) /usr/cross/i686-apple-darwin8/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.2) and nothing when I use the -arch x86_64 flag ... I'm guessing then, that it needs to be re-compiled for x86_64, however, i'm afraid I've no idea how to go about doing that ... When I rnn otool -arch i386 -L /Applications/LilyPond.app/Contents/Resources/bin/lilypond otool -arch x86_64 -L /Applications/LilyPond.app/Contents/Resources/bin/lilypond the binary only calls 32-bit libraries. So it seems that when you compile whatever is calling midi.so with GCC, you should add the -arch i386 flag. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 773 in lilypond: melisma centered i.s.o. left-aligned when using \melisma
Updates: Status: Fixed Owner: tdaniels...@googlemail.com Labels: fixed_2_13_55 Comment #6 on issue 773 by tdaniels...@googlemail.com: melisma centered i.s.o. left-aligned when using \melisma http://code.google.com/p/lilypond/issues/detail?id=773 There is an easier fix, which I've now pushed 8d1d9740b8d0ed9a2315909c7fdcccdf68894889 after checking all vocal sections in NR are OK and reg tests run clean. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond v2.13.54
James Lowe james.l...@datacore.com wrote in message news:cb5b3d13-9e78-4f2f-94fa-d161c78a8...@datacore.com... hello, On 17 Mar 2011, at 17:53, -Eluze elu...@gmail.com wrote: Phil Holmes-2 wrote: -Eluze elu...@gmail.com wrote in message news:31173816.p...@talk.nabble.com... Phil Holmes-2 wrote: I've rechecked my system and found an odd feature. Lilypond 13.54 is in the PATH shown in the Windows System Properties Environment Variables. But it's not there if I type PATH in a command window! Could you check what your system has? it's in both! Did you uninstall the previous versions before installing LP, or modify the PATH? I'm just wondering whether the install checks whether a work like lilypond is already in the path, and doesn't do an update if it exists? this time i uninstalled - usually i just delete or move the latest version to an external drive - then i cleaned the path (8 times c:\program files\lilypond\usr\bin) and then i installed lilypond (without creating a shortcut) - and the path was ok again, i.e. with 1 lilypond record. lilypond certainly does not check the path or clean up when installing or uninstalling. --- The installer must do something. Else you'd either never have LilyPond in you PATH or you'd have dozens of them as it concatenated the PATH every time you installed new. @Ming Can you tell us if you run add/remove programs before you install a later version? and if so what version did you have installed before 2.13.54? James === If you don't uninstall, it does appear simply to add the latest path to your path variable. I ended up unable to run things like PING from my command line, and found it was because there were so many lilypond paths that the PATH variable had overflowed. -- Phil Holmes Bug Squad -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile
Comment #2 on issue 1562 by percival.music.ca: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 James, have you succeeded in duplicating this behaviour on a clean windows 7 machine? Since nobody else has seen the same error, I'm tempted to mark this invalid. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems
Updates: Labels: fixed_2_13_54 Comment #7 on issue 1565 by percival.music.ca: Changing staff with manual beaming can give very long stems http://code.google.com/p/lilypond/issues/detail?id=1565 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion
Updates: Labels: -Patch-abandoned fixed_2_13_53 Comment #11 on issue 839 by percival.music.ca: Enhancement: improving midi2ly conversion http://code.google.com/p/lilypond/issues/detail?id=839 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1073 in lilypond: convert-ly and accented characters
Comment #7 on issue 1073 by paconet@gmail.com: convert-ly and accented
characters
http://code.google.com/p/lilypond/issues/detail?id=1073
I think it would be useful to have a description of the bug right here.
The problem arises from convert-ly or midi2ly commands when they are given
as argument a filename which contains any accented character.
For example
convert-ly minué.ly
or
midi2ly minué.midi
output from convert-ly is
convert-ly (GNU LilyPond) 2.13.55
Traceback (most recent call last):
File /usr/local/bin/convert-ly, line 369, in module
main ()
File /usr/local/bin/convert-ly, line 356, in main
do_one_file (f)
File /usr/local/bin/convert-ly, line 243, in do_one_file
ly.stderr_write (_ (Processing `%s\'... ) % infile_name)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 4:
ordinal not in range(128)
output from midi2ly is
Traceback (most recent call last):
File /usr/local/bin/midi2ly, line 1207, in module
main ()
File /usr/local/bin/midi2ly, line 1204, in main
convert_midi (f, o)
File /usr/local/bin/midi2ly, line 1047, in convert_midi
progress (_ (%s output to `%s'...) % ('LY', out_file))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 4:
ordinal not in range(128)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.
Comment #8 on issue 1349 by jan.nieuwenhuizen: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 Thanks. FWIW, I used it for schikkers list and I haven't seen any segfaults, guile stable-2.0: f80ed1be I was almost going to suggest to push it to master. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
Francisco Vila schreef op vr 18-03-2011 om 12:46 [+0100]:
2011/3/14 Graham Percival gra...@percival-music.ca:
File /usr/local/bin/midi2ly, line 1047, in convert_midi
progress (_ (%s output to `%s'...) % ('LY', out_file))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
4: ordinal not in range(128)
patch in
http://lists.gnu.org/archive/html/lilypond-devel/2011-03/msg00420.html
from Jan is applied.
Interesting. For me it works (see below). I assume you did
make -C python?
Waitaminute. Ah, I have a utf-8 locale. You must set LANG=C
for it to break. see below below. With new patch.
Jan.
16:11:00 janneke@vuurvlieg:~/vc/lilypond
$ PATH=~/vc/lilypond/out/bin:$PATH lilypond minué
GNU LilyPond 2.13.55
Verwerken van `minué.ly'
Ontleden...
minué.ly:0: waarschuwing: geen \version uitdrukking gevonden, voeg
\version 2.13.55
toe voor toekomstige compatibiliteit
Vertolken van muziek...
MIDI uitvoer naar minué.midi...
succes: Samenstellen met succes voltooid
16:11:18 janneke@vuurvlieg:~/vc/lilypond
$ PATH=~/vc/lilypond/out/bin:$PATH midi2ly minué
LY uitvoer naar `minué-midi.ly'...
=
$ PATH=~/vc/lilypond/out/bin:$PATH LANG=c midi2ly minué
Traceback (most recent call last):
File /home/janneke/vc/lilypond/out/bin/midi2ly, line 1207, in
module
main ()
File /home/janneke/vc/lilypond/out/bin/midi2ly, line 1204, in main
convert_midi (f, o)
File /home/janneke/vc/lilypond/out/bin/midi2ly, line 1047, in
convert_midi
progress (_ (%s output to `%s'...) % ('LY', out_file))
File /home/janneke/vc/lilypond/out/bin/midi2ly, line 106, in
progress
ly.encoded_write (errorport, s + '\n')
File
/home/janneke/vc/lilypond/out/lib/lilypond/current/python/lilylib.py,
line 57, in encoded_write
f.write (s.encode (f.encoding or 'utf-8'))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in
position 18: ordinal not in range(128)
--
Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
From e72b10e90e8fec6f19866f2165bc1f16179426f9 Mon Sep 17 00:00:00 2001
From: Jan Nieuwenhuizen jann...@gnu.org
Date: Thu, 17 Mar 2011 21:44:05 +0100
Subject: [PATCH] lilylib: handle encodings. Fixes #1073 and u#714213.
---
python/lilylib.py | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/python/lilylib.py b/python/lilylib.py
index 3bf77f6..6fb96bb 100644
--- a/python/lilylib.py
+++ b/python/lilylib.py
@@ -47,13 +47,19 @@ underscore = _
# Urg, Python 2.4 does not define stderr/stdout encoding
# Maybe guess encoding from LANG/LC_ALL/LC_CTYPE?
+reload (sys)
+sys.setdefaultencoding ('utf-8')
+import codecs
+sys.stdout = codecs.getwriter ('utf8') (sys.stdout)
+sys.stderr = codecs.getwriter ('utf8') (sys.stderr)
+
def encoded_write(f, s):
-f.write (s.encode (f.encoding or 'utf_8'))
+f.write (s.encode (f.encoding or 'utf-8', 'replace'))
# ugh, Python 2.5 optparse requires Unicode strings in some argument
# functions, and refuse them in some other places
def display_encode (s):
-return s.encode (sys.stderr.encoding or 'utf_8')
+return s.encode (sys.stderr.encoding or 'utf-8', 'replace')
# Lilylib globals.
program_version = '@TOPLEVEL_VERSION@'
--
1.7.1
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
2011/3/18 Jan Nieuwenhuizen janneke-l...@xs4all.nl:
Francisco Vila schreef op vr 18-03-2011 om 12:46 [+0100]:
2011/3/14 Graham Percival gra...@percival-music.ca:
File /usr/local/bin/midi2ly, line 1047, in convert_midi
progress (_ (%s output to `%s'...) % ('LY', out_file))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
4: ordinal not in range(128)
patch in
http://lists.gnu.org/archive/html/lilypond-devel/2011-03/msg00420.html
from Jan is applied.
Interesting. For me it works (see below). I assume you did
make -C python?
Yes, I did.
Waitaminute. Ah, I have a utf-8 locale. You must set LANG=C
for it to break. see below below. With new patch.
New patch applied, 'convert-ly minué.ly' and midi2ly minué.midi still
fail, sorry.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
Francisco Vila schreef op vr 18-03-2011 om 17:03 [+0100]: New patch applied, 'convert-ly minué.ly' and midi2ly minué.midi still fail, sorry. Well, thanks for testing I guess... However, if there's any chance of me fixing this, I'm going to need a bit more information. For example, what's your locale. Does LANG=c ... midi2ly also fail? What's the exact command you use? What's the error message. Things like that. ;-) Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile
Comment #3 on issue 1562 by pkx1...@hotmail.com: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 I have not succeeded on 3 attempts on 3 different cleanly installed Windows 7 VMs :( but it still fails on my two machines that I use LP generally on. So I guess it is invalid, just not for me - I'll continue to try to pin down the culprit in my own 'space and time' so to speak. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
RE: midi2ly crashed with UnicodeDecodeError in convert_midi()
Christian Fillion schreef op vr 18-03-2011 om 12:16 [-0400]: Here a full report generated by Apport (on Ubuntu 10.10). https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/714213 Yes, I've seen that. This should be fixed by my first patch, even. I need the specifics to produce te crash with my second patch applied. Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
2011/3/18 Jan Nieuwenhuizen janneke-l...@xs4all.nl:
Christian Fillion schreef op vr 18-03-2011 om 12:16 [-0400]:
Here a full report generated by Apport (on Ubuntu 10.10).
https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/714213
Yes, I've seen that. This should be fixed by my first patch,
even. I need the specifics to produce te crash with my
second patch applied.
my output from 'locale' is
LANG=es_ES.UTF-8
LANGUAGE=es_ES:en
LC_CTYPE=es_ES.UTF-8
LC_NUMERIC=es_ES.UTF-8
LC_TIME=es_ES.UTF-8
LC_COLLATE=es_ES.UTF-8
LC_MONETARY=es_ES.UTF-8
LC_MESSAGES=es_ES.UTF-8
LC_PAPER=es_ES.UTF-8
LC_NAME=es_ES.UTF-8
LC_ADDRESS=es_ES.UTF-8
LC_TELEPHONE=es_ES.UTF-8
LC_MEASUREMENT=es_ES.UTF-8
LC_IDENTIFICATION=es_ES.UTF-8
LC_ALL=
'git show HEAD' tells
diff --git a/python/lilylib.py b/python/lilylib.py
index 3bf77f6..6fb96bb 100644
--- a/python/lilylib.py
+++ b/python/lilylib.py
(...)
# functions, and refuse them in some other places
def display_encode (s):
-return s.encode (sys.stderr.encoding or 'utf_8')
+return s.encode (sys.stderr.encoding or 'utf-8', 'replace')
i.e. your second patch is applied. Then I do
rm python/*.pyc
make -C python/
make
sudo make install
lilypond minué.ly
then
midi2ly minué.midi
LANG= midi2ly minué.midi
LANG=C midi2ly minué.midi
LANG=c midi2ly minué.midi
convert-ly minué.ly
LANG= convert-ly minué.ly
LANG=C convert-ly minué.ly
LANG=c convert-ly minué.ly
all fail with
$ midi2ly minué.midi
Traceback (most recent call last):
File /usr/local/bin/midi2ly, line 1207, in module
main ()
File /usr/local/bin/midi2ly, line 1204, in main
convert_midi (f, o)
File /usr/local/bin/midi2ly, line 1047, in convert_midi
progress (_ (%s output to `%s'...) % ('LY', out_file))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
4: ordinal not in range(128)
and
$ convert-ly minué.ly
convert-ly (GNU LilyPond) 2.13.55
Traceback (most recent call last):
File /usr/local/bin/convert-ly, line 369, in module
main ()
File /usr/local/bin/convert-ly, line 356, in main
do_one_file (f)
File /usr/local/bin/convert-ly, line 243, in do_one_file
ly.stderr_write (_ (Processing `%s\'... ) % infile_name)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
4: ordinal not in range(128)
respectively.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities
Updates: Labels: Patch-new Comment #17 on issue 1555 by percival.music.ca: Multiple warnings concerning staff-affinities http://code.google.com/p/lilypond/issues/detail?id=1555 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile
Updates: Status: Invalid Comment #4 on issue 1562 by percival.music.ca: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 ok. If you can find out more info, then by all means re-open this (or report a new issue). ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
Francisco Vila schreef op vr 18-03-2011 om 18:57 [+0100]: 2011/3/18 Jan Nieuwenhuizen janneke-l...@xs4all.nl: i.e. your second patch is applied. Then I do rm python/*.pyc make -C python/ make sudo make install Eek, why not PATH=$(pwd)/out/bin:$PATH midi2ly ? midi2ly minué.midi LANG= midi2ly minué.midi LANG=C midi2ly minué.midi LANG=c midi2ly minué.midi convert-ly minué.ly LANG= convert-ly minué.ly LANG=C convert-ly minué.ly LANG=c convert-ly minué.ly all fail with Weird. It says: replace and that's what happens over here. Can you please double-check that the function with 'replace' is being used? Eg, edit /usr/share/lilypond/2.13.55/python/lilylib.py to read def display_encode (s): print 'Yes we are here' return s.encode (sys.stderr.encoding or 'utf-8', 'replace') Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Beaming rules may cause oddness when using hideNotes
Greetings everybody,
I've just stumbled upon the following piece of code, and it took me a
while to understand what was going wrong (although, granted, I should
know better).
\new Staff
\new Voice { \voiceOne
\set tieWaitForNote = ##t
c''16~ b''~ c'' b''8~ b''2.
}
\new Voice { \voiceTwo
s8
\hideNotes
c''~
\unHideNotes
c''8. d''16 c''2
}
Printed scores usually use 2+2 beaming for 4/4 time signatures, but
they revert to 4+4+4+4 whenever there's a silence or a trick such as
the one above. In this particular case, the (attached) output is
clearly not something one would expect to happen by default; that
being said, I'm not sure the beaming rules can be made more
intelligent (see #638, for example). Perhaps it's just something to
document? (Or maybe that's just me ;)
Thanks!
Valentin.
attachment: toto.preview.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
2011/3/18 Jan Nieuwenhuizen janneke-l...@xs4all.nl: Francisco Vila schreef op vr 18-03-2011 om 18:57 [+0100]: 2011/3/18 Jan Nieuwenhuizen janneke-l...@xs4all.nl: i.e. your second patch is applied. Then I do rm python/*.pyc make -C python/ make sudo make install Eek, why not PATH=$(pwd)/out/bin:$PATH midi2ly ? This way both commands work perfectly. Does this imply that make install is not doing its work? The good news is that reverting the patch both commands become broken again. midi2ly minué.midi LANG= midi2ly minué.midi LANG=C midi2ly minué.midi LANG=c midi2ly minué.midi convert-ly minué.ly LANG= convert-ly minué.ly LANG=C convert-ly minué.ly LANG=c convert-ly minué.ly all fail with Weird. It says: replace and that's what happens over here. Can you please double-check that the function with 'replace' is being used? Eg, edit /usr/share/lilypond/2.13.55/python/lilylib.py in my case it's /usr/local/share/lilypond/... to read def display_encode (s): print 'Yes we are here' return s.encode (sys.stderr.encoding or 'utf-8', 'replace') No, I've put that mark but it is not shown. We are not using that very function. Why on Earth? -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
On Fri, Mar 18, 2011 at 11:50:38PM +0100, Francisco Vila wrote: /usr/share/lilypond/2.13.55/python/lilylib.py in my case it's /usr/local/share/lilypond/... Silly question: do you have lilypond installed with your package manager? I mean, when you run midi2ly or which midi2ly does it run an executable in /usr/bin/midi2ly, or /usr/local/bin/midi2ly ? Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
Francisco Vila schreef op vr 18-03-2011 om 23:50 [+0100]: 2011/3/18 Jan Nieuwenhuizen janneke-l...@xs4all.nl: Francisco Vila schreef op vr 18-03-2011 om 18:57 [+0100]: 2011/3/18 Jan Nieuwenhuizen janneke-l...@xs4all.nl: Eek, why not PATH=$(pwd)/out/bin:$PATH midi2ly ? This way both commands work perfectly. Does this imply that make install is not doing its work? No, it just means that you're most probably not running the midi2ly (or importing the lilylib.py) that you think you're running (or importing). The good news is that reverting the patch both commands become broken again. Good, I think we should apply it, then. in my case it's /usr/local/share/lilypond/... Sure No, I've put that mark but it is not shown. We are not using that very function. Why on Earth? We are using it, but you're running a different file. def display_encode (s): print 'Yes we are here' return s.encode (sys.stderr.encoding or 'utf-8', 'replace') 23:57:19 janneke@vuurvlieg:~/vc/lilypond $ LANG=C PATH=~/vc/lilypond/out/bin:$PATH midi2ly minué Yes we are here LY output to `minu?-midi.ly'... Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
2011/3/18 Graham Percival gra...@percival-music.ca: On Fri, Mar 18, 2011 at 11:50:38PM +0100, Francisco Vila wrote: /usr/share/lilypond/2.13.55/python/lilylib.py in my case it's /usr/local/share/lilypond/... Silly question: do you have lilypond installed with your package manager? No! that would be 2.12.3. Just checked. I also have not our distributed package installed. I mean, when you run midi2ly or which midi2ly does it run an executable in /usr/bin/midi2ly, or Don't have that. /usr/local/bin/midi2ly ? Yes, there is a midi2ly there. 'which' confirms. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond v2.13.54
Ming, On 18 Mar 2011, at 10:58, MING TSANG tsan...@rogers.commailto:tsan...@rogers.com wrote: Here is the sequence steps: 1. uninstall v2.13.53 (uninstall program came with lilypond) 2. Do PATH on command prompt - lilypond still on the path 3. install v.13.54 4. Do PATH on command prompt 5. Do lilypond http://D2F.ly D2F.lyhttp://D2F.ly After step 3, system tell me 1 virus deleted (I did not notice two days ago when I first install v2.13.53) below is the command prompt display. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Administratorpath PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\jZ ip;C:\WINDOWS\system32\gs\gs7.05\bin;C:\Program Files\jEdit;C:\Program Files\Qui ckTime\QTSystem\;C:\Program Files\LilyPond\usr\bin;C:\Program Files\LilyPond\usr \bin C:\Documents and Settings\Administratorpath PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\jZ ip;C:\WINDOWS\system32\gs\gs7.05\bin;C:\Program Files\jEdit;C:\Program Files\Qui ckTime\QTSystem\;C:\Program Files\LilyPond\usr\bin;C:\Program Files\LilyPond\usr \bin C:\Documents and Settings\Administratorcd desktop\lily_pond C:\Documents and Settings\Administrator\Desktop\LILY_PONDlilypond http://D2F.ly D2F.lyhttp://D2F.ly 'lilypond' is not recognized as an internal or external command, operable program or batch file. While the two statements Are not expected, they shouldn't stop the command being run as the PATH to LilyPond looks correct. Just to be sure can you open your cmd prompt, cd into your directory with your .ly file in it, now open windows explorer and find the LilyPond binary (it should be in 'bin') now drag this binary to the command window and drop it on it. This should now list the absolute path to the binary and then simply add your .ly file to the end of the command as normal and see if that runs correctly. Else all I can suggest at this time is to uninstall LilyPond and before re-installing it, use the procedure I gave you to edit the PATH but this time delete the two PATH statements (including the semi colon) then reinstall it again and see if the PATH is there and the command runs. James ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
