sup

A curses threads-with-tags style email client

sup-website.git

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

community/pipermail-archives/sup-devel/2011-12.txt (11397B) - raw

      1 From dmishd@gmail.com  Sat Dec 17 13:46:07 2011
      2 From: dmishd@gmail.com (Hamish D)
      3 Date: Sat, 17 Dec 2011 18:46:07 +0000
      4 Subject: [sup-devel] [PATCH] Don't fail on empty lines while expanding
      5 In-Reply-To: <1318500554-sup-8811@qwerzila>
      6 References: <1318500554-sup-8811@qwerzila>
      7 Message-ID: <CAOxvSbc_S9grJVZxjTT3e1jepE53y9Y5ZYgy-n9QRboVMQvLzA@mail.gmail.com>
      8 
      9 Applied to next.
     10 
     11 Hamish
     12 
     13 On 13 October 2011 11:10, Gaute Hope <eg at gaute.vetsj.com> wrote:
     14 > While expanding an GPG signature which must have contained a line that
     15 > ended up as nil while chomp'ing, chomp will crash. This patch filters
     16 > out lines which are nil.
     17 > ---
     18 > ?lib/sup/modes/thread-view-mode.rb | ? ?2 +-
     19 > ?1 files changed, 1 insertions(+), 1 deletions(-)
     20 >
     21 > diff --git a/lib/sup/modes/thread-view-mode.rb b/lib/sup/modes/thread-view-mode.rb
     22 > index 9fcc45d..ec1a82e 100644
     23 > --- a/lib/sup/modes/thread-view-mode.rb
     24 > +++ b/lib/sup/modes/thread-view-mode.rb
     25 > @@ -846,7 +846,7 @@ private
     26 > ? ? ? else
     27 > ? ? ? ? width = buffer.content_width
     28 > ? ? ? end
     29 > - ? ? ?lines = lines.map { |l| l.chomp.wrap width }.flatten
     30 > + ? ? ?lines = lines.map { |l| l.chomp.wrap width if l }.flatten
     31 > ? ? end
     32 > ? ? return lines
     33 > ? end
     34 > --
     35 > 1.7.7
     36 >
     37 > _______________________________________________
     38 > Sup-devel mailing list
     39 > Sup-devel at rubyforge.org
     40 > http://rubyforge.org/mailman/listinfo/sup-devel
     41 
     42 From michael+sup@stapelberg.de  Mon Dec 19 18:42:20 2011
     43 From: michael+sup@stapelberg.de (Michael Stapelberg)
     44 Date: Mon, 19 Dec 2011 23:42:20 +0000
     45 Subject: [sup-devel] Status of Heliotrope/Turnsole?
     46 Message-ID: <1324338016-sup-6248@stapelberg.de>
     47 
     48 Hi William,
     49 
     50 I am wondering what the current status of Heliotrope/Turnsole is? I threw my
     51 mails into it and from the first few minutes with it, it seems pretty usable (I
     52 didn?t have an in-depth look, though).
     53 
     54 Do you recommend it for daily use?
     55 
     56 Which features are missing until you want to make the first release? Do you
     57 need any help with anything?
     58 
     59 Is there a migration path for sup users (to migrate labels, hooks, configfile)?
     60 
     61 Best regards,
     62 Michael
     63 
     64 From wmorgan@masanjin.net  Mon Dec 19 19:31:42 2011
     65 From: wmorgan@masanjin.net (William Morgan)
     66 Date: Mon, 19 Dec 2011 16:31:42 -0800
     67 Subject: [sup-devel] Status of Heliotrope/Turnsole?
     68 In-Reply-To: <1324338016-sup-6248@stapelberg.de>
     69 References: <1324338016-sup-6248@stapelberg.de>
     70 Message-ID: <1324340519-sup-5614@typhon>
     71 
     72 Hi Michael,
     73 
     74 Excerpts from Michael Stapelberg's message of 2011-12-19 15:42:20 -0800:
     75 > I am wondering what the current status of Heliotrope/Turnsole is? I
     76 > threw my mails into it and from the first few minutes with it, it
     77 > seems pretty usable (I didn?t have an in-depth look, though).
     78 > 
     79 > Do you recommend it for daily use?
     80 
     81 I have been using it for my personal email for a couple weeks now, so
     82 it's certainly possible. I don't know if I would recommend it. The
     83 obvious issues are:
     84 
     85 Turnsole:
     86 - Communication with the server is still mostly synchronous, which means
     87   the UI is very laggy unless the server is running on the same machine.
     88   I'm slowly working on fixing this (there is a good async mechanism in
     89   there; I just have to move all the operaitons over).
     90 - The addressbook / favorites stuff isn't in there, so you have to type
     91   everyone's email address out by hand all the time. Irritating.
     92 - No drafts. Irritating.
     93 
     94 Heliotrope:
     95 - I occasionally see weirdnesses in search. Specifically, labels being
     96   "forgotten" by the server for a brief time period, and repeated
     97   searches of the same query getting "stuck" on later result pages for
     98   no apparent reason.
     99 
    100 > Which features are missing until you want to make the first release?
    101 > Do you need any help with anything?
    102 
    103 The above list is what I'm interested in help with and is basically my
    104 0.1 release goal, though possibly drafts and addressbook can be left
    105 out.
    106 
    107 > Is there a migration path for sup users (to migrate labels, hooks,
    108 > configfile)?
    109 
    110 The hooks and config file will probably have to be done manually.
    111 There's not really a 1-to-1 mapping.
    112 
    113 But to the above release-ready list you can add another big one: being
    114 able to import your sup mail into heliotrope, including labels and
    115 message state. Right now you can basically do this if you have only one
    116 mail source in sup. Multiple mail sources require Heliotrope being able
    117 to reorder the index. I have code for this (bin/heliotrope-reindex) but
    118 when I tried it I found some weird bugs, so I have to figure this one
    119 out.
    120 
    121 Hope that's helpful. Now that I'm using it every day, I'm pretty
    122 motivated to fix these things. :)
    123 -- 
    124 William <wmorgan at masanjin.net>
    125 
    126 From wmorgan@masanjin.net  Wed Dec 28 17:23:06 2011
    127 From: wmorgan@masanjin.net (William Morgan)
    128 Date: Wed, 28 Dec 2011 14:23:06 -0800
    129 Subject: [sup-devel] Status of Heliotrope/Turnsole?
    130 In-Reply-To: <1324340519-sup-5614@typhon>
    131 References: <1324338016-sup-6248@stapelberg.de> <1324340519-sup-5614@typhon>
    132 Message-ID: <1325110949-sup-9638@tw-mbp-wmorgan.local>
    133 
    134 Excerpts from William Morgan's message of Mon Dec 19 16:31:42 -0800 2011:
    135 > - Communication with the server is still mostly synchronous
    136 
    137 Fixed.
    138 
    139 > - I occasionally see weirdnesses in search.
    140 
    141 Fixed.
    142 -- 
    143 William <w at masanjin.net>
    144 
    145 From wmorgan@masanjin.net  Fri Dec 30 00:50:46 2011
    146 From: wmorgan@masanjin.net (William Morgan)
    147 Date: Thu, 29 Dec 2011 21:50:46 -0800
    148 Subject: [sup-devel] Ruby 1.8 compatibility patches for Heliotrope and
    149 	Turnsole.
    150 In-Reply-To: <CA+ogd7HSKVpt27u6vcqi9LAjWmSWvvtaMgHv8eE9XgAxz_RpxQ@mail.gmail.com>
    151 References: <CA+ogd7HSKVpt27u6vcqi9LAjWmSWvvtaMgHv8eE9XgAxz_RpxQ@mail.gmail.com>
    152 Message-ID: <1325223938-sup-1516@tw-mbp-wmorgan.local>
    153 
    154 Excerpts from Robin Burchell's message of Tue Dec 13 08:46:30 -0800 2011:
    155 > I recently tried Turnsole/Heliotrope from git. I'm forced (thanks to
    156 > Fedora) to use Ruby 1.8, and noticed there were at least one issue in
    157 > both Heliotrope and Turnsole. Patches attached.
    158 
    159 Thank you. I've applied the IMAP one. The escapeHTML issue I believe
    160 I've fixed elsewise. Please let me know if it doesn't work for you.
    161 
    162 As for the string encoding error, I'm reluctant to apply string encoding
    163 patches like that because they tend to infect the entire codebase. (Sup
    164 is a good example of this.) If you can figure out the source of the
    165 corrupted string, then we can fix the problem at the point where it's
    166 brought into the system rather than having to fix every possible place.
    167 
    168 > P.S. Did you take a look at
    169 > http://www.mail-archive.com/sup-devel at rubyforge.org/msg01071.html ?
    170 > I'm interested in two-way sync as much as is sanely possible (both
    171 > gmail and regular imap), without it, I sadly don't think I'll ever be
    172 > able to become more than a casual observer.
    173 
    174 I am more than happy that someone is working on this, but it's not a
    175 problem I personally want to address. I would rather make Heliotrope so
    176 awesome that it's worth switching to, and provide easy exit mechanisms
    177 so that you aren't trapped.
    178 -- 
    179 William <w at masanjin.net>
    180 
    181 From matthieu.rakotojaona@gmail.com  Fri Dec 30 02:39:35 2011
    182 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
    183 Date: Fri, 30 Dec 2011 08:39:35 +0100
    184 Subject: [sup-devel] Ruby 1.8 compatibility patches for Heliotrope and
    185 	Turnsole.
    186 In-Reply-To: <1325223938-sup-1516@tw-mbp-wmorgan.local>
    187 References: <CA+ogd7HSKVpt27u6vcqi9LAjWmSWvvtaMgHv8eE9XgAxz_RpxQ@mail.gmail.com>
    188 	<1325223938-sup-1516@tw-mbp-wmorgan.local>
    189 Message-ID: <CAMiZLn2k-AqQ-XOQenu-kSDKhRjg-nF7Pch++cpjr8fX_6whqg@mail.gmail.com>
    190 
    191 On Fri, Dec 30, 2011 at 6:50 AM, William Morgan <wmorgan at masanjin.net> wrote:
    192 >> P.S. Did you take a look at
    193 >> http://www.mail-archive.com/sup-devel at rubyforge.org/msg01071.html ?
    194 >> I'm interested in two-way sync as much as is sanely possible (both
    195 >> gmail and regular imap), without it, I sadly don't think I'll ever be
    196 >> able to become more than a casual observer.
    197 >
    198 > I am more than happy that someone is working on this, but it's not a
    199 > problem I personally want to address.
    200 
    201 I am currently working on a IMAP frontend to heliotrope [0]. It is not
    202 entirely functional yet (mostly has encoding errors), but it's more or
    203 less functional. Coded with love, not expertise.
    204 
    205 Problem : to use this, you will have to use a modified version of
    206 heliotrope (mostly only a new method in heliotrope-client to fetch
    207 only messageinfos and not the whole body if needed). I'll send a merge
    208 request when I have the time, that is next year.
    209 
    210 Happy new year !
    211 
    212 [0] https://github.com/rakoo/imaptrope
    213 -- 
    214 Matthieu RAKOTOJAONA
    215 
    216 From wmorgan-sup@masanjin.net  Fri Dec 30 14:35:29 2011
    217 From: wmorgan-sup@masanjin.net (William Morgan)
    218 Date: Fri, 30 Dec 2011 11:35:29 -0800
    219 Subject: [sup-devel] Ruby 1.8 compatibility patches for Heliotrope and
    220 	Turnsole.
    221 In-Reply-To: <CAMiZLn2k-AqQ-XOQenu-kSDKhRjg-nF7Pch++cpjr8fX_6whqg@mail.gmail.com>
    222 References: <CA+ogd7HSKVpt27u6vcqi9LAjWmSWvvtaMgHv8eE9XgAxz_RpxQ@mail.gmail.com>
    223 	<1325223938-sup-1516@tw-mbp-wmorgan.local>
    224 	<CAMiZLn2k-AqQ-XOQenu-kSDKhRjg-nF7Pch++cpjr8fX_6whqg@mail.gmail.com>
    225 Message-ID: <1325273627-sup-7605@typhon>
    226 
    227 Excerpts from Matthieu Rakotojaona's message of 2011-12-29 23:39:35 -0800:
    228 > I am currently working on a IMAP frontend to heliotrope [0].
    229 
    230 This is something I'm really excited about having, since it means you
    231 will be able to read your email from all sorts of other clients,
    232 including your phone.
    233 
    234 > Problem : to use this, you will have to use a modified version of
    235 > heliotrope (mostly only a new method in heliotrope-client to fetch
    236 > only messageinfos and not the whole body if needed). I'll send a merge
    237 > request when I have the time, that is next year.
    238 
    239 That shouldn't be a problem to merge in.
    240 -- 
    241 William <wmorgan at masanjin.net>
    242 
    243 From wmorgan-sup@masanjin.net  Fri Dec 30 15:31:24 2011
    244 From: wmorgan-sup@masanjin.net (William Morgan)
    245 Date: Fri, 30 Dec 2011 12:31:24 -0800
    246 Subject: [sup-devel] importing your sup email into heliotrope
    247 Message-ID: <1325277038-sup-3185@tw-mbp-wmorgan.local>
    248 
    249 If you're feeling adventurous, here is how to import your Sup email into
    250 Heliotrope. This might break horribly for you--no guarantees. Bug
    251 reports are welcome.
    252 
    253 1. Install heliotrope and its dependencies. There is no gem yet, so
    254    follow the instructions at https://github.com/wmorgan/heliotrope.
    255 
    256 2. Dump your sup labels to a file by running sup-dump > <dumpfile>.
    257 
    258 3. Import your mail sources into heliotrope. Mbox and maildir sources
    259    should go pretty quick; IMAP, as usual, will be very slow. For each
    260    source you can do this:
    261 
    262      $HELIOTROPE_DIR> ruby -Ilib bin/heliotrope-import --dir <mailstore dir> --sup-dumpfile <dumpfile> --mbox <mbox file>
    263 
    264    Or replace "--mbox <mbox file>" with the corresponding argument to
    265    your source (use --help to see them all).
    266 
    267 4. Add your ~/.sup/drafts.mbox file using the same commands.
    268 
    269 5. Finally, reorder the index so that messages appear in order:
    270 
    271      $HELIOTROPE_DIR> ruby -Ilib bin/heliotrope-reindex --reorder --dir <mailstore dir>
    272      $HELIOTROPE_DIR> mv <mailstore dir>/index <mailstore dir>/index-old
    273      $HELIOTROPE_DIR> mv <mailstore dir>/index-reindexed <mailstore dir>/index
    274 
    275 6. Start the server:
    276 
    277      $HELIOTROPE_DIR> ruby -Ilib bin/heliotrope-server --dir <mailstore dir>
    278 
    279 Point your web browser to http://localhost:8042 and see if that works!
    280 If it looks good, you can also try and get turnsole working, for a
    281 Sup-like client: https://github.com/wmorgan/turnsole.
    282 
    283 Good luck and have fun!
    284 -- 
    285 William <w at masanjin.net>
    286