Sorry, William. I've been busy and haven't monitered the list. I'll probably set up a proper mail system tonight so I don't screw this up again.
> Reformatted excerpts from Andrei Thorp's message of 2009-10-18: >> - I've applyed Lloyd's patch for fixing the UTF-8 check. > > Which patch was this? The only "Lloyd patch" one I'm aware of is: > http://github.com/lloyd/sup/commit/d07986419b87053b41f7ed4bd7b6d1e537704864 No, that's not it... the patch that I applied is http://aur.archlinux.org/packages/sup/sup/fix-utf8-hack.patch. At least' that's my copy of it that I uploaded to the AUR. I'm assuming that Lloyd still has this in his repos somewhere. I'm not sure this patch is strictly necessary, but at the time I was under the impression that it seemed reasonable. Admittedly, I'm not a great Ruby programmer. Ah, here it is. http://github.com/lloyd/sup/commit/e32c48c4abfb921c60d337354634cd905f7e9149 >> The error up there doesn't really make sense. Each not defined on >> buffer strings? > >It makes sense to me. There's no String#each in Ruby 1.9, so this is >probably a (trivially fixable) bug in the lockfile gem for 1.9. I'm still not sure why this bug doesn't happen for me. Oh wait! Discovery! Sean left a comment on my AUR page stating, "It was just a stale lock file. removed ~/.sup/lock and it started up nicely." So never mind that, lockfile's fine in 1.9. As for trying things like ,n, I'll give it a whirl tonight. I need to set up my mail... I've been busy/putting it off :). Cheers! -Andrei Thorp _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
