Search results
Jump to navigation
Jump to search
Create the page "Command/value:commands" on this wiki! See also the search results found.
- <h1 class="command">\startcomponent ... \stopcomponent</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->2 KB (263 words) - 13:11, 6 September 2020
- To avoid clashes with existing and future commands, any module Context provides the user command {{cmd|definenamespace}}7 KB (1,036 words) - 07:34, 17 July 2023
- {{See also casing commands}} [[Category:Command/Fonts|CAP]]793 bytes (98 words) - 14:55, 15 October 2019
- <h1 class="command">\<i>delimitedtext</i></h1> <!-- a short command summary goes here -->3 KB (365 words) - 08:56, 21 August 2020
- ...ng the reader to run <code>tex</code>, and then simply start typing at the command line that appears. This is a good way to explore TeXing, as there's no nee ...that one generally wants to put into the document each time. However, the command line <i>is</i> very useful for experimenting with programming; one can defi1 KB (219 words) - 13:22, 9 August 2020
- <h1 class="command">\<i>language</i></h1> ...e of those limitations, it is generally better to use the {{cmd|language}} command instead of directly accessing a language switching control sequence.1 KB (214 words) - 15:46, 11 November 2021
- {{See also casing commands}} [[Category:Command/Fonts|cap]]728 bytes (91 words) - 19:34, 13 January 2020
- The need for these commands appears when you have to strip braces from a (saved) argument. For instance \dosingleargument\command = \command[#1]6 KB (720 words) - 16:52, 8 June 2020
- ...e value of the `\linewidth` register, which is applied by most `\setup...` commands to set `rulethickness`, e.g. {{cmd|setupframed}}, {{cmd|setupbackgrounds}}, [[Category:Command/Paragraphs|setuplinewidth]]709 bytes (82 words) - 14:30, 29 March 2020
- ==Commands== <tr><th>Command</th><th>Description</th></tr>4 KB (508 words) - 15:29, 8 June 2020
- ...in ConTeXt with the <tt>\setupalign[line]</tt> directive. The rest of the commands in the examples below are merely to produce fake text to illustrate the eff2 KB (387 words) - 22:26, 28 September 2005
- <h1 class="command">\project</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->2 KB (328 words) - 13:08, 6 September 2020
- ...expressions used within text), since by default TeX ignores spaces after a command macro. Compare the following two definitions.728 bytes (106 words) - 16:06, 8 June 2020
- [[Category:Command/TeX commands|hrule]] [[Category:Command/Rules|hrule]]999 bytes (134 words) - 18:23, 19 November 2019
- This macro is to be used inside custom defined section commands to propagate the options set in {{cmd|setuphead}}. The options which are s <span class="cmd">[[Command/keyword:align|align]]</span>,2 KB (199 words) - 19:27, 13 January 2020
- <h1 class="command">\ReadFile</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->3 KB (407 words) - 08:23, 1 November 2021
- <td>see [[Command/setuptyping|\setuptyping]] </td> ...yping environment and the corresponding <tt>\start</tt> and <tt>\stop</tt> commands. The first argument is the name of the typing environment, the second argum2 KB (178 words) - 20:46, 13 January 2020
- ==Commands== : To disable sectioning commands, set <tt>\SetupSteps[defaultsection=page]</tt>.8 KB (1,049 words) - 15:16, 8 June 2020
- Now if one needs to pass arguments from Lua to a macro command defined in ConTeXt, one has several possibilities. The same applies to all the commands which take one or more parameters, provided that in their definition no spe3 KB (482 words) - 15:31, 14 December 2020
- Place headers and footers with the commands \setupheadertexts and {{cmd|setupfootertexts}}. These commands take 4 arguments. The first is for the left handed side on odd pages, the s3 KB (420 words) - 08:07, 20 March 2024