Right now, if there are tests to be run at record, one can find out
that an omission of small one-line change in the current "record"
makes it invalid and thus rejected.

If there was a long commit comment supplied, it will be lost forever,
and one will have to type it from the very beginning. It would be nice
if commint comment would be preserved somewhere in the "." or in
$TMPDIR and could be reused.

> New submission from Dmitry Astapov <adept@umc.com.ua>:
>
> Right now, if there are tests to be run at record, one can find out
> that an omission of small one-line change in the current "record"
> makes it invalid and thus rejected.
>
> If there was a long commit comment supplied, it will be lost forever,
> and one will have to type it from the very beginning. It would be nice
> if commint comment would be preserved somewhere in the "." or in
> $TMPDIR and could be reused.

Dmitry,

If you look at recent messages on this mailing list, I posted a patch
named "save long comment file so it can be reused if record fails." 
It is going through a few iterations as I fix it up, but hopefully it
will be ready for inclusion soon.

fixed in 1.0.6
Fri Dec 16 03:39:48 CET 2005  Zachary P. Landau <kapheine@divineinvasion.net>
  * save long comment file if a test fails during record