From: gsf@fruct.us (Gabriel Sean Farrell)
Subject: [sup-talk] Persistence between IMAP clients
Date: Wed, 6 Feb 2008 17:37:33 -0500 [thread overview]
Message-ID: <20080206223733.GA13929@manheim.library.drexel.edu> (raw)
In-Reply-To: <1202248916-sup-1460@south>
On Tue, Feb 05, 2008 at 02:02:37PM -0800, William Morgan wrote:
> Reformatted excerpts from William Morgan's message of 2008-02-05:
> > Sup will probably never work well in this kind of setup.
>
> Until we make SupServer!
>
Something like SupServer could be exciting. Along with its shortcomings
in the display department, mutt also suffers in a multiple-client-IMAP
setup. For example, I see no reason why I should keep aliases and list
subscriptions for each client.
next prev parent reply other threads:[~2008-02-06 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 15:12 Gabriel Sean Farrell
2008-02-04 18:46 ` John Bent
2008-02-05 21:03 ` Gabriel Sean Farrell
2008-02-05 16:42 ` William Morgan
2008-02-05 19:12 ` Magnus Therning
2008-02-05 19:51 ` William Morgan
2008-02-05 21:11 ` Gabriel Sean Farrell
2008-02-05 22:02 ` William Morgan
2008-02-06 22:37 ` Gabriel Sean Farrell [this message]
2008-02-07 8:45 ` Marcus Williams
2008-02-07 18:12 ` William Morgan
2008-02-07 20:12 ` Gabriel Sean Farrell
2008-02-07 21:09 ` Marcus Williams
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=20080206223733.GA13929@manheim.library.drexel.edu \
--to=gsf@fruct.us \
/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