From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Fri, 9 Aug 2002 04:35:16 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 297 ************************************************** Thursday 08 August 2002 Number 297 ************************************************** Subjects for today 1 Re: Mutt 1.4 : Patrick Ash **= Email 1 ==========================** Date: Fri, 09 Aug 2002 01:18:12 +0000 From: Patrick Ash Subject: Re: Mutt 1.4 On Thu, 08 Aug 2002 20:01:41 +0100, John Poltorak wrote: > >One of the OS/2 specific changes I find useful is the use of 20*^H >seperators in a mailbox sometimes referred to as MMDF formatted mailboxes. >I don't know where they originated but UUPC/2 and elm could handle them >and I have mailboxes going back many years in this format so it would be >handy to be able to read them. According to the manual.txt (found in /doc/mutt) this format is one of the formats that mutt supports. I do not beleive that it is a feature specific to the OS/2 version. From the manual Mutt supports reading and writing of four different mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to use a flag for different mailbox types. When creating new mailboxes, Mutt uses the default specified with the ``$mbox_type'' variable. > >I can't seem t read any msgs, I get an error saying:- > >Could not create temporary file! > >when I select a msg from the index. I do have %TMP% defined and there is >plenty of free space, so I don't know why I get this error. > >This mutt uses a hard code mailpath of c:/mptn/etc/mail which doesn't >exist here. %ETC% is defined as c:\etc and mailboxes are in c:\var\mail. > I built another version with the mailpath variable set to /var/mail. The configure script will not complete if this variable is empty, so it has to be set to something. Perhaps it can be changed in .muttrc. I am not sure what is the cause of the error creating temporary files. There are 4-5 different modules where this could occur, and I will have to look at the code in each to see what is the cause. This might take a day or 2. Hopefully less, but one never knows. Pat -- Patrick Ash patash at comcast.net This OS/2 system uptime is 7 days, 16:02 hours and 30 seconds