[imp] moving/deleting option

[Paul]

chuck> But that's not the meaning of a draft folder. I understand
chuck> Cliff and would like to see imp acting the way he suggested. If
chuck> the purging of resumed messages is only done in the user
chuck> defined draft folder you can create a template folder and use
chuck> this for your tasks.

jan> In my book, it _is_ the meaning of a drafts folder. Maybe not of
jan> a postponed- messages folder. But that's all semantics.

green> Yes, it is semantics, and therein lies the problem.  If it were
green> a clearcut distinction that the protocol supported, there'd be
green> less to argue about.

Well, current IMP allows an easy solution, assuming Chuck doesn't want
to be *too* pedantic. B^)

Just create a folder call "Postponed" and mark that as the "Draft"
folder for IMP. Then the folder Chuck calls Draft doesn't get played
with in unwanted ways and the IMP code doesn't need to be changed.

Then, document clearly that in the context of IMP, "Drafts" means
composition postponed for now, not Draft templates. We're all used to
context sensitive definitions, right? B^)

--
			Paul


>From chuck@horde.org Date: Tue,  4 Sep 2001 15:06:18 -0400
Return-Path: <chuck@horde.org>
Mailing-List: contact imp-help@lists.horde.org; run by ezmlm
Delivered-To: mailing list imp@lists.horde.org
Received: (qmail 24382 invoked from network); 4 Sep 2001 19:08:27 -0000
Received: from h00104bc60b3c.ne.mediaone.net (HELO marina.horde.org) (24.91.198.7)
  by horde.org with SMTP; 4 Sep 2001 19:08:27 -0000
Received: by marina.horde.org (Postfix, from userid 33)
	id D2FAB3D9F; Tue,  4 Sep 2001 15:06:18 -0400 (EDT)
Received: from 206.243.191.252 ( [206.243.191.252])
	as user chuck@localhost by marina.horde.org with HTTP;
	Tue,  4 Sep 2001 15:06:18 -0400
Message-ID: <999630378.3b95262ab02cc@marina.horde.org>
Date: Tue,  4 Sep 2001 15:06:18 -0400
From: Chuck Hagenbuch <chuck@horde.org>
To: imp@lists.horde.org
References: <Pine.HPX.4.33.0109040103310.27615-100000@rwja.umdnj.edu> <999617856.3b94f540d5108@marina.horde.org> <999618523.3b94f7dbb43c8@linux.wg.de> <999625672.3b9513c8b6272@marina.horde.org> <999627243.3b9519eb24fc0@grendel.umdnj.edu>
In-Reply-To: <999627243.3b9519eb24fc0@grendel.umdnj.edu>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs
Subject: Re: [imp] moving/deleting option

Quoting Cliff Green <green@UMDNJ.EDU>:

> For me, then, the next question is whether it's worthwhile to make it possible
> for a user to set such a preference, and make it the system administrator's
> choice of whether that's the default or not. Fortunately, at some point you 
> will have to make the choice of where feature-creep will stop for the imp
> distro, and this may be one of those things.  Anything else can be maintained 
> in local mods and the burden falls to the local admin.

I can see having a "delete drafts after sending" preference, if someone wants 
to provide a patch and a cogent description of it.

There are times when I'm a bit dismayed by all of the options we have. There 
are other times when I'm impressed that we manage to make it all work. It's a 
balancing act. :)

-chuck

--
Charles Hagenbuch, <chuck@horde.org>
Some fallen angels have their good reasons.


>From chuck@horde.org Date: Tue,  4 Sep 2001 15:07:12 -0400
Return-Path: <chuck@horde.org>
Mailing-List: contact imp-help@lists.horde.org; run by ezmlm
Delivered-To: mailing list imp@lists.horde.org
Received: (qmail 24954 invoked from network); 4 Sep 2001 19:09:17 -0000
Received: from h00104bc60b3c.ne.mediaone.net (HELO marina.horde.org) (24.91.198.7)
  by horde.org with SMTP; 4 Sep 2001 19:09:17 -0000
Received: by marina.horde.org (Postfix, from userid 33)
	id 0CB7E3D9F; Tue,  4 Sep 2001 15:07:13 -0400 (EDT)
Received: from 206.243.191.252 ( [206.243.191.252])
	as user chuck@localhost by marina.horde.org with HTTP;
	Tue,  4 Sep 2001 15:07:12 -0400
Message-ID: <999630432.3b952660e107b@marina.horde.org>
Date: Tue,  4 Sep 2001 15:07:12 -0400
From: Chuck Hagenbuch <chuck@horde.org>
To: imp@lists.horde.org
References: <200109041851.f84IpgL27181@ns1.pae.com>
In-Reply-To: <200109041851.f84IpgL27181@ns1.pae.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs
Subject: Re: [imp] moving/deleting option 

Quoting Paul <list-imp@dragon.net>:

> chuck> But that's not the meaning of a draft folder. I understand
> chuck> Cliff and would like to see imp acting the way he suggested. If
> chuck> the purging of resumed messages is only done in the user
> chuck> defined draft folder you can create a template folder and use
> chuck> this for your tasks.
> 
> jan> In my book, it _is_ the meaning of a drafts folder. Maybe not of
> jan> a postponed- messages folder. But that's all semantics.
> 
> green> Yes, it is semantics, and therein lies the problem.  If it were
> green> a clearcut distinction that the protocol supported, there'd be
> green> less to argue about.

You got your quotes rather wrong there, just fyi...

> Just create a folder call "Postponed" and mark that as the "Draft"
> folder for IMP. Then the folder Chuck calls Draft doesn't get played
> with in unwanted ways and the IMP code doesn't need to be changed.
> 
> Then, document clearly that in the context of IMP, "Drafts" means
> composition postponed for now, not Draft templates. We're all used to
> context sensitive definitions, right? B^)

I prefer Cliff's idea of a preference.

-chuck

--
Charles Hagenbuch, <chuck@horde.org>
Some fallen angels have their good reasons.