Article View: gnu.emacs.vm.bug
Article #9165Re: vm 5.32 lossage with ^A^A^A^A format folders
From: Jamie Zawinski
Date: Mon, 09 Mar 1992 23:39
Date: Mon, 09 Mar 1992 23:39
48 lines
3225 bytes
3225 bytes
In message <9203092306.AA01860@wendy-fate.UU.NET> kyle@wendy-fate.uu.net wrote: > > From the perspective of trying to use any other mail tools on > your mail folders, I'd say BABYL isn't sane at all. If it don't run in emacs, it ain't of use to me. Of course, there are people who see things differently, and they should be able to continue to use From_ format. "Availability of tools" is a good argument for which mail format to use, but I was talking about which format is more rational. Here are some of the reasons I think that BABYL is better designed than From_ (to the extent that From_ was "designed" at all, that is): BABYL mail readers can reorder, reformat, and delete headers to their heart's content without destroying any information, because they can keep two copies of the headers, the original (untouched) one, and the one to show to the user. VM's current approach (which is the only efficient thing to do with From_ format) is to reorder the headers and only show the last few. This is lossy. If VM were to do header-reformatting (for instance, converting the Date field to be in the local timezone) this would be even more lossy, but BABYL could handle it easily. You don't have to mangle the message to quote lines beginning with "From ". If you want to add keywords or other annotations to a message, you don't have to alter the headers (again, your only alter your copy of them). These keywords are represented in the file in a well-defined, portable way, and canot be confused with a "Keywords:" field added by the original sender of the message. The various flag-bits that VM supports are already implicit in the file format, making the X-VM-Data header be a redundant efficiency hint, rather than a necessary piece of information (that is, another mail reader using BABYL format would know whether a message was "filed" without having to know about the format of X-VM-Data.) > I think MH is the sanest of all... one message per file, like Ghod intended. I think the multi-file approach is good, but there are pros and cons. You pay a bigger price for selecting messages, and a smaller price for selecting folders. Also, you can run into problems with inode allocation, thanks to that abortive hack that unix calls a file system. And I believe that the format MH uses within the individual messages still suffers the afforementioned problems that From_ does. -- Jamie
Technical Details
Message-ID:
<9203092339.AA07806@thalidomide.lucid>Path:
arc1-ca.pugleaf.net!sparky!uunet!wendy-fate.uu.net!bug-vmReferences:
<9203092235.AA04257@churchy.gnu.ai.mit.edu> <9203092237.AA28624@wendy-fate.UU.NET> <9203092247.AA07651@thalidomide.lucid> <9203092251.AA29857@wendy-fate.UU.NET> <9203092301.AA07757@thalidomide.lucid> <9203092306.AA01860@wendy-fate.UU.NET>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f6829,cfa18af4514eb905 X-Google-Attributes: gidf6829,public X-Google-ArrivalTime: 1992-03-09 15:43:22 PST Newsgroups: gnu.emacs.vm.bug Sender: bug-vm-request@uunet.uu.net Date: Mon, 9 Mar 92 15:39:35 PST Message-ID: <9203092339.AA07806@thalidomide.lucid> X-Windows: It could happen to you. From: Jamie Zawinski <jwz@lucid.com> Subject: Re: vm 5.32 lossage with ^A^A^A^A format folders References: <9203092235.AA04257@churchy.gnu.ai.mit.edu> <9203092237.AA28624@wendy-fate.UU.NET> <9203092247.AA07651@thalidomide.lucid> <9203092251.AA29857@wendy-fate.UU.NET> <9203092301.AA07757@thalidomide.lucid> <9203092306.AA01860@wendy-fate.UU.NET> Path: arc1-ca.pugleaf.net!sparky!uunet!wendy-fate.uu.net!bug-vm