Fossil SCM
Wrap over-length lines in the www/settings.wiki documentation page.
Commit
abe1030ca8b01c8bb41baa0540a25ce01d194c3c
Parent
d7afa8f15342d18…
1 file changed
+47
-17
+47
-17
| --- www/settings.wiki | ||
| +++ www/settings.wiki | ||
| @@ -1,31 +1,61 @@ | ||
| 1 | 1 | <title>Fossil Settings</title> |
| 2 | 2 | |
| 3 | 3 | <h2>Using Fossil Settings</h2> |
| 4 | 4 | |
| 5 | -Settings control the behaviour of fossil. They are set with the <tt>fossil settings</tt> command, or through the web interface in the Settings page in the Admin section. | |
| 5 | +Settings control the behaviour of fossil. They are set with the | |
| 6 | +<tt>fossil settings</tt> command, or through the web interface in | |
| 7 | +the Settings page in the Admin section. | |
| 6 | 8 | |
| 7 | -For a list of all settings, view the Settings page, or type <tt>fossil help settings</tt> from the command line. | |
| 9 | +For a list of all settings, view the Settings page, or type | |
| 10 | +<tt>fossil help settings</tt> from the command line. | |
| 8 | 11 | |
| 9 | 12 | |
| 10 | 13 | <h3>Repository settings</h3> |
| 11 | 14 | |
| 12 | -Settings are set on a per-repository basis. When you clone a repository, a subset of settings are copied to your local repository. | |
| 15 | +Settings are set on a per-repository basis. When you clone a repository, | |
| 16 | +a subset of settings are copied to your local repository. | |
| 13 | 17 | |
| 14 | -If you make a change to a setting on your local repository, it is not synced back to the server when you <tt>push</tt> or <tt>sync</tt>. If you make a change on the server, you need to manually make the change on all repositories which are cloned from this repository. | |
| 18 | +If you make a change to a setting on your local repository, it is not | |
| 19 | +synced back to the server when you <tt>push</tt> or <tt>sync</tt>. If | |
| 20 | +you make a change on the server, you need to manually make the change on | |
| 21 | +all repositories which are cloned from this repository. | |
| 15 | 22 | |
| 16 | -You can also set a setting globally on your local machine. The value will be used for all repositories cloned to your machine, unless overridden explicitly in a particular repository. Global settings can be set by using the <tt>-global</tt> option on the <tt>fossil settings</tt> command. | |
| 17 | - | |
| 23 | +You can also set a setting globally on your local machine. The value | |
| 24 | +will be used for all repositories cloned to your machine, unless | |
| 25 | +overridden explicitly in a particular repository. Global settings can be | |
| 26 | +set by using the <tt>-global</tt> option on the <tt>fossil settings</tt> | |
| 27 | +command. | |
| 18 | 28 | |
| 19 | 29 | <h3>"Versionable" settings</h3> |
| 20 | 30 | |
| 21 | -Most of the settings control the behaviour of fossil on your local machine, largely acting to reflect your preference on how you want to use Fossil, how you communicate with the server, or options for hosting a repository on the web. | |
| 22 | - | |
| 23 | -However, for historical reasons, some settings affect how you work with versioned files. These are <tt>allow-symlinks</tt>, <tt>binary-glob</tt>, <tt>crnl-glob</tt>, <tt>empty-dirs</tt>, <tt>encoding-glob</tt>, <tt>ignore-glob</tt>, <tt>keep-glob</tt> and <tt>manifest</tt>. The most important is <tt>ignore-glob</tt> which specifies which files should be ignored when looking for unmanaged files with the <tt>extras</tt> command. | |
| 24 | - | |
| 25 | -Because these options can change over time, and the inconvenience of replicating changes, these settings are "versionable". As well as being able to be set using the <tt>settings</tt> command or the web interface, you can created versioned files in the <tt>.fossil-settings</tt> directory named with the setting name. The contents of the file is the value of the setting, and these files are checked in, committed, merged, and so on, as with any other file. | |
| 26 | - | |
| 27 | -Where a setting is a list of values, such as <tt>ignore-glob</tt>, you can use a newline as a separator as well as a comma. | |
| 28 | - | |
| 29 | -For example, to set the list of ignored files, create a <tt>.fossil-settings/ignore-glob</tt> file where each line contains a glob for ignored files. | |
| 30 | - | |
| 31 | -If you set the value of a setting using the <tt>settings</tt> command as well as a versioned file, the versioned setting will take precedence. A warning will be displayed. | |
| 31 | +Most of the settings control the behaviour of fossil on your local | |
| 32 | +machine, largely acting to reflect your preference on how you want to | |
| 33 | +use Fossil, how you communicate with the server, or options for hosting | |
| 34 | +a repository on the web. | |
| 35 | + | |
| 36 | +However, for historical reasons, some settings affect how you work with | |
| 37 | +versioned files. These are <tt>allow-symlinks</tt>, | |
| 38 | +<tt>binary-glob</tt>, <tt>crnl-glob</tt>, <tt>empty-dirs</tt>, | |
| 39 | +<tt>encoding-glob</tt>, <tt>ignore-glob</tt>, <tt>keep-glob</tt> and | |
| 40 | +<tt>manifest</tt>. The most important is <tt>ignore-glob</tt> which | |
| 41 | +specifies which files should be ignored when looking for unmanaged files | |
| 42 | +with the <tt>extras</tt> command. | |
| 43 | + | |
| 44 | +Because these options can change over time, and the inconvenience of | |
| 45 | +replicating changes, these settings are "versionable". As well as being | |
| 46 | +able to be set using the <tt>settings</tt> command or the web interface, | |
| 47 | +you can created versioned files in the <tt>.fossil-settings</tt> | |
| 48 | +directory named with the setting name. The contents of the file is the | |
| 49 | +value of the setting, and these files are checked in, committed, merged, | |
| 50 | +and so on, as with any other file. | |
| 51 | + | |
| 52 | +Where a setting is a list of values, such as <tt>ignore-glob</tt>, you | |
| 53 | +can use a newline as a separator as well as a comma. | |
| 54 | + | |
| 55 | +For example, to set the list of ignored files, create a | |
| 56 | +<tt>.fossil-settings/ignore-glob</tt> file where each line contains a | |
| 57 | +glob for ignored files. | |
| 58 | + | |
| 59 | +If you set the value of a setting using the <tt>settings</tt> command as | |
| 60 | +well as a versioned file, the versioned setting will take precedence. A | |
| 61 | +warning will be displayed. | |
| 32 | 62 |
| --- www/settings.wiki | |
| +++ www/settings.wiki | |
| @@ -1,31 +1,61 @@ | |
| 1 | <title>Fossil Settings</title> |
| 2 | |
| 3 | <h2>Using Fossil Settings</h2> |
| 4 | |
| 5 | Settings control the behaviour of fossil. They are set with the <tt>fossil settings</tt> command, or through the web interface in the Settings page in the Admin section. |
| 6 | |
| 7 | For a list of all settings, view the Settings page, or type <tt>fossil help settings</tt> from the command line. |
| 8 | |
| 9 | |
| 10 | <h3>Repository settings</h3> |
| 11 | |
| 12 | Settings are set on a per-repository basis. When you clone a repository, a subset of settings are copied to your local repository. |
| 13 | |
| 14 | If you make a change to a setting on your local repository, it is not synced back to the server when you <tt>push</tt> or <tt>sync</tt>. If you make a change on the server, you need to manually make the change on all repositories which are cloned from this repository. |
| 15 | |
| 16 | You can also set a setting globally on your local machine. The value will be used for all repositories cloned to your machine, unless overridden explicitly in a particular repository. Global settings can be set by using the <tt>-global</tt> option on the <tt>fossil settings</tt> command. |
| 17 | |
| 18 | |
| 19 | <h3>"Versionable" settings</h3> |
| 20 | |
| 21 | Most of the settings control the behaviour of fossil on your local machine, largely acting to reflect your preference on how you want to use Fossil, how you communicate with the server, or options for hosting a repository on the web. |
| 22 | |
| 23 | However, for historical reasons, some settings affect how you work with versioned files. These are <tt>allow-symlinks</tt>, <tt>binary-glob</tt>, <tt>crnl-glob</tt>, <tt>empty-dirs</tt>, <tt>encoding-glob</tt>, <tt>ignore-glob</tt>, <tt>keep-glob</tt> and <tt>manifest</tt>. The most important is <tt>ignore-glob</tt> which specifies which files should be ignored when looking for unmanaged files with the <tt>extras</tt> command. |
| 24 | |
| 25 | Because these options can change over time, and the inconvenience of replicating changes, these settings are "versionable". As well as being able to be set using the <tt>settings</tt> command or the web interface, you can created versioned files in the <tt>.fossil-settings</tt> directory named with the setting name. The contents of the file is the value of the setting, and these files are checked in, committed, merged, and so on, as with any other file. |
| 26 | |
| 27 | Where a setting is a list of values, such as <tt>ignore-glob</tt>, you can use a newline as a separator as well as a comma. |
| 28 | |
| 29 | For example, to set the list of ignored files, create a <tt>.fossil-settings/ignore-glob</tt> file where each line contains a glob for ignored files. |
| 30 | |
| 31 | If you set the value of a setting using the <tt>settings</tt> command as well as a versioned file, the versioned setting will take precedence. A warning will be displayed. |
| 32 |
| --- www/settings.wiki | |
| +++ www/settings.wiki | |
| @@ -1,31 +1,61 @@ | |
| 1 | <title>Fossil Settings</title> |
| 2 | |
| 3 | <h2>Using Fossil Settings</h2> |
| 4 | |
| 5 | Settings control the behaviour of fossil. They are set with the |
| 6 | <tt>fossil settings</tt> command, or through the web interface in |
| 7 | the Settings page in the Admin section. |
| 8 | |
| 9 | For a list of all settings, view the Settings page, or type |
| 10 | <tt>fossil help settings</tt> from the command line. |
| 11 | |
| 12 | |
| 13 | <h3>Repository settings</h3> |
| 14 | |
| 15 | Settings are set on a per-repository basis. When you clone a repository, |
| 16 | a subset of settings are copied to your local repository. |
| 17 | |
| 18 | If you make a change to a setting on your local repository, it is not |
| 19 | synced back to the server when you <tt>push</tt> or <tt>sync</tt>. If |
| 20 | you make a change on the server, you need to manually make the change on |
| 21 | all repositories which are cloned from this repository. |
| 22 | |
| 23 | You can also set a setting globally on your local machine. The value |
| 24 | will be used for all repositories cloned to your machine, unless |
| 25 | overridden explicitly in a particular repository. Global settings can be |
| 26 | set by using the <tt>-global</tt> option on the <tt>fossil settings</tt> |
| 27 | command. |
| 28 | |
| 29 | <h3>"Versionable" settings</h3> |
| 30 | |
| 31 | Most of the settings control the behaviour of fossil on your local |
| 32 | machine, largely acting to reflect your preference on how you want to |
| 33 | use Fossil, how you communicate with the server, or options for hosting |
| 34 | a repository on the web. |
| 35 | |
| 36 | However, for historical reasons, some settings affect how you work with |
| 37 | versioned files. These are <tt>allow-symlinks</tt>, |
| 38 | <tt>binary-glob</tt>, <tt>crnl-glob</tt>, <tt>empty-dirs</tt>, |
| 39 | <tt>encoding-glob</tt>, <tt>ignore-glob</tt>, <tt>keep-glob</tt> and |
| 40 | <tt>manifest</tt>. The most important is <tt>ignore-glob</tt> which |
| 41 | specifies which files should be ignored when looking for unmanaged files |
| 42 | with the <tt>extras</tt> command. |
| 43 | |
| 44 | Because these options can change over time, and the inconvenience of |
| 45 | replicating changes, these settings are "versionable". As well as being |
| 46 | able to be set using the <tt>settings</tt> command or the web interface, |
| 47 | you can created versioned files in the <tt>.fossil-settings</tt> |
| 48 | directory named with the setting name. The contents of the file is the |
| 49 | value of the setting, and these files are checked in, committed, merged, |
| 50 | and so on, as with any other file. |
| 51 | |
| 52 | Where a setting is a list of values, such as <tt>ignore-glob</tt>, you |
| 53 | can use a newline as a separator as well as a comma. |
| 54 | |
| 55 | For example, to set the list of ignored files, create a |
| 56 | <tt>.fossil-settings/ignore-glob</tt> file where each line contains a |
| 57 | glob for ignored files. |
| 58 | |
| 59 | If you set the value of a setting using the <tt>settings</tt> command as |
| 60 | well as a versioned file, the versioned setting will take precedence. A |
| 61 | warning will be displayed. |
| 62 |