427
428
429
430
431
432
433
434
435
436
437
438
439
440
|
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
|
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
|
matching any files, unless you happen to have files named with a
trailing comma in the current directory. If the pattern matches no
files, it is passed into Fossil's `main()` function as-is by the C
runtime system. Since Fossil uses commas to separate multiple glob
patterns, this means "all files at the root of the Fossil checkout
directory and nothing else."
## Experimenting
To preview the effects of command line glob pattern expansion for
various glob patterns (unquoted, quoted, comma-terminated), for any
combination of command shell and Fossil executable, on both POSIX
systems and Windows, the [`test-echo`][] command can be injected as
the first argument on the Fossil command line:
$ fossil test-echo setting crlf-glob "*"
$ echo * | fossil test-echo setting crlf-glob --args -
Moreover, the [`test-glob`][] command is handy to test if a string
matches a glob pattern.
[`test-echo`]: /help?cmd=test-echo
[`test-glob`]: /help?cmd=test-glob
## Converting `.gitignore` to `ignore-glob`
Many other version control systems handle the specific case of
ignoring certain files differently from fossil: they have you create
individual "ignore" files in each folder, which specify things ignored
in that folder and below. Usually some form of glob patterns are used
|