Search results

Jump to navigation Jump to search
  • <td>file typing name </td> ...typing environment, the second argument are the options to apply for this environment.
    2 KB (178 words) - 20:46, 13 January 2020
  • ==== Typing Environment Inclusions ==== The parser supports marking the following typing environments:
    3 KB (367 words) - 00:56, 23 April 2022
  • ...en called with a single argument, this command changes the options for all typing environments: {{cmd|starttyping}}, {{cmd|startTEX}} etc. as well as {{cmd|t With the optional argument, it affects only specific typing environment (as created with {{cmd|definetyping}}).
    2 KB (250 words) - 17:28, 29 July 2023
  • ; Typing one $ gets you $$ with the insertion point between them. ; Typing a second $ turns the $$ into ConTeXt's form for displayed math:
    8 KB (841 words) - 10:57, 2 July 2020
  • ...also note [https://superuser.com/questions/284342/what-are-path-and-other-environment-variables-and-how-can-i-set-or-use-them]) ...n\bin</tt> for using <tt>context-setup-mswin.zip</tt>) to the search path (environment variable <tt>path</tt> under advanced system properties). If you are the on
    5 KB (850 words) - 16:03, 8 June 2020
  • Unlike LaTeX's <code>verbatim</code> environment, ConTeXt's <code>typing</code> environments have quite a range of built-in options for formatting t By default, typing environments include some blank space before the first line and after the l
    23 KB (3,313 words) - 01:05, 13 August 2023
  • ...errors (one per line). The cursor will stay in the main document, so your typing workflow will not ...in <tt>$PATH</tt>. For more fine grained control over the command and its environment, you may invoke `context.Typeset()` directly (or `context#Typeset()` from l
    24 KB (3,766 words) - 06:57, 31 July 2023
  • ...n\bin</tt> (eg <tt>c:\context\tex\texmf-mswin\bin</tt>)to the search path (environment variable <tt>path</tt> under advanced system properties). If you are the on ...mputer. You can check that the path is there by opening command prompt and typing
    6 KB (1,090 words) - 12:05, 6 June 2014
  • ...xecute Lua code in a ConTeXt document: The command {{cmd|ctxlua}}, and the environment {{cmd|startluacode}}…{{cmd|stopluacode}}. Both are wrappers around the Lu Inside the {{cmd|startluacode}}…{{cmd|stopluacode}} environment, newlines and special characters behave normally. This solves the catcode p
    23 KB (3,423 words) - 07:15, 13 July 2023
  • ...nstalling a complete ConTeXt installation for each project in a production environment. The installation tree is portable (see Moving the Installation Around, bel ...our application's invocation of ConTeXt, you will need to set up the shell environment. This is easily done by creating a simple BASH shell script, also to be in
    22 KB (3,335 words) - 05:15, 11 April 2023
  • ...|enableregime}}<code>[some]</code>, preferably in your [[Project_structure|environment file]]. ...ine ([[Mark IV]]) all utf8 characters from your font may be used directly. Typing some characters may require some keyboard setting or may not be possible at
    15 KB (2,430 words) - 13:17, 9 August 2020
  • ...here the fonts should be looked for, by setting the <code>OSFONTDIR</code> environment variable. On Windows, this might be achieved by running ...the next run of <code>context</code>. You can also generate it manually by typing
    24 KB (3,172 words) - 17:57, 22 January 2023