Stephan Beal <[email protected]> wrote: > > 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()). >
Hm, I just relized how your EDITOR="" example works. That will not work with Fossil, as the way the EDITOR= variable works is: $ export EDITOR=nano $ fossil commit --- Here fossil see's that no message has been supplied on the command line so it generates a unique filename and then writes something like: # All text below this line will be ignored. # ADDED abc.xyz # DELETED def.123 # MODIFIED john.doe It then does a system call something like: nano unique-filename.txt You are then presented with the editor editing unique-filename.txt. You add your comment, quit the editor (saving of course) and fossil continues. If fossil sees that you have not added any content to the file (i.e. didn't save it), then it will say "Empty commit message, continue? [yN]". So, fossil already writes/reads from a commit message, it just doesn't expose the functionality to the user. Jeremy _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
