Fossil SCM
Replaced a few more bits of local formatting in the adding_code doc with generic "verbatim" blocks, uniformly styled by the skin.
Commit
4003c654b660a9df711f17d2e180441809b30d84be302760baffdb6c22e2b135
Parent
010e5527ce12de1…
1 file changed
+11
-5
+11
-5
| --- www/adding_code.wiki | ||
| +++ www/adding_code.wiki | ||
| @@ -50,11 +50,13 @@ | ||
| 50 | 50 | Do so by editing the file tools/makemake.tcl and adding "xyzzy" (without |
| 51 | 51 | the final ".c") to the list of source modules at the top of that script. |
| 52 | 52 | Save the result and then run the makemake.tcl script using a TCL |
| 53 | 53 | interpreter. The command to run the makemake.tcl script is: |
| 54 | 54 | |
| 55 | - <b>tclsh makemake.tcl</b> | |
| 55 | +<verbatim> | |
| 56 | +tclsh makemake.tcl | |
| 57 | +</verbatim> | |
| 56 | 58 | |
| 57 | 59 | The working directory must be src/ when the command above is run. |
| 58 | 60 | Note that TCL is not normally required to build Fossil, but |
| 59 | 61 | it is required for this step. If you do not have a TCL interpreter on |
| 60 | 62 | your system already, they are easy to install. A popular choice is the |
| @@ -107,11 +109,13 @@ | ||
| 107 | 109 | <h2 id="newcmd">4.0 Creating A New Command</h2> |
| 108 | 110 | |
| 109 | 111 | By "commands" we mean the keywords that follow "fossil" when invoking |
| 110 | 112 | Fossil from the command-line. So, for example, in |
| 111 | 113 | |
| 112 | - <b>fossil diff xyzzy.c</b> | |
| 114 | +<verbatim> | |
| 115 | +fossil diff xyzzy.c | |
| 116 | +</verbatim> | |
| 113 | 117 | |
| 114 | 118 | The "command" is "diff". Commands may optionally be followed by |
| 115 | 119 | arguments and/or options. To create new commands in Fossil, add code |
| 116 | 120 | (either to an existing source file, or to a new source file created as |
| 117 | 121 | described above) according to the following template: |
| @@ -144,13 +148,15 @@ | ||
| 144 | 148 | |
| 145 | 149 | The example above is a fully functioning Fossil command. You can add |
| 146 | 150 | the text shown to an existing Fossil source file, recompiling then test |
| 147 | 151 | it out by typing: |
| 148 | 152 | |
| 149 | - <b>./fossil xyzzy<br> | |
| 150 | - ./fossil help xyzzy<br> | |
| 151 | - ./fossil xyzzy --help</b> | |
| 153 | +<verbatim> | |
| 154 | +./fossil xyzzy | |
| 155 | +./fossil help xyzzy | |
| 156 | +./fossil xyzzy --help | |
| 157 | +</verbatim> | |
| 152 | 158 | |
| 153 | 159 | The name of the C function that implements the command can be anything |
| 154 | 160 | you like (as long as it does not collide with some other symbol in the |
| 155 | 161 | Fossil code) but it is traditional to name the function |
| 156 | 162 | "<i>commandname</i><b>_cmd</b>", as is done in the example. |
| 157 | 163 |
| --- www/adding_code.wiki | |
| +++ www/adding_code.wiki | |
| @@ -50,11 +50,13 @@ | |
| 50 | Do so by editing the file tools/makemake.tcl and adding "xyzzy" (without |
| 51 | the final ".c") to the list of source modules at the top of that script. |
| 52 | Save the result and then run the makemake.tcl script using a TCL |
| 53 | interpreter. The command to run the makemake.tcl script is: |
| 54 | |
| 55 | <b>tclsh makemake.tcl</b> |
| 56 | |
| 57 | The working directory must be src/ when the command above is run. |
| 58 | Note that TCL is not normally required to build Fossil, but |
| 59 | it is required for this step. If you do not have a TCL interpreter on |
| 60 | your system already, they are easy to install. A popular choice is the |
| @@ -107,11 +109,13 @@ | |
| 107 | <h2 id="newcmd">4.0 Creating A New Command</h2> |
| 108 | |
| 109 | By "commands" we mean the keywords that follow "fossil" when invoking |
| 110 | Fossil from the command-line. So, for example, in |
| 111 | |
| 112 | <b>fossil diff xyzzy.c</b> |
| 113 | |
| 114 | The "command" is "diff". Commands may optionally be followed by |
| 115 | arguments and/or options. To create new commands in Fossil, add code |
| 116 | (either to an existing source file, or to a new source file created as |
| 117 | described above) according to the following template: |
| @@ -144,13 +148,15 @@ | |
| 144 | |
| 145 | The example above is a fully functioning Fossil command. You can add |
| 146 | the text shown to an existing Fossil source file, recompiling then test |
| 147 | it out by typing: |
| 148 | |
| 149 | <b>./fossil xyzzy<br> |
| 150 | ./fossil help xyzzy<br> |
| 151 | ./fossil xyzzy --help</b> |
| 152 | |
| 153 | The name of the C function that implements the command can be anything |
| 154 | you like (as long as it does not collide with some other symbol in the |
| 155 | Fossil code) but it is traditional to name the function |
| 156 | "<i>commandname</i><b>_cmd</b>", as is done in the example. |
| 157 |
| --- www/adding_code.wiki | |
| +++ www/adding_code.wiki | |
| @@ -50,11 +50,13 @@ | |
| 50 | Do so by editing the file tools/makemake.tcl and adding "xyzzy" (without |
| 51 | the final ".c") to the list of source modules at the top of that script. |
| 52 | Save the result and then run the makemake.tcl script using a TCL |
| 53 | interpreter. The command to run the makemake.tcl script is: |
| 54 | |
| 55 | <verbatim> |
| 56 | tclsh makemake.tcl |
| 57 | </verbatim> |
| 58 | |
| 59 | The working directory must be src/ when the command above is run. |
| 60 | Note that TCL is not normally required to build Fossil, but |
| 61 | it is required for this step. If you do not have a TCL interpreter on |
| 62 | your system already, they are easy to install. A popular choice is the |
| @@ -107,11 +109,13 @@ | |
| 109 | <h2 id="newcmd">4.0 Creating A New Command</h2> |
| 110 | |
| 111 | By "commands" we mean the keywords that follow "fossil" when invoking |
| 112 | Fossil from the command-line. So, for example, in |
| 113 | |
| 114 | <verbatim> |
| 115 | fossil diff xyzzy.c |
| 116 | </verbatim> |
| 117 | |
| 118 | The "command" is "diff". Commands may optionally be followed by |
| 119 | arguments and/or options. To create new commands in Fossil, add code |
| 120 | (either to an existing source file, or to a new source file created as |
| 121 | described above) according to the following template: |
| @@ -144,13 +148,15 @@ | |
| 148 | |
| 149 | The example above is a fully functioning Fossil command. You can add |
| 150 | the text shown to an existing Fossil source file, recompiling then test |
| 151 | it out by typing: |
| 152 | |
| 153 | <verbatim> |
| 154 | ./fossil xyzzy |
| 155 | ./fossil help xyzzy |
| 156 | ./fossil xyzzy --help |
| 157 | </verbatim> |
| 158 | |
| 159 | The name of the C function that implements the command can be anything |
| 160 | you like (as long as it does not collide with some other symbol in the |
| 161 | Fossil code) but it is traditional to name the function |
| 162 | "<i>commandname</i><b>_cmd</b>", as is done in the example. |
| 163 |