Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: web-sup@superscript.com (William Erik Baxter)
Subject: [sup-talk] Why inbox-mode instead of default search?
Date: Sun, 27 Sep 2009 13:04:39 -0400	[thread overview]
Message-ID: <1254070015-sup-5151@kronos> (raw)

Why does sup have a separate mode for viewing the inbox rather than simply
applying a default search (possibly configurable) and displaying the results
with search-results-mode?  Like a number of other posters to the list, I wanted
to refine my inbox search.  But the requisite key binding exists only in
search-results-mode and not in inbox-mode.

Using inbox as an ordinary label with search-results-mode instead of inbox-mode
offers several advantages over the separate inbox-mode: less code, less
separate modality, ability to refine the inbox search.  It introduces the
possibility of closing the inbox window, readily addressed with a key binding
to perform the default search.  What are the disadvantages?  One loses the
difference in the archiving behavior between the two modes.  The inbox label
would appear in the label editors.  The program may need new code to handle a
new no-windows case.  Perhaps efficiency considerations enter here. 

Thanks, W.


             reply	other threads:[~2009-09-27 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 17:04 William Erik Baxter [this message]
2009-09-27 17:46 ` William Morgan
2009-09-27 18:50   ` William Erik Baxter
2009-09-30 15:16     ` William Morgan
2009-09-30 16:12       ` Carl Worth
2009-09-30 17:47         ` Rich Lane
2009-09-30 18:04           ` William Morgan
2009-09-30 19:12           ` Carl Worth

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=1254070015-sup-5151@kronos \
    --to=web-sup@superscript.com \
    /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