On Thu, 16 Oct 2003 21:46:45 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
VZ> EV> 6 - Some of the lists I receive are quite volumnous. Usually I will VZ> EV> archive these once a month to save on the sort/open times for each VZ> EV> folder. On trying to create a filter that would move files received VZ> EV> before a certain date, I was unsuccessful. I tried every Windows date VZ> EV> format I could find (mm/dd/yy, mm/dd/yyyy, dd mmm yy, etc.) and a few VZ> EV> attempts at expressions (Win32 regex, *NIX regex, pcre) and each time VZ> EV> the filter would move all the messages in a folder. VZ> VZ> I think that something like "if ( now() - date() > 30 )" should do it. The VZ> dates are expressed in days and it's not very useful to use date() as is as VZ> it counts the days since Epoch... VZ> VZ> EV> Could a default "Archive" function be added that would find the correct VZ> EV> received date and move all messages older than the specified date to a VZ> EV> designated folder? VZ> VZ> This is one of the most frequently requested functions and I'd definitely VZ> like to have it one of these days but .... not yet. You may subscribe VZ> to/vote for the relevant bug (684) if you're interested. This was actually the very first function I intended to try to add once Python is working again. I'm coming along but I made the mistake of doing a cvs update which included Robert's current work so I have to wait till he gets finished putting it all back together again :-) >From my point of view, if I do a make -f Makefile.swig in the src/Python folder I now get a clean make and all the wrappers get generated so it will be interesting once I can do a complete compile to see if his current work has changed anything as the main makefile previously made cleanly for me IIRC. Maybe there was an advantage to you not getting around to integrating Makefile.swig into the main makefile LOL ;-D I've also give the Swig vs. Pyste issue some thought. ISTM that we should go for SWIG mainly for one good reason - If we do, it is a whole lot easier for someone to come along later and add support for scripting via one of the plethora of languages SWIG supports (Perl, Python, Tcl, Guile, Mzscheme, Java, Ruby, PHP, Ocaml, C# and CHICKEN). As I understand it, Pyste is a Python only solution. We also would not be having to waste the thousands of dollars it has not cost us implementing the current Python code valued highly according to Sloccount I posted earlier :-D LOL What is your / others opinion(s)? HTH Dr. QA ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ Mahogany-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-users
