From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
Subject: [sup-talk] Beginner questions
Date: Mon, 05 May 2008 14:09:41 -0400 [thread overview]
Message-ID: <1210009778-sup-6833@cabinet> (raw)
In-Reply-To: <481E5936.7040600@gmail.com>
Excerpts from yanghatespam's message of Sun May 04 20:47:50 -0400 2008:
> When dealing with IMAP servers, does sup store its labels as IMAP
> keywords (i.e., are they stored on the server)?
By default no modification is made to your mail source. There are
recent discussions about the reason for this and what sorts of
write-back might/might not be accepted as patches in the future.
> (3) How does sup group messages into the same thread? Does it rely on
> References: header fields, subject-matching,
> body-substring-matching/overlap, or something else?
Default behavior seems (I haven't looked at that code) to be to use the
References and In-Reply-To headers. There's an option you can turn on
in config.yaml thread_by_subject which seems to do what it says.
> (4) yanghatespam at gmail.com is the account I use for mailing lists. I
> use many lists, so I needed a way to cope with the large message volume.
> Most of the time, I am only interested in the threads in which I have
> been a participant (e.g., I'm interested in replies to my posts). I
> have Gmail filters that use simple heuristics like "If my name is in the
> email, leave it marked as unread; otherwise mark it read." This, of
> course, leads to many false positives/negatives (Gmail's filterts are
> only so expressive).
>
> If sup's thread-grouping is decent, then it would be neat/more accurate
> to extend sup somehow to instead use these groupings for the filtering.
> I.e., if an incoming message is grouped with a thread in which I was a
> participant, then leave it marked unread; otherwise, mark it read.
I believe what you are looking for is a custom before-add-message hook.
That gets passed a message object. You might have to operate on the
References: header of that message to get to the information you're
looking for (I think threads only exist at the presentation level), but
it should be possible to get at least most of the way to what you're
looking for.
The power of hooks is that you have an entire programming language
available for this kind of computation if you want it.
See `sup --list-hooks` and http://sup.rubyforge.org/wiki/wiki.pl?Hooks
for more information.
> (6) Scrolling through the buffer that is immediately presented to me
> when starting sup, I only see about 3 pages of threads. Is this
> correct? How do I get to the rest?
'M' to load more messages, or '!!' to load everything. You can
interrupt the latter with ^G. These work for any thread-index, not just
the inbox, so if a search returns a lot of results, you get the same
behavior.
> (7) Does sup support Unicode? The inbox display seems to be a bit
> screwy for me (extraneous floating characters, things changing when
> highlighted, etc.), though it could also be my terminal (I'm using
> putty, but I just verified that I'm running it in UTF-8 mode).
Yes, it does. However, the stock Ruby ncurses gem doesn't handle wide
characters well. See http://sup.rubyforge.org/wiki/wiki.pl?UTF8 for
information on how to deal with this.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080505/e324e364/attachment.bin>
next prev parent reply other threads:[~2008-05-05 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 0:47 Yang Zhang
2008-05-05 1:02 ` Daniel Wagner
2008-05-05 2:08 ` Yang Zhang
2008-05-05 18:09 ` Marc Hartstein [this message]
2008-05-05 18:29 ` Yang Zhang
2008-05-19 23:38 ` William Morgan
2008-05-06 2:15 ` Christopher Warrington
2008-05-05 2:48 kendall at clarkparsia.com
2008-05-19 23:44 ` William Morgan
2008-08-03 23:17 Thorsten Kramer
2008-08-04 1:41 ` William Morgan
2008-08-05 21:52 ` Thorsten Kramer
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=1210009778-sup-6833@cabinet \
--to=marc.hartstein@alum.vassar.edu \
/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