From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup crashed: NoMethodError
Date: Fri, 28 Aug 2009 13:41:41 -0700 [thread overview]
Message-ID: <1251492008-sup-6128@masanjin.net> (raw)
In-Reply-To: <20090827200317.GA3065@gmail.com>
Reformatted excerpts from Sean Escriva's message of 2009-08-27:
> so far I have tried a gem cleanup, gem uninstall sup, gem install -r
> sup, all to no avail. It still always crashes with the following:
>
> --- NoMethodError from thread: main
> undefined method `[]' for false:FalseClass
> /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup.rb:107:in `start'
> /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/bin/sup:161
> /usr/bin/sup:19:in `load'
> /usr/bin/sup:19
>
> Any tips on how to fix/figure out what I did wrong are greatly
> appreciated!
Hm, is your ~/.sup/config.yaml file empty for some reason? If so, delete
it and retry, and I will add some code to catch this case.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-08-28 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 20:03 Sean Escriva
2009-08-28 20:41 ` William Morgan [this message]
2009-08-28 22:50 ` Sean Escriva
2009-09-03 17:13 ` 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=1251492008-sup-6128@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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