Stephan Beal wrote: > --===============1015663013== > Content-Type: multipart/alternative; boundary=f46d04388df3ee3c0605027d793b > > --f46d04388df3ee3c0605027d793b > Content-Type: text/plain; charset=UTF-8 > > On Sun, Sep 7, 2014 at 7:55 PM, Ron W <ronw.m...@gmail.com> wrote: > >> It's still only a 1 line "window" - unless you know a trick I don't >> >> (I (and my team) try to write several lines even though we do rely on >> citing issues.) >> > > i just keep on typing... > > http://fossil.wanderinghorse.net/repos/cwal/index.cgi/info/ce97684b46927bae3090ac06b7ac09340f51005f > http://fossil.wanderinghorse.net/repos/cwal/index.cgi/info/1648e371e7db611c46b0a12c4fab7bec7ca42a84 > http://fossil.wanderinghorse.net/repos/cwal/index.cgi/info/af8b1fba5a5904b5b43feef5665ee71bbfbe513c > > i've never felt compelled to format commit messages to some > "management-friendly" form.
I have to admit that I *hate* to mistype a commit message and have it frozen for all time. Using an editor just seems so much easier... > It takes me less time to type such a message from the CLI than it does to > either (A) wait on emacs (my preferred editor) to start up or (B) fight > with vi in doing the little things my fingers do intuitively in emacs. I use Emacs too, and I don't have any problem with startup time. (Maybe I have a lighter ~/.emacs ?) -- Will _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
