From: andrei@andreimaxim.ro (Andrei Maxim)
Subject: [sup-talk] Skipped '.'
Date: Thu, 29 Nov 2007 03:05:02 +0200 [thread overview]
Message-ID: <a630bbc30711281705r3df5f40au11940deb886625f0@mail.gmail.com> (raw)
Hi again guys,
I'm trying to move away from Gmail (mostly because I hate to top post and
because I'd like to be able to read my emails when I'm offline) to A Better
Email Client and sup seems a very interesting solution. But the ride isn't
as smooth as I thought it would be.
I did a sup-config and then a sup-sync. Everything went fine. But when I'm
starting sup, all I get is "Skipped '.'" and then exits:
$ sup
Skipped '.'
$
I tried to google around, but it seems to be an odd error. What might be the
problem? Is there a log or something similar?
I'm running Mac OS X 10.4, I have ncurses installed, I installed every
dependency for sup and I have the latest 0.3.
Thanks,
--
Andrei Maxim
http://andreimaxim.ro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/sup-talk/attachments/20071129/ce461bce/attachment.html
next reply other threads:[~2007-11-29 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 1:05 Andrei Maxim [this message]
2007-11-29 5:44 ` William Morgan
2007-11-29 6:54 ` Andrei Maxim
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=a630bbc30711281705r3df5f40au11940deb886625f0@mail.gmail.com \
--to=andrei@andreimaxim.ro \
/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