On Sat, Mar 03, 2007 at 02:07:38AM +0100, Alain Bench wrote: : I'm sorry you lost data, but it's not a bug.
In the sense that one does not expect to lose data when one "SAVE"s a message, it's a bug and very much so. : > I am convinced that people who SAVE a mail want it to be complete and : > not to LOSE information. : : Of course, and then they use <save-message>. No, they want a decrypt and save, but not a decrypt then lose headers then save :-) *** I don't want to get into an argument; if the behaviour of decode-save has always been like that, it should remain, (and you're right from your POV), BUT: I think there is a substantial chance that people will want a decode-save that does not lose headers, and that they don't even read the docs if there is just one command that sounds like it. I know it's happened to me, and I've always been upset with the tendency of all >1000 packages in a modern Linux distro to think they are most important and to require the user to read all docs carefully. In fact, noone does. *** Jeremy Blosser pointed out that there might be need for a new command that does decrypt and save, but not decode (i.e. don't mime-decode, don't strip headers, etc.). A lot of people will want to encrypt in transport, but decrypt in storage (e.g. to use grep or some search software). So, please reconsider this as a feature request that would be really helpful. Either a command decrypt-save, or a flag save-decrypted would help remedy this situation. Best regards, Claus -- Claus Fischer <[EMAIL PROTECTED]> http://www.clausfischer.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
