| commit | c29d57e2b33c71391713f6495c88bca9f47a0136 | |
| author | Steffen "Daode" Nurpmeso <sdaoden@users.sf.net> | |
| Sat, 6 Oct 2012 17:05:06 +0000 (6 19:05 +0200) | ||
| committer | Steffen "Daode" Nurpmeso <sdaoden@users.sf.net> | |
| Sat, 6 Oct 2012 17:05:29 +0000 (6 19:05 +0200) | ||
| tree | 24f0c460d072eff47ad01e7c56a8d346b149370d | treesnapshot (tar.gz zip) |
| parent | c5c3e9b21a5d06c05bf18f591bd0bccbcb155d24 | commitdiff |
*writebackedited* hack..
Sofar if the final newlines of an edited message has been
stripped away the resulting MBOX file was broken, because
the required separating newline was not automatically added
again, i.e., that was part of the edit action!
So do a 15 minutes quick and dirty hack to ensure that the
resulting MBOX is a valid one.
THIS MAY NOT BE CORRECT in that noone knows what may be the
target, and the better approach would be to only pass through
to the user what really can be edited, but due to the way
the code works this is not that easy.
It seems to work for normal MBOX input and normal MBOX output.
NetBSD mailx(1) suffers from the same bug.
Sofar if the final newlines of an edited message has been
stripped away the resulting MBOX file was broken, because
the required separating newline was not automatically added
again, i.e., that was part of the edit action!
So do a 15 minutes quick and dirty hack to ensure that the
resulting MBOX is a valid one.
THIS MAY NOT BE CORRECT in that noone knows what may be the
target, and the better approach would be to only pass through
to the user what really can be edited, but due to the way
the code works this is not that easy.
It seems to work for normal MBOX input and normal MBOX output.
NetBSD mailx(1) suffers from the same bug.
| edit.c | diffblobblamehistory |