Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] not moving msgs to /cur in Maildir?
Date: Mon, 19 Jul 2010 22:46:41 -0400	[thread overview]
Message-ID: <1279593880-sup-4595@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1279591667-sup-6537@gerlach.ca>

Excerpts from Eric Gerlach's message of Mon Jul 19 22:15:17 -0400 2010:

> I've also just started with sup, and though I don't know about sup's
> behaviour (I think it should be moving mail from new/ to cur/ as
> well)

I haven't looked at the most recent Maildir changes[1], but as is
sup's way it hasn't traditionally altered the filesystem at all.  It
treats all mail sources as read-only, which in this case means it
doesn't do the ln new/foo cur/foo; rm new/foo steps.

HTH.
-Ben

[1] There was talk of implementing this as one step toward having sup
    play nicer with other MUA's.
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-07-20  2:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20  2:00 David Rysdam
2010-07-20  2:15 ` Eric Gerlach
2010-07-20  2:46   ` Ben Walton [this message]
2010-07-20  9:51     ` Sven Moritz Hallberg
2010-07-20 11:07       ` Damien Leone
2010-07-20 14:37         ` Sven Moritz Hallberg
2010-07-20 14:52 ` David Rysdam

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=1279593880-sup-4595@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --cc=sup-talk@rubyforge.org \
    /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