Fossil SCM
Hoist the list of POSIX subsystem features for Windows up to the top of the "Windows" section in globs.md to wave readers off to the "POSIX" section of the same doc before we get into truly Windows-specific details.
Commit
21929d37a36bce7b06bc6e6036024172a9ead73fb3fb0f19abef4a93d942ad60
Parent
50a8e53640903d4…
1 file changed
+20
-12
+20
-12
| --- www/globs.md | ||
| +++ www/globs.md | ||
| @@ -261,11 +261,11 @@ | ||
| 261 | 261 | That advice does not help you when you are giving one-off glob patterns |
| 262 | 262 | in `fossil` commands. The remainder of this section gives remedies and |
| 263 | 263 | workarounds for these problems. |
| 264 | 264 | |
| 265 | 265 | |
| 266 | -## POSIX Systems | |
| 266 | +### <a name="posix"></a>POSIX Systems | |
| 267 | 267 | |
| 268 | 268 | If you are using Fossil on a system with a POSIX-compatible shell |
| 269 | 269 | — Linux, macOS, the BSDs, Unix, Cygwin, WSL etc. — the shell |
| 270 | 270 | may expand the glob patterns before passing the result to the `fossil` |
| 271 | 271 | executable. |
| @@ -348,11 +348,28 @@ | ||
| 348 | 348 | accidentally check something like a password, an API key, or the |
| 349 | 349 | private half of a public cryptographic key into Fossil repository that |
| 350 | 350 | can be read by people who should not have such secrets. |
| 351 | 351 | |
| 352 | 352 | |
| 353 | -## Windows | |
| 353 | +### <a name="windows"></a>Windows | |
| 354 | + | |
| 355 | +Before we get into Windows-specific details here, beware that this | |
| 356 | +section does not apply to the several Microsoft Windows extensions that | |
| 357 | +provide POSIX semantics to Windows, for which you want to use the advice | |
| 358 | +in [the POSIX section above](#posix) instead: | |
| 359 | + | |
| 360 | + * the ancient and rarely-used [Microsoft POSIX subsystem][mps]; | |
| 361 | + * its now-discontinued replacement feature, [Services for Unix][sfu]; or | |
| 362 | + * their modern replacement, the [Windows Subsystem for Linux][wsl] | |
| 363 | + | |
| 364 | +[mps]: https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem | |
| 365 | +[sfu]: https://en.wikipedia.org/wiki/Windows_Services_for_UNIX | |
| 366 | +[wsl]: https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux | |
| 367 | + | |
| 368 | +(The latter is sometimes incorrectly called "Bash on Windows" or "Ubuntu | |
| 369 | +on Windows," but the feature provides much more than just Bash or Ubuntu | |
| 370 | +for Windows.) | |
| 354 | 371 | |
| 355 | 372 | Neither standard Windows command shell — `cmd.exe` or PowerShell |
| 356 | 373 | — expands glob patterns the way POSIX shells do. Windows command |
| 357 | 374 | shells rely on the command itself to do the glob pattern expansion. The |
| 358 | 375 | way this works depends on several factors: |
| @@ -374,23 +391,14 @@ | ||
| 374 | 391 | applies in a way that affects how Fossil interprets the glob pattern. |
| 375 | 392 | |
| 376 | 393 | The most common problem is figuring out how to get a glob pattern passed |
| 377 | 394 | on the command line into `fossil.exe` without it being expanded by the C |
| 378 | 395 | runtime library that your particular Fossil executable is linked to, |
| 379 | -which tries to act like the POSIX systems described above. Windows is | |
| 396 | +which tries to act like [the POSIX systems described above](#posix). Windows is | |
| 380 | 397 | not strongly governed by POSIX, so it has not historically hewed closely |
| 381 | 398 | to its strictures. |
| 382 | 399 | |
| 383 | -(This section does not cover the [Microsoft POSIX | |
| 384 | -subsystem](https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem), | |
| 385 | -Windows' obsolete [Services for Unix | |
| 386 | -3.*x*](https://en.wikipedia.org/wiki/Windows_Services_for_UNIX) feature, | |
| 387 | -or the [Windows Subsystem for | |
| 388 | -Linux](https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux). (The | |
| 389 | -latter is sometimes incorrectly called "Bash on Windows" or "Ubuntu on | |
| 390 | -Windows.") See the POSIX Systems section above for those cases.) | |
| 391 | - | |
| 392 | 400 | For example, consider how you would set `crlf-glob` to `*` in order to |
| 393 | 401 | disable Fossil's "looks like a binary file" checks. The naïve |
| 394 | 402 | approach will not work: |
| 395 | 403 | |
| 396 | 404 | C:\...> fossil setting crlf-glob * |
| 397 | 405 |
| --- www/globs.md | |
| +++ www/globs.md | |
| @@ -261,11 +261,11 @@ | |
| 261 | That advice does not help you when you are giving one-off glob patterns |
| 262 | in `fossil` commands. The remainder of this section gives remedies and |
| 263 | workarounds for these problems. |
| 264 | |
| 265 | |
| 266 | ## POSIX Systems |
| 267 | |
| 268 | If you are using Fossil on a system with a POSIX-compatible shell |
| 269 | — Linux, macOS, the BSDs, Unix, Cygwin, WSL etc. — the shell |
| 270 | may expand the glob patterns before passing the result to the `fossil` |
| 271 | executable. |
| @@ -348,11 +348,28 @@ | |
| 348 | accidentally check something like a password, an API key, or the |
| 349 | private half of a public cryptographic key into Fossil repository that |
| 350 | can be read by people who should not have such secrets. |
| 351 | |
| 352 | |
| 353 | ## Windows |
| 354 | |
| 355 | Neither standard Windows command shell — `cmd.exe` or PowerShell |
| 356 | — expands glob patterns the way POSIX shells do. Windows command |
| 357 | shells rely on the command itself to do the glob pattern expansion. The |
| 358 | way this works depends on several factors: |
| @@ -374,23 +391,14 @@ | |
| 374 | applies in a way that affects how Fossil interprets the glob pattern. |
| 375 | |
| 376 | The most common problem is figuring out how to get a glob pattern passed |
| 377 | on the command line into `fossil.exe` without it being expanded by the C |
| 378 | runtime library that your particular Fossil executable is linked to, |
| 379 | which tries to act like the POSIX systems described above. Windows is |
| 380 | not strongly governed by POSIX, so it has not historically hewed closely |
| 381 | to its strictures. |
| 382 | |
| 383 | (This section does not cover the [Microsoft POSIX |
| 384 | subsystem](https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem), |
| 385 | Windows' obsolete [Services for Unix |
| 386 | 3.*x*](https://en.wikipedia.org/wiki/Windows_Services_for_UNIX) feature, |
| 387 | or the [Windows Subsystem for |
| 388 | Linux](https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux). (The |
| 389 | latter is sometimes incorrectly called "Bash on Windows" or "Ubuntu on |
| 390 | Windows.") See the POSIX Systems section above for those cases.) |
| 391 | |
| 392 | For example, consider how you would set `crlf-glob` to `*` in order to |
| 393 | disable Fossil's "looks like a binary file" checks. The naïve |
| 394 | approach will not work: |
| 395 | |
| 396 | C:\...> fossil setting crlf-glob * |
| 397 |
| --- www/globs.md | |
| +++ www/globs.md | |
| @@ -261,11 +261,11 @@ | |
| 261 | That advice does not help you when you are giving one-off glob patterns |
| 262 | in `fossil` commands. The remainder of this section gives remedies and |
| 263 | workarounds for these problems. |
| 264 | |
| 265 | |
| 266 | ### <a name="posix"></a>POSIX Systems |
| 267 | |
| 268 | If you are using Fossil on a system with a POSIX-compatible shell |
| 269 | — Linux, macOS, the BSDs, Unix, Cygwin, WSL etc. — the shell |
| 270 | may expand the glob patterns before passing the result to the `fossil` |
| 271 | executable. |
| @@ -348,11 +348,28 @@ | |
| 348 | accidentally check something like a password, an API key, or the |
| 349 | private half of a public cryptographic key into Fossil repository that |
| 350 | can be read by people who should not have such secrets. |
| 351 | |
| 352 | |
| 353 | ### <a name="windows"></a>Windows |
| 354 | |
| 355 | Before we get into Windows-specific details here, beware that this |
| 356 | section does not apply to the several Microsoft Windows extensions that |
| 357 | provide POSIX semantics to Windows, for which you want to use the advice |
| 358 | in [the POSIX section above](#posix) instead: |
| 359 | |
| 360 | * the ancient and rarely-used [Microsoft POSIX subsystem][mps]; |
| 361 | * its now-discontinued replacement feature, [Services for Unix][sfu]; or |
| 362 | * their modern replacement, the [Windows Subsystem for Linux][wsl] |
| 363 | |
| 364 | [mps]: https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem |
| 365 | [sfu]: https://en.wikipedia.org/wiki/Windows_Services_for_UNIX |
| 366 | [wsl]: https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux |
| 367 | |
| 368 | (The latter is sometimes incorrectly called "Bash on Windows" or "Ubuntu |
| 369 | on Windows," but the feature provides much more than just Bash or Ubuntu |
| 370 | for Windows.) |
| 371 | |
| 372 | Neither standard Windows command shell — `cmd.exe` or PowerShell |
| 373 | — expands glob patterns the way POSIX shells do. Windows command |
| 374 | shells rely on the command itself to do the glob pattern expansion. The |
| 375 | way this works depends on several factors: |
| @@ -374,23 +391,14 @@ | |
| 391 | applies in a way that affects how Fossil interprets the glob pattern. |
| 392 | |
| 393 | The most common problem is figuring out how to get a glob pattern passed |
| 394 | on the command line into `fossil.exe` without it being expanded by the C |
| 395 | runtime library that your particular Fossil executable is linked to, |
| 396 | which tries to act like [the POSIX systems described above](#posix). Windows is |
| 397 | not strongly governed by POSIX, so it has not historically hewed closely |
| 398 | to its strictures. |
| 399 | |
| 400 | For example, consider how you would set `crlf-glob` to `*` in order to |
| 401 | disable Fossil's "looks like a binary file" checks. The naïve |
| 402 | approach will not work: |
| 403 | |
| 404 | C:\...> fossil setting crlf-glob * |
| 405 |