Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] What's your sup workflow (and a spew of ideas)
Date: Wed, 19 Aug 2009 16:21:08 -0700	[thread overview]
Message-ID: <1250723746-sup-4632@yoom.home.cworth.org> (raw)
In-Reply-To: <1250649270-sup-2166@zyrg.net>

Excerpts from Rich Lane's message of Tue Aug 18 20:02:57 -0700 2009:
> Excerpts from Carl Worth's message of Tue Aug 18 21:58:55 -0400 2009:
> > Maybe a page on the wiki?
> 
> Sure, I added an example to the end of the Hooks page.

Excellent. That looks very helpful.

And looking closer at the hooks wiki page, I see that it shows me how
to label incoming mail with ruby code, (which I've been wanting to
switch to instead of using maildrop to deliver mail to different
maildirs, and sup adding labels based on the source).

The hooks page also shows me how to display the number of unread
messages in a thread like I wanted, (though I'll still propose that
for sup itself rather than relying on a user hook for this).

So thanks for the encouragement to take a closer look at this page.

> I'm glad to know there are other people annoyed by UI race conditions :).
> Even after a quick look at the code I'm not sure what ThreadViewMode
> will do when a thread is added to. It might actually archive/read/etc
> new messages but not display them.

That was definitely my fear.

> I'd like a keybinding to reload/redisplay the thread and a status bar
> note if there are new messages. Any label changes should only affect
> messages that have been displayed. What do you think?

Only affecting messages that have been displayed is the critical
piece, yes. Adding a status bar notice would be a nice addition.

-Carl
-------------- 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/20090819/62013666/attachment.bin>


      parent reply	other threads:[~2009-08-19 23:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 21:02 Carl Worth
2009-08-18 21:46 ` Carl Worth
2009-08-18 22:07 ` Andrei Thorp
2009-08-18 22:16   ` Carl Worth
2009-08-18 23:02 ` Rich Lane
2009-08-19  1:58   ` Carl Worth
2009-08-19  3:02     ` Rich Lane
2009-08-19 14:03       ` Andrei Thorp
2009-08-19 23:21       ` Carl Worth [this message]

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=1250723746-sup-4632@yoom.home.cworth.org \
    --to=cworth@cworth.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