From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/18590 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: MIME composition (was: Storing the group a message has been written to) Date: 14 Nov 1998 02:09:21 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035157088 6987 80.91.224.250 (20 Oct 2002 23:38:08 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:38:08 +0000 (UTC) Return-Path: Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id UAA03109 for ; Fri, 13 Nov 1998 20:10:30 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by karazm.math.uh.edu (8.9.1/8.9.1) with ESMTP id TAB12795; Fri, 13 Nov 1998 19:09:43 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 13 Nov 1998 19:09:38 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [209.195.19.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id TAA07598 for ; Fri, 13 Nov 1998 19:09:29 -0600 (CST) Original-Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id UAA03079 for ; Fri, 13 Nov 1998 20:09:23 -0500 (EST) Original-Received: (from hniksic@localhost) by jagor.srce.hr (8.9.0/8.9.0) id CAA09293; Sat, 14 Nov 1998 02:09:21 +0100 (MET) Original-To: ding@gnus.org X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h writes: > Kai.Grossjohann@CS.Uni-Dortmund.DE writes: > > > Suggestion: use a convenient in-buffer representation, and use the > > `correct' MIME representation on disk. Use format-alist to convert > > between the two upon disk i/o. > > That would probably be rather slow when autosaving, I think. Not if you do it right. For example, image attachments needn't be actually base64'ed -- you can simply add `X-Gnus-Something' header that names the file name of the image, etc. > And there's not much to be gained, I think. You gain the goals you set: * nndrafts and autosaving is (more or less) guaranteed to work correctly; * everything is within a single buffer/file; * you are not inventing an all-new all-weird format for storing stuff. > > By `inline' and `attachment' I don't mean content-disposition, I'm > > referring to the looks of the message composition buffer. > > `Inline' parts are shown inline while one is editing the messages, > > and `attachment' parts are represented by a button. For Emacs, > > only textual parts will be inline, but for XEmacs, images can be > > inline, too, right? > > Yes, but I don't think displaying images inline when composing makes > much sense. Agreed. VM doesn't do that, either. -- Hrvoje Niksic | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Speak softly and carry a +6 two-handed sword.