Hi, As an alternative, you can specify explicitely "python jallib.py ..." (I suppose you run it with "./jallib.py" or something like this). "svn diff -r1350:HEAD jallib.py" shows nothing about shebang line "#!/usr/bin/python", but if you "svn blame -r1350 jallib.py", you'll know who to blame :))))
My guess is "\r\n" can't be recognize by your shell (triedbash and zsh). I can't find a fix except overwrite it replacing "\r\n" with "\n"... But this can occur again. My suggestion is to use jallib wrapper. See "jallib" file (no .py extension), and fill env. vars, specially JALLIB_PYTHON. Put it in dir knows by PATH, and run it with "jallib reindent ...". I always use this. Mine looks like this: #!/bin/bash # ... ######################### # ENVIRONMENT VARIABLES # ######################### # Path to the jallib root's repository (containing "tools, export JALLIB_ROOT=$HOME/Documents/Projects/jallib # path to jallib root's libraries. export JALLIB_REPOS=$JALLIB_ROOT/include # path to jallib root's samples. export JALLIB_SAMPLEDIR=$JALLIB_ROOT/sample # path to "jalv2" executable. If not in your PATH, set an absolute path to the exec export JALLIB_JALV2="/home/sirloon/bin/jalv24l -long-start" ... ... #################### # python script # #################### # (advanced users) # uncomment the two last line, and comment the standalone call. ## path to "python" executable, if needed export JALLIB_PYTHON=python $JALLIB_PYTHON $JALLIB_ROOT/tools/jallib.py $* You can be very explicit with python interpreter version (and that's why I don't like the shebang way) export JALLIB_PYTHON=python2.5 Let me know if you have any problems. Cheers, Seb 2009/10/6 William <[email protected]> > > Hi Rob, > > Thanks for your reply. Let me try and do a better job of explaining. > If I get the very latest, I get the error stated above. So I started > testing older versions of the jallib.py script, until I found one that > works -- r1337. I suspect something broke in the r1350 revision of > jallib.py, perhaps it only shows up on Debian systems? > > Saying it another way -- I've been using the reindent feature > extensively here, and never had a problem until today, when I updated > my entire trunk to the latest. > > William > > > On Oct 6, 1:55 pm, Rob Hamerling <[email protected]> wrote: > > William wrote: > > > I did an svn update of the entire trunk, and now I get an error when I > > > try to use jallib.py reindent myfile.jal > > > > > The error is: /usr/bin/python^M: bad interpreter: No such file or > > > directory > > > > Isn't that a problem related to Python itself (or your system setup)? > > > > > I've spent 30 mins or so but I haven't found the problem. I rolled > > > back to previous versions of jallib.py and found that r1337 is OK, but > > > r1350 doesn't work. > > > > I didn't refresh the complete trunk, but SVN reports R1380, R1350 is dd > > 27 Sept. Maybe you should do a new checkout. > > > > reindent works fine here. > > > > Regards, Rob. > > > > -- > > Rob Hamerling, Vianen, NL (http://www.robh.nl/) > > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
