Stephan Beal <[email protected]> wrote: > On Wed, Dec 9, 2009 at 6:39 PM, Jeremy Cowgar <[email protected]> wrote: > > > It seems that fossil is in need of two things: > > > > 1. Save the commit message to a file when the commit failed > > 2. Provide a means of making fossil read the commit message from a file > > > > If you're having to re-*type* your commit message, you're using the wrong > shell. All modern shells support up-arrow to scroll back through your > command history. If you're in the Bash shell, try tapping Ctrl-R, then tap > "-m" (the commit message argument), and the history will jump back to the > most recent command with "-m" in it. Then just tap enter. >
I tend to write lengthy (even formatting with the wiki syntax) commit messages. Thus, I usually type at the prompt: $ fossil commit Which triggers fossil into launching my prefered editor to edit the commit message. Thus, many times there is no history in the command shell to get the commit message back. It's gone forever. Jeremy _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
