From: web-sup@superscript.com (William Erik Baxter)
Subject: [sup-talk] Why inbox-mode instead of default search?
Date: Sun, 27 Sep 2009 14:50:08 -0400 [thread overview]
Message-ID: <1254074517-sup-4465@kronos> (raw)
In-Reply-To: <1254073440-sup-2700@masanjin.net>
Excerpts from William Morgan's message of Sun Sep 27 13:46:00 -0400 2009:
> Reformatted excerpts from William Erik Baxter's message of 2009-09-27:
> > 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?
>
> Because there are two special actions that are specific to inboxes:
> archiving and killing.
Both modes support archive and kill in some form. So I don't understand how
this argues for splitting as opposed to consolidating the two modes. The need
for preallocated, special-purpose labels like inbox and killed seems clear
enough. However, minimizing the amount of magical behavior they exhibit also
seems beneficial, if only for the sake of consistency. Treating the inbox as
something other than an ordinary label search is magical.
> It would be easy enough to add a "|" command to inbox mode that would
> spawn a search buffer with label:inbox and the rest of your search
> terms.
A patch to add this command to inbox-mode appears in the August sup-talk
archive. I would like to see this feature become part of the base system.
Cheers, W.
next prev parent reply other threads:[~2009-09-27 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 17:04 William Erik Baxter
2009-09-27 17:46 ` William Morgan
2009-09-27 18:50 ` William Erik Baxter [this message]
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=1254074517-sup-4465@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