On Thu, 7 Apr 2011 10:04:22 -0400 Richard Hipp <d...@sqlite.org> wrote:
> On Thu, Apr 7, 2011 at 9:37 AM, Wilson, Ronald <rwils...@harris.com> > wrote: > > > crnl-glob A comma-separated list of GLOB patterns for > > text files > > > > in which it is ok to have CR+NL line endings. > > > > Set to "*" to disable CR+NL checking. > > > > > > > > I’m unable to set crnl-glob to * in windows, per the > > documentation. I’m using powershell in windows 7 and I’ve also > > tried the regular windows command shell. I even tried *.* just for > > grins. > > > > Apparently, there is no way in the DOS shell to pass * in as a > parameter to a program. I think you're wrong. To demonstrate (Windows XP, cmd.exe): C:\>fossil set crnl-glob "" C:\>fossil settings|grep crnl crnl-glob (local) C:\>fossil set crnl-glob "*" C:\>fossil settings|grep crnl crnl-glob (local) * [...] In fact, cmd.exe has the opposite problem: while on Unix it expands bare * in certain places, trying to replace it with a matching list of files, on Windows the shell passes the asterisk to the program it calls "as is" and the program is then supposed to do whatever it wants with that asterisk. I mean that in a POSIX shell, if we have $ ls aaa bbb ccc then $ rm * will result in the call "rm aaa bbb ccc", while on Windows it will result in the call "rm *". On the other hand, the original poster seems to be using PowerShell, not cmd.exe; I'm personally not familiar with it (our shop is still using Windows XP/Windows 2003 on which PowerShell is painfully slow to the level of being unusable) and it might well have different semantics. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
