sup

A curses threads-with-tags style email client

sup-website.git

git clone https://supmua.dev/git/sup-website/

community/pipermail-archives/sup-talk/2012-01.txt (9432B) - raw

      1 From allan_wind@lifeintegrity.com  Mon Jan 23 01:58:14 2012
      2 From: allan_wind@lifeintegrity.com (Allan Wind)
      3 Date: Mon, 23 Jan 2012 01:58:14 -0500
      4 Subject: [sup-talk] First impressions
      5 Message-ID: <1327301754-sup-3169@lifeintegrity.com>
      6 
      7 I was trying to see if sup v0.12.1 would be a suitable alternative to mutt but
      8 first impressions are shaky.  Is there a more stalbe version than the one from
      9 installed vi gem?  Help/insight appreciated.
     10 
     11 As suggest in the new users guide I first ran sup-config, but that seem to
     12 create a bad config and sup crashed on start-up with:
     13 
     14 /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)
     15         from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup:370
     16         from /var/lib/gems/1.8/bin/sup:19:in `load'
     17         from /var/lib/gems/1.8/bin/sup:19
     18 
     19 I am happy to send the .sup directory along if anyone are interested.  Figured
     20 there was nothing else to lose so I blew the .sup directory away, and found
     21 that it was auto-created on start-up.  Nice.
     22 
     23 Next step was to add a source and the new users guide suggest using sup-add
     24 with maildir://path/to/a/filename.  This fails with:
     25 
     26 allan at vent:~$ sup-add maildir://home/allan/mail/received
     27 /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)
     28         from /var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/index.rb:106:in `new'
     29         from /var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/index.rb:106:in `load_index'
     30         from /var/lib/gems/1.8/gems/sup-0.12.1/lib/sup/index.rb:93:in `load'
     31         from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:80
     32         from /var/lib/gems/1.8/bin/sup-add:19:in `load'
     33         from /var/lib/gems/1.8/bin/sup-add:19
     34 
     35 so I quit sup and try it again and get this error:
     36 
     37 allan at vent:~$ sup-add maildir://home/allan/mail/received
     38 [Mon Jan 23 01:41:06 -0500 2012] Flushing Xapian updates to disk. This may take a while...
     39 /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)
     40         from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:100:in `new'
     41         from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:100
     42         from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:87:in `each'
     43         from /var/lib/gems/1.8/gems/sup-0.12.1/bin/sup-add:87
     44         from /var/lib/gems/1.8/bin/sup-add:19:in `load'
     45         from /var/lib/gems/1.8/bin/sup-add:19
     46 
     47 sup-add --help suggest a single slash alternative syntax which works (not sure
     48 if this a code or doc defect):
     49 
     50 For Maildir folders, use the form:
     51     maildir:<path to Maildir directory>; or
     52     maildir://<path to Maildir directory>
     53 
     54 Next step was to convince sup to use a maildir instead of a mbox for sent
     55 folder.  Changing .sup/config.yml to:
     56 
     57 :sent_source: maildir:/home/allan/mail/sent
     58 
     59 seemed to be ignord even after adding it as a source as suggested in the email
     60 archives.
     61 
     62 Then I tried some of the searches listed in the "Searching your mail" wiki.  In
     63 particular I was trying to find all messages and came up short.  I tried the
     64 date searches (after:yesterday, before:tomorrow etc) but they returned nothing.
     65 
     66 I was able to pull up things by lables, and was able to search with from:allan
     67 OR to:allan.  It puzzled me a bit that OR had to be upper case.
     68 
     69 In writing this message I postposted (P) and I thought recalled the message with
     70 R and then selected the newest version but the UI gives me the impression that
     71 I end up with a draft each time I postpose a message.   Maybe this is a feature
     72 and I am just missing something here.
     73 
     74 I know Q quits and q asks for confirmation.  Is there a way to not have q ask
     75 for confirmation?  Sorry if this is documented somewhere, still going through
     76 the mail archive and wiki.
     77 
     78 Hope it helps,
     79 
     80 
     81 /Allan
     82 -- 
     83 Allan Wind
     84 Life Integrity, LLC
     85 <http://lifeintegrity.com>
     86 
     87 From treed@ultraviolet.org  Sat Jan 28 00:14:14 2012
     88 From: treed@ultraviolet.org (Tracy Reed)
     89 Date: Fri, 27 Jan 2012 21:14:14 -0800
     90 Subject: [sup-talk] First impressions
     91 In-Reply-To: <1327301754-sup-3169@lifeintegrity.com>
     92 References: <1327301754-sup-3169@lifeintegrity.com>
     93 Message-ID: <20120128051414.GB3481@tracyreed.org>
     94 
     95 On Mon, Jan 23, 2012 at 01:58:14AM -0500, Allan Wind spake thusly:
     96 > I was trying to see if sup v0.12.1 would be a suitable alternative to mutt but
     97 > first impressions are shaky.  
     98 
     99 I went through the very same process. I've given up on sup and am sticking with
    100 mutt for the time being.. The developers aren't really doing anything with sup
    101 other than minor bug fixes. They prefer to work on heliotrope which is the
    102 successor to sup. sup itself doesn't have a future as far as I can tell. While
    103 I love the tagging and configurability via a nice programming language I found
    104 it crashed a lot too.
    105 
    106 -- 
    107 Tracy Reed
    108 http://tracyreed.org
    109 Digital signature attached for your safety.
    110 -------------- next part --------------
    111 A non-text attachment was scrubbed...
    112 Name: not available
    113 Type: application/pgp-signature
    114 Size: 189 bytes
    115 Desc: not available
    116 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20120127/6dac9268/attachment-0001.bin>
    117 
    118 From allan_wind@lifeintegrity.com  Sat Jan 28 13:38:01 2012
    119 From: allan_wind@lifeintegrity.com (Allan Wind)
    120 Date: Sat, 28 Jan 2012 13:38:01 -0500
    121 Subject: [sup-talk] First impressions
    122 In-Reply-To: <20120128051414.GB3481@tracyreed.org>
    123 References: <1327301754-sup-3169@lifeintegrity.com>
    124 	<20120128051414.GB3481@tracyreed.org>
    125 Message-ID: <20120128183801.GF25519@lifeintegrity.com>
    126 
    127 On 2012-01-27 21:14:14, Tracy Reed wrote:
    128 > I went through the very same process. I've given up on sup and am sticking with
    129 > mutt for the time being.. The developers aren't really doing anything with sup
    130 > other than minor bug fixes. They prefer to work on heliotrope which is the
    131 > successor to sup. sup itself doesn't have a future as far as I can tell. While
    132 > I love the tagging and configurability via a nice programming language I found
    133 > it crashed a lot too.
    134 
    135 Thanks Tracy.
    136 
    137 
    138 /Allan
    139 -- 
    140 Allan Wind
    141 Life Integrity, LLC
    142 <http://lifeintegrity.com>
    143 
    144 From patricktotzke@googlemail.com  Sat Jan 28 14:32:19 2012
    145 From: patricktotzke@googlemail.com (Patrick Totzke)
    146 Date: Sat, 28 Jan 2012 19:32:19 -0000
    147 Subject: [sup-talk] First impressions
    148 In-Reply-To: <20120128183801.GF25519@lifeintegrity.com>
    149 References: <1327301754-sup-3169@lifeintegrity.com>
    150 	<20120128051414.GB3481@tracyreed.org>
    151 	<20120128183801.GF25519@lifeintegrity.com>
    152 Message-ID: <20120128193219.16698.23541@brick.lan>
    153 
    154 Hi Allan and everybody else who might be interested;
    155 Apologies in advance for the spam.
    156 
    157 I can recommend switching to notmuch [0], a mail indexer that started of as some improvements to sup
    158 but has grown into a very reliable and powerful mail indexer.
    159 
    160 Notmuch uses Xapian to provide a mail indexing library and bindings for go, python and ruby are
    161 included. There are several user interfaces that make use of this library:
    162 Apart from a command-line binary there is an Emacs mode and a few attempts to integrate notmuch into mutt.
    163 I am the author of a terminal interface [2] that uses notmuch's python bindings and the urwid [1] toolkit
    164 to provide a MUA experience similar to that of sup.
    165 
    166 Notmuch is very stable, very fast and under active development of a mid-sized group of excellent
    167 developers.
    168 
    169 Hope this helps, looking forward to discussions in #notmuch at freenode,
    170 /p
    171 
    172 [0] http://notmuchmail.org
    173 [1] http://excess.org/urwid
    174 [2] https://github.com/pazz/alot
    175 
    176 From allan_wind@lifeintegrity.com  Sat Jan 28 16:06:35 2012
    177 From: allan_wind@lifeintegrity.com (Allan Wind)
    178 Date: Sat, 28 Jan 2012 16:06:35 -0500
    179 Subject: [sup-talk] First impressions
    180 In-Reply-To: <20120128193219.16698.23541@brick.lan>
    181 References: <1327301754-sup-3169@lifeintegrity.com>
    182 	<20120128051414.GB3481@tracyreed.org>
    183 	<20120128183801.GF25519@lifeintegrity.com>
    184 	<20120128193219.16698.23541@brick.lan>
    185 Message-ID: <20120128210635.GB29628@lifeintegrity.com>
    186 
    187 On 2012-01-28 19:32:19, Patrick Totzke wrote:
    188 > I can recommend switching to notmuch [0], a mail indexer that started of as some improvements to sup
    189 > but has grown into a very reliable and powerful mail indexer.
    190 
    191 Thanks for the pointer.  I installed it earlier this week and 
    192 integrated into offlineimap for (re)indexing of new email.
    193 
    194 > Notmuch uses Xapian to provide a mail indexing library and bindings for go, python and ruby are
    195 > included. There are several user interfaces that make use of this library:
    196 > Apart from a command-line binary there is an Emacs mode and a few attempts to integrate notmuch into mutt.
    197 
    198 I am trying to convince mutt-kz (which has notmuch integration) 
    199 to compile without much luck.
    200 
    201 > I am the author of a terminal interface [2] that uses notmuch's python bindings and the urwid [1] toolkit
    202 > to provide a MUA experience similar to that of sup.
    203 
    204 The dependencies of alot makes this a bit of a challenge to run 
    205 on Debian stable:
    206 
    207 Alot depends on recent versions of notmuch (>=0.10) and urwid 
    208 (>=1.0). Note that due to restrictions on argparse and 
    209 subprocess, you need to run *python v>=2.7*,
    210 
    211 > Notmuch is very stable, very fast and under active development of a mid-sized group of excellent
    212 > developers.
    213 > 
    214 > Hope this helps, looking forward to discussions in #notmuch at freenode,
    215 
    216 Thanks again.
    217 
    218 
    219 /Allan
    220 -- 
    221 Allan Wind
    222 Life Integrity, LLC
    223 <http://lifeintegrity.com>
    224