From: Allan Wind <allan_wind@lifeintegrity.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] First impressions
Date: Mon, 23 Jan 2012 01:58:14 -0500 [thread overview]
Message-ID: <1327301754-sup-3169@lifeintegrity.com> (raw)
I was trying to see if sup v0.12.1 would be a suitable alternative to mutt but
first impressions are shaky. Is there a more stalbe version than the one from
installed vi gem? Help/insight appreciated.
As suggest in the new users guide I first ran sup-config, but that seem to
create a bad config and sup crashed on start-up with:
/var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/util.rb:601:in `method_missing': no Redwood::HookManager instance defined in method call to run! (RuntimeError)
from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup:370
from /var/lib/gems/1.8/bin/sup:19:in `load'
from /var/lib/gems/1.8/bin/sup:19
I am happy to send the .sup directory along if anyone are interested. Figured
there was nothing else to lose so I blew the .sup directory away, and found
that it was auto-created on start-up. Nice.
Next step was to add a source and the new users guide suggest using sup-add
with maildir://path/to/a/filename. This fails with:
allan@vent:~$ sup-add maildir://home/allan/mail/received
/var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/index.rb:106:in `initialize': DatabaseLockError: Unable to get write lock on /home/allan/.sup/xapian: already locked (IOError)
from /var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/index.rb:106:in `new'
from /var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/index.rb:106:in `load_index'
from /var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/index.rb:93:in `load'
from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:80
from /var/lib/gems/1.8/bin/sup-add:19:in `load'
from /var/lib/gems/1.8/bin/sup-add:19
so I quit sup and try it again and get this error:
allan@vent:~$ sup-add maildir://home/allan/mail/received
[Mon Jan 23 01:41:06 -0500 2012] Flushing Xapian updates to disk. This may take a while...
/var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/maildir.rb:17:in `initialize': maildir URI cannot have a host: home (ArgumentError)
from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:100:in `new'
from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:100
from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:87:in `each'
from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:87
from /var/lib/gems/1.8/bin/sup-add:19:in `load'
from /var/lib/gems/1.8/bin/sup-add:19
sup-add --help suggest a single slash alternative syntax which works (not sure
if this a code or doc defect):
For Maildir folders, use the form:
maildir:<path to Maildir directory>; or
maildir://<path to Maildir directory>
Next step was to convince sup to use a maildir instead of a mbox for sent
folder. Changing .sup/config.yml to:
:sent_source: maildir:/home/allan/mail/sent
seemed to be ignord even after adding it as a source as suggested in the email
archives.
Then I tried some of the searches listed in the "Searching your mail" wiki. In
particular I was trying to find all messages and came up short. I tried the
date searches (after:yesterday, before:tomorrow etc) but they returned nothing.
I was able to pull up things by lables, and was able to search with from:allan
OR to:allan. It puzzled me a bit that OR had to be upper case.
In writing this message I postposted (P) and I thought recalled the message with
R and then selected the newest version but the UI gives me the impression that
I end up with a draft each time I postpose a message. Maybe this is a feature
and I am just missing something here.
I know Q quits and q asks for confirmation. Is there a way to not have q ask
for confirmation? Sorry if this is documented somewhere, still going through
the mail archive and wiki.
Hope it helps,
/Allan
--
Allan Wind
Life Integrity, LLC
<http://lifeintegrity.com>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2012-01-23 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 6:58 Allan Wind [this message]
2012-01-28 5:14 ` Tracy Reed
2012-01-28 18:38 ` Allan Wind
2012-01-28 19:32 ` Patrick Totzke
2012-01-28 21:06 ` Allan Wind
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=1327301754-sup-3169@lifeintegrity.com \
--to=allan_wind@lifeintegrity.com \
--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