Re: [fossil-users] Fossil cannot add filenames with \*[]?
On Mon, 4 Apr 2011 19:37:07 -0400 Ron Wilson ronw.m...@gmail.com wrote: Fossil failed on filenames containing brackets - []. Huh? Browsing the mail shows this to be a known issue. Browsing the responses came up short. Any glaring reason(s) for not allowing certain wildcards in filenames? Especially when competing SCM's are already past this... In some development environments, these characters are not a problem. Only the characters used by the file system, such as / in Unix/Linux and \ and : in Windows, are not allowed in file names. However, in environments that, directly or indirectly, use command line processing, such as shell scripts, .BAT scripts and even make files, these characters are often used for other purposes and will cause problems if not properly quoted and/or escaped. That typically adds ', and \ to the list of problem characters. Also, ; is often used as a command delimiter, and the space and tab characters are often used as parameter delimiters. [...] All that said, however, it would make sense to make the prohibition of these characters a configurable setting. There are plenty of new developpers who have never had to worry about these restrictions, so will likely choose an SCM that either lacks these restrictions or can be configured to disable them. I concur. There is a huge difference between having the need to tweak something to get the desired functionality and complete inability to get it (commenting out some source code would be a solution only in a tiny fraction of possible cases, I reckon). So, a user-configurable setting to switch off banning of this additional set of characters in filenames would be just OK I think. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] sqlite.org skin
Published? If you clone the fossil repository and then do fossil config export skin sqlite-skin.txt -R sqlite.fossil you'll have the complete skin-spec in the file sqlite-skin.txt. You can then import it into whatever you want using fossil config import sqlite-skin.txt -R myrepo.fossil. My mistake; I was looking for the gradient, rounded corners skin and I think it wasn't working for me because I hadn't done a fossil rebuild. RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications(tm) inline: image002.png___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
On Apr 4, 2011, at 22:55 , Stephan Beal wrote: On a related note: some tools (like cvs or svn) warn if a file's last line has no end-of-line marker. That's because (as i was taught, anyway) the official definition of a text file is basically variable-length records separated by a record separator (an end-of-line sequence (\n on *nix, \r\n on Windows)), and that the last record must also have such a separator. Actually, this way the definition says that the last line can not have a \n. You probably wanted to write ended by a record separator, but then the word separator is misleading ;) Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
On Tue, Apr 5, 2011 at 3:49 PM, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: On Apr 4, 2011, at 22:55 , Stephan Beal wrote: On a related note: some tools (like cvs or svn) warn if a file's last line has no end-of-line marker. That's because (as i was taught, anyway) the official definition of a text file is basically variable-length records separated by a record separator (an end-of-line sequence (\n on *nix, \r\n on Windows)), and that the last record must also have such a separator. Actually, this way the definition says that the last line can not have a \n. You probably wanted to write ended by a record separator, but then the word separator is misleading ;) I recall it being defined as variable length records, each ending with a record terminator, which was, because of the way teletype machine worked, CR-LF. (Though, with the real machine, LF-CR had the same end result.) Interestingly, Microsoft choose control-Z as end-of-file, rather than any of the other defined control values that might have been better. My guess is that that was because Z is the last letter of the alphabet, and Z being closest to the lower left corner of the keyboard. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
Sometime on 4/5/2011, Ron Wilson wrote: Interestingly, Microsoft choose control-Z as end-of-file, rather than any of the other defined control values that might have been better. My guess is that that was because Z is the last letter of the alphabet, and Z being closest to the lower left corner of the keyboard. For some reason, that sets off an urge to reminisce about old computers... Ctrl+Z was used as an end of file mark in CP/M-80, and DOS 1.0 had a lot of CP/M heritage and inspiration. That is where drive letters and 8.3 file names come from, for instance. Ctrl+Z (or some marker, at least) was needed because the CP/M file system stored files in whole disk blocks, and had no other way of marking the end of a file to single-byte accuracy. CP/M wasn't alone in this choice. Digital's RT-11 also stored files in whole block increments and used Ctrl+Z as EOF. IIRC, very early versions of DOS followed the same conventions, and many old utilities would pad files out to block boundaries or at least insert a Ctrl+Z after the last byte written. To this day, files opened in Text on Windows will report EOF at the first Ctrl+Z encountered, although all versions of the FAT file system and its descendents know the file size in bytes. As a further bit of trivia, PNG files include a Ctrl+Z in their header to explicitly catch the case that the file was opened with text-mode translations enabled. In that case, the file will appear to end after six bytes are read. The header is: 0x89 0x50 0x4E 0x47 0x0d 0x0a 0x1a 0x0a. This sequence catches a bunch of incorrect ways to process the file including 7-bit only transmission, CRLF to NL, NL to CRLF, Ctrl+Z as EOF, and byte order. And if you use TYPE at the command prompt to display a PNG file, it will show the string PNG before stopping. Incidentally, the use of Ctrl+D in Unix derivatives is a property of the tty driver and it does not get translated as EOF when read from files at all. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
I believe Ctrl-Z is defined as EOF in ASCII which predates Microsoft. Terminating text files with EOF was the solution employeed by CP/M because file sizes were a sector count instead of a byte count. On Apr 5, 2011 3:06 PM, Ron Wilson ronw.m...@gmail.com wrote: On Tue, Apr 5, 2011 at 3:49 PM, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: On Apr 4, 2011, at 22:55 , Stephan Beal wrote: On a related note: some tools (like cvs or svn) warn if a file's last line has no end-of-line marker. That's because (as i was taught, anyway) the official definition of a text file is basically variable-length records separated by a record separator (an end-of-line sequence (\n on *nix, \r\n on Windows)), and that the last record must also have such a separator. Actually, this way the definition says that the last line can not have a \n. You probably wanted to write ended by a record separator, but then the word separator is misleading ;) I recall it being defined as variable length records, each ending with a record terminator, which was, because of the way teletype machine worked, CR-LF. (Though, with the real machine, LF-CR had the same end result.) Interestingly, Microsoft choose control-Z as end-of-file, rather than any of the other defined control values that might have been better. My guess is that that was because Z is the last letter of the alphabet, and Z being closest to the lower left corner of the keyboard. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
At 06:37 PM 4/5/2011, Scott Robinson wrote: I believe Ctrl-Z is defined as EOF in ASCII... In ASCII, Ctrl+Z is SUB, intended to substitute for a damaged character read from tape or received in a channel. ASCII did not define a specific end of file code. The closest are Ctrl+C aka ETX for End of Transmission, and Ctrl+D aka EOT for End of Text. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit question
Ah, thank you. I am on the road with barely enough bandwidth to email. At least I was smart enough to give myself an out with I believe instead of stating it as solid fact. :) SDR On Apr 5, 2011 6:48 PM, Ross Berteig r...@cheshireeng.com wrote: At 06:37 PM 4/5/2011, Scott Robinson wrote: I believe Ctrl-Z is defined as EOF in ASCII... In ASCII, Ctrl+Z is SUB, intended to substitute for a damaged character read from tape or received in a channel. ASCII did not define a specific end of file code. The closest are Ctrl+C aka ETX for End of Transmission, and Ctrl+D aka EOT for End of Text. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
