Difference between revisions of "Inside ConTeXt"

From Wiki
Jump to navigation Jump to search
m (Added Console Mode link.)
m (→‎Programming Topics: : Added link to Modes.)
Line 2: Line 2:
== Programming Topics ==
== Programming Topics ==
=== ConTeXt Features ===
* [[Modes]]: Document options that can be selected when the document is processed.
=== Commands and Arguments ===
=== Commands and Arguments ===

Revision as of 06:33, 5 September 2005

< Main Page >

Programming Topics

ConTeXt Features

  • Modes: Document options that can be selected when the document is processed.

Commands and Arguments

Programming Techniques


  • Console Mode: Using ConTeXt on keyboard input directly, rather than loading a .tex file.

Using variables


TODO: This could really use a specific example or two. (See: To-Do List)

Defining new commands

Special characters in command names

Some commands have special characters in their names, that TeX normally does not consider to be letters: @, ! and ?. Before and after the use or definition of such protected commands in your input files, the catcode of these characters has to be changed. This is done by \unprotect and \protect:


The newly defined command \!test can of course only be called upon when we are in the \unprotected state, otherwise TeX reads the command \!, followed by the word test (and probably complains loudly about not being in math mode). These protection/unprotection commands can be nested. When the nesting becomes deeper than one level, the system reports the current protection level. It is a good habit to always start your macro files with \unprotect and end them with \protect.

Passing verbatim text as macro parameter

In case you want to write macros that should handle verbatim text, you can use the tex primitives \obeyspaces and \obeylines. \obeyspaces changes the category code of the space character, so that spaces become significant. \obeylines does the same for the newline character.

This works fine for the following example:

\framed{\obeyspaces{A gap from here     to there!}}

But if you pass this text as a parameter for your own macro \TextWithSpaces

\TextWithSpaces{A gap from here     to there!}

the additional spaces are ignored. This happens because the category code change is not yet in effect when the argument is parsed, and the spaces are removed during parsing. To keep the spaces, the catcode change must be done before the argument is parsed.

Here is a two-part solution for the problem (suggested by Taco Hoekwater):


Another way is to postpone argument loading (suggested by Hans Hagen).

\def  \TextWithSpaces  {\framed\bgroup\obeyspaces\doTextWithSpaces}
\def\doTextWithSpaces     #1{#1\egroup} 

Both of these produce the desired result: