A few recent threads have brought up crnl-glob, and in one, someone else pointed out that “CRNL” would be better as “CRLF”, and I agreed. I even typo’d “crlf-glob” in a more recent post.
But, after a trip to the source code, I now know that what this setting actually does it makes Fossil ignore any change involving CR in files, on the assumption that this is a text file, and might be using Mac or Windows line endings. (See line ~1500 in src/checkin.c. Notice that crnlOk only takes fHasAnyCr into account. Checks against fHasCrLfOnly happen *after* crnlOk pops you out of this function.) Given that, I wonder if it would be better called “cr-glob”? Obviously there is a legacy issue here. The option parser could silently continue to recognize crnl-glob, while only supporting the new name in external interactions. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
