From: sho.fukamachi@gmail.com (Sho Fukamachi)
Subject: [sup-talk] NoMethodError running sup-config
Date: Fri, 25 Jan 2008 21:35:30 +1100 [thread overview]
Message-ID: <DDD895BC-24BA-45F4-A895-2647E83D41DB@gmail.com> (raw)
In-Reply-To: <1201220266-sup-191@south>
On 25/01/2008, at 11:26 AM, William Morgan wrote:
> Nope, this is an Official Bug. Sorry! The following minor patch should
> fix it. Git master and next have been updated with this.
Great, I cloned it and ran from there. The problem is fixed, but
exposed another problem when it tried to do a sup-add, which also
errored out. I was able, however, to do the sup-add manually without
further issue. Weirdly, my friend also running leopard didn't have any
issue at all. Maybe a gem I have installed? She was running stock, I
have a billion gems installed for dev work.
Anyway, thanks for your help! I really like sup .. it's a joy to use.
One more thing: there seem to be pretty severe display errors when I
display (and scroll through) japanese mail. I'm not really sure how to
go about troubleshooting what's wrong. Shall I make a new thread here,
or send you the mail I have in mind which exposes the problem directly?
thanks!
Sho
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2429 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080125/9ce505ed/attachment.bin
next prev parent reply other threads:[~2008-01-25 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 8:11 Sho Fukamachi
2008-01-25 0:26 ` William Morgan
2008-01-25 10:35 ` Sho Fukamachi [this message]
2008-01-30 17:14 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DDD895BC-24BA-45F4-A895-2647E83D41DB@gmail.com \
--to=sho.fukamachi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox