Hi Barton,

Thanks for all the comments! Many of the issues you bring up are real.
My current focus is on the backend to Sup 2.0, but in general I'm happy
to accept patches and merge requests to fix these issues.

Detailed comments inlined:

Reformatted excerpts from barton.schaefer's message of 2008-08-23:
> One suggestion for an improvement on the gmail interface:  Consider
> introducing a hierarchy syntax in labels. E.g., if I've got a label
> for "restaurants" I might create a label "restaurants/lunch" that
> means "first search for anything tagged restaraurants and then narrow
> by searching for anything also tagged lunch".

Personally I don't like the idea of adding structure to labels, because
this proposal (and others before it) are oriented at people with a lot
of labels, and I suspect that too many labels is a symptom that you're
doing something wrong.

That said, I know I'm crazy, and I would accept a patch that made this
an (optional!) feature. One easy way might be to make it solely a UI
tweak to LabelSearchMode, where any labels with a "/" in them are fit
into a pre-collapsed hierarchy instead of displayed in a big list.

> (Is it possible to search for messages based on which source they came
> from?)

Technically yes, but there's not a good interface on top of it. Search
for "source_id:X", where X is the numeric source id of the source, which
you have look up in sources.yaml.

> The default color scheme is pretty terrible.  (I did mention there'd
> be "nits".)

I like it, but maybe I'm just accustomed to it. It's configurable, and
I'd accept patches for the default, if, say, more than one other person
felt was better.

> When I widened my terminal window to try to see more of the preview
> text on the thread screen, sup didn't pick up on the size change.

I could never get SIGWINCH to work due to a weird interaction between
curses and Ruby threads. If you can, I'd be happy to accept a patch.
In the meantime, you can press ^L to redraw the screen, and Sup should
notice the change.

> There's either no on-screen help for how one builds up a search
> expression, or it's simply too hard to find that help, and in
> particular it wasn't obvious how one searches for all messages having
> a certain label (I was expecting maybe something like gmail's
> label:Xyz syntax).

The "label:asdf" syntax should work as you expect.

I agree that better search expression help would be nice. Patches
accepted. :)

> I happened to encounter a case of new mail arriving while I was using
> sup, wherein a colleague had replied to a message by editing the
> Subject such that his entire reply was there and the message body was
> empty.  Sup collapsed this into the thread and hid his new subject
> behind the original subject.  I had to bail out and switch over to
> alpine to figure out why he'd sent a seemingly empty message.

I think that if you had expanded the header (with 'h') while in
thread-view-mode, you would've seen the full subject.

> I have a LOT of IMAP folders (conservatively, hundreds), many of them
> in a shared hierarchy not under my control; sup's interface would be
> the perfect way to get a handle on these, but it would take me way too
> long to add them one by one as separate URL sources. 

Agreed. This has been on the todo list for a while.

> If you're going to have any hope of becoming the choice of nerds
> everywhere, you've got address the "play well with others" problem, at
> the very least with the IMAP INBOX, if not with other mailboxes.

Actually, I'm going to be taking a very different tack in Sup 2.0, and
not deal with IMAP at all. Sup will maintain its own document store, and
it's going to be up to the user to insert your mail into it.

I know that's probably not the answer you want. But I have no desire to
spend the requisite years of my life dealing with with hokey IMAP
servers, Ruby's hokey IMAP libraries, and everything in between. I've
taken a few steps down that path, but that's been more than enough to
recognize it as the path to madness.

-- 
William <[EMAIL PROTECTED]>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

Reply via email to