On Wed, Dec 9, 2009 at 8:58 PM, Jeremy Cowgar <[email protected]> wrote:
> 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. > > Theoretically (i haven't tried it) you could use a workaround like this: a) Put your commit in a file, e.g. msg.txt. b) type: EDITOR="cat msg.txt" fossil commit foo.c whether or not that works depends largely on how the EDITOR arg is passed on to the system (as a single arg via execvp() and friends or as part of a concated string passed to system()). -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
