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/) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
