Fossil SCM

*, which is the value for most of my projects, is not accepted as a parameter for crnl-glob on command line. It has to be set through the browser. As ui/server command do not work too well when a vpn is installed, I need to set the settings from command line only, which is not possible.

Command: fossil settings crnl-glob * Here is the output: d:\tools\fossil.exe: Usage: d:\tools\fossil.exe settings ?PROPERTY? ?VALUE?

anonymous claiming to be Martin added on 2011-06-15 05:29:02 UTC: You might want to read this thread from mailing list:

[http://www.mail-archive.com/[email protected]/msg04322.html]

anonymous added on 2011-06-15 08:12:51 UTC: Ah, My apologies. I should have searched the mailing list first. So, this is a MinGW error instead. The problem is, on a specific system, the ui command fails. And I can't set the settings with command line also. So, as of now, I have no way of setting the value to *.

stephan added on 2011-09-14 18:16:18 UTC: This is not a bug: the problem is that your SHELL is resolving '*' before fossil ever gets it. You have to escape * by wrapping it in quotes.

mistachkin added on 2011-09-14 18:52:30 UTC: This may still be an issue on Win32, where a naked * is not actually interpreted by the shell (yet should be accepted by Fossil as valid).

stephan added on 2011-09-15 09:08:23 UTC: i got an email from the poster, who reports:

I don't know exactly what changed, but in version 1.18 or 1.19, the commands:
fossil setting crnl-glob *
fossil setting crnl-glob "*"
work perfectly.

... (weird - fossil is prematurely ending my PRE block...)

And BTW, previously neither single quotes or double quotes
worked to set the value to *. Single quotes were taken in
the value and double quotes gave the same error which I
mentioned in the thread.

Changing status from not-a-bug to fixed.

@Yogesh - if this comes back, please let us.