From: Markus Klinik <m.klinik@gmx.de>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] One buffer for each account at startup
Date: Mon, 03 Aug 2015 12:37:58 +0200 [thread overview]
Message-ID: <1438594989-sup-9384@x200> (raw)
In-Reply-To: <1436078354-sup-7697@ruthard-lappi>
Excerpts from Ruthard Baudach's message of 2015-07-05 09:07:20 +0200:
> Hello Pablo,
>
> Sup has a search and label based approach to accessing mail, not an
> account based one. Actually there is no special "Inbox buffer", it's
> just a normal buffer presenting the result of the search `label:inbox`.
> (Well, granted, it is kind of special as it is built in)
Hi,
I thought about this some time ago, here is what I came up with.
> To display all emails of an account, search n the inbox buffer by
> pressing `/` for `to:my.name@my.isp`.
This search won't turn up emails where you are in BCC, nor emails sent to
mailing lists this account is subscribed to.
> You can save typing time by autolabeling messages in the
> before-add-message hook, searching for `label:work`
Letting sup label messages and then search for those labels is indeed
what you want. A better way than the before-add-message hook however is
to associate labels with sources. Check the documentation for the
--labels option of sup-add. You may want to auto-archive messages that
are not from your main account. That's what the --archive flag of sup-add
does. Then you can switch between sources by using the label filter
function 'L'.
The downside to this method is that the archived vs read functionality
doesn't work with the auto-archived sources. When you view the mails from
such a source, you always see all of them.
If I understand correctly, Inbox is just a label that sup gives to
incoming mails per default, and the archive key 'a' toggles this label. I
don't have this set up, but it should be possible to combine
- labels for sources
- not auto-archiving them
- and saved searches involving the Inbox label
to mimic multiple inboxes.
This doesn't answer Pablo's original question about having multiple inbox
buffers at startup though, but I think this is as far as you can get
without hacking sup.
Cheers,
Markus
prev parent reply other threads:[~2015-08-03 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 7:51 Pablo O
2015-07-05 7:07 ` [sup] " Ruthard Baudach
2015-08-03 10:37 ` Markus Klinik [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=1438594989-sup-9384@x200 \
--to=m.klinik@gmx.de \
--cc=supmua@googlegroups.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