From: Peter Lutek <plutek@infinity.net>
To: <sup-talk@rubyforge.org>
Subject: [sup-talk] sup crashing on start
Date: Wed, 1 Dec 2010 14:05:37 -0500 [thread overview]
Message-ID: <11028.1291230337@infinity.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 640 bytes --]
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;
}greetings!
just this morning, i have been unable to start sup -- it is crashing
as soon as i try to start. the inbox buffer starts to show briefly,
but then sup immediately crashes. this is after a "sup-sync -a", but
i've been running this setup and doing "sup-sync -a" for many months
without issue.
any help would be greatly appreciated -- i'm currently resorting to
webmail. yuck!
sup 0.11
ruby 1.8
i've submitted a report at the sup bug tracker, and my
.sup/exception-log.txt is attached there -- see ID 135.
thanks in advance.... cheers!
.pltk.
[-- Attachment #1.2: Type: text/html, Size: 728 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
reply other threads:[~2010-12-01 19:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=11028.1291230337@infinity.net \
--to=plutek@infinity.net \
--cc=sup-talk@rubyforge.org \
/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