From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Why inbox-mode instead of default search?
Date: Wed, 30 Sep 2009 08:16:35 -0700 [thread overview]
Message-ID: <1254323181-sup-1735@masanjin.net> (raw)
In-Reply-To: <1254074517-sup-4465@kronos>
Reformatted excerpts from William Erik Baxter's message of 2009-09-27:
> 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.
How does the notion of killing a thread that makes sense except in the
context of having an special inbox mode?
> 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.
The inbox is magical, because you do different things with your inbox
than you do with non-inbox buffers: you classify threads into a) I'm
done with this thread for now, but let me know if someone replies
(archive); b) I'm done with this thread for now and don't let me know if
someone replies (kill); c) I'll deal with this later (ignore).
> 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.
I agree.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-09-30 15:16 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
2009-09-30 15:16 ` William Morgan [this message]
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=1254323181-sup-1735@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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