Package: mutt
Version: 1.5.11+cvs20060126-2
Severity: normal
I'm preparing a new upstream release of saods9, and while waiting for
the compile to finish, I composed a message to submit a wishlist New
upstream release but, to which I attached the .diff.gz, my intent
being to ask -science for a sponsored upload. Then I put off the
project, for a couple weeks, since the executable didn't work, and I
ran out of time. When I came back, and wanted to resume work, I
started to pull the .diff.gz from the postponed message with the
'C'opy command. The default save filename was:
/tmp/saods9_4.0b7-1.1.diff.gz
which makes sense, since that it the filename that I initially
attached it as. The problem is that that file already exists, since
editting the postponed message message causes it to get written there
(with that name).
This makes little sense to me; if the default name is going to cause
overwriting of the file, then there shouldn't even be a default name.
This also causes this annoying prompt:
/tmp/saods9_4.0b7-1.1.diff.gz [#2] modified. Update encoding? ([yes]/no):
and actually ends up truncating the file:
-rw--- 1 pryzbyj pryzbyj 0 Mar 15 11:01 saods9_4.0b7-1.1.diff.gz
if I choose to overwrite (which is the default [!]).
Expected behavior would be for the default filename to be what it was
(the filename of the initial attach, perhaps with the full pathname),
but on editting the postponed message, that the attachment is saved
with a `tempfile`like name, which is unlikely to be overwritten.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
