Hello, I have a few comments (and not realy much more than that) on the way Fossil implements the editing of commit messages:
- I noticed that the choice of editor seems to be a global setting in the repository. At least, that is the behaviour I observe with one repository (but that may be peculiar to that particular project). As editors are a highly personal choice, I would expect this to be a user-defined setting. - I noticed that when I compile Fossil for MinGW, the default editor is not notepad in the absence of EDITOR etc. environment variables, but a command-line interface. I think notepad, whatever you think of it, would be a more natural choice. - As I mostly work on Windows, my editor is set to write CR/LF line-endings. If I commit files that I forgot to save with LF line-endings, I get a question about this - but only for the first file. If I then break off the commit, repair this and try again, a message follows about the next file. Would it be possible to simply scan all the files to be committed and present a list of files that have a CR/LF issue, so that you can repair all of them at once? Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
