From: Tero Tilus <tero@tilus.net>
To: Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Need a simple check / nice error message for user error on mbox being a dir
Date: Thu, 27 Jan 2011 22:59:00 +0200 [thread overview]
Message-ID: <1296161278-sup-5120@tilus.net> (raw)
In-Reply-To: <AANLkTimwsQMLrpLgtWKjZ6A35b81MrR9Tomxq67VD3dr@mail.gmail.com>
Andrei Thorp, 2011-01-27 21:16:
> Scanning mbox:/var/spool/mail/thought...
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/mbox.rb:155:in
> `gets': Is a directory - /var/spool/mail/thought (Errno::EISDIR)
...
> Obviously a simple user error here. Would be nice if sup knew to throw
> a nicer error here. Not a big deal!
Did you mean sup should detect if mbox source actually points to a
maildir (was /var/spool/mail/thought a maildir?) and suggest a
correction to configuration or that sup wouldn't crash but reported
"/var/spool/mail/thought Is a directory. File was expected."
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-01-27 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 19:16 Andrei Thorp
2011-01-27 20:59 ` Tero Tilus [this message]
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=1296161278-sup-5120@tilus.net \
--to=tero@tilus.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