Changes

<{{cmd>|starttyping</cmd>}},<{{cmd>|typebuffer</cmd>}}

=In-line Inline text=

To typeset code inside the paragraph, you have the command <code>\startTEX ... \stopTEXtype</code> only works when typesetting the whole paragraph. If you need to type only a command or two as in-line text, you It can use the following be configured with <code>\setuptype[type][User:Taco|Taco's...]] macro (hopefully this will land in the core once in the future):</code>.

To have colored code, you need to use <texcodecode>\def\typeTEXdefinetype[NAME][option=TEX]</code> and use it with the name you chose. Other values are: <code>mp lua xml parsed-xml nested tex context</code>. {\bgroup \def\processinlineverbatim##1%An example that shows both features: {\processingverbatimtrue \localcatcodestrue<context source="yes"> \def\endofverbatimcommand{\TEXendofcommand##1}%definetype[inlineTEX][option=TEX] \bgroup This is the way to type code: \aftergroup\endofverbatimcommand \futurelet\next\doprocessinlineverbatim}% \initializetypingtype{TEX}% \startverbatimcolor the \processinlineverbatimConTeXt\egroup command}</texcode>.

Now you can sayAnd this is the way to have colored code:\inlineTEX{the \ConTeXt\ command},</context>

= Making a tight vertical fit =By default, typing environments include some blank space before the first line and after the last line of the verbatim text. This is because the <texcodett>\typeTEX+\typeTEX{\typeTEX is a wonderful macro}+, isn't it?before</tt> and <tt>after</texcodett>commands are set to <contexttt>\setupcolors[state=start]\def\typeTEX {\bgroup \def\processinlineverbatim##1% {\processingverbatimtrue \localcatcodestrue \def\endofverbatimcommand{\TEXendofcommand##1}% \bgroup \aftergroup\endofverbatimcommand \futurelet\next\doprocessinlineverbatim}% \initializetyping{TEX}% \startverbatimcolor \processinlineverbatim\egroup }blank</tt> by default. For example:

<context source="yes">\typeTEX+framed[offset=0mm,strut=no,align=right]{\typeTEX{starttypingFoo\typeTEX is a wonderful macrostoptyping}+, isn't it?

Source: [http:Here, we've added a <tt>\framed</tt> so you can see the extra spacing, but with <tt>offset=0mm</tt> and <tt>strut=no</tt> to prevent framed from introducing spacing, and <tt>align=right</archive.contextgardentt> to prevent framed from eating all newlines (not sure why that works like this).net To prevent this extra vertical space, we must unset the <tt>before</threadtt> and <tt>after</20050907.093522.baf795f5.en.htmltt> options:<context source="yes">\setuptyping[before=,after=]\framed[offset=0mm,strut=no,align=right]{\starttypingFoo\stoptyping}</context>

 There are already some formatters for several programming languages in the ConTeXt distribution:distributionr. The following list is for MkII and MkIV.

! Language !! Code for MkII !! LanguageCode for MkIV

| C || [[source:verb-c.texmkii|C]] || [[modules:pret-c| C]]

| Eiffel || [[source:verb-eif.texmkii|EIF]] || Eiffel

| JavaScript || [[source:verb-js.texmkii|JS]] || JavaScript

| Java || [[source:verb-jv.texmkii|JV]] || Java

| Lua || || [[source:verbpret-mplua.texlua|MPLUA]] || MetaPost & MetaFont

| MetaPost & MetaFont || [[source:verb-pasmp.texmkii|PASMP]] || Pascal & Modula[[source:pret-mp.lua|MP]]

| Pascal & Modula || [[source:verb-plpas.texmkii|PLPAS]] || Perl 5

| Perl 5 || [[source:verb-sqlpl.texmkii|SQLPL]] || SQL

| SQL || [[source:verb-texsql.texmkii|TEXSQL]] || TeX

| TeX || [[source:verb-tex.mkii|TEX]] || [[source:pret-tex.lua|TEX]] |- | XML || [[source:verb-xml.texmkii|XML]] || [[source:pret-xml.lua| XML]]

Your file has You refer to have a pretty printer using its name like (''e.g.'', the<tt>xxxx</tt> in <tt>verb-xxxx.tex</tt>, with or <tt>pret-xxxx.lua</tt> a ),which should be in lowercase short identifier (example: verb-php.tex)Before you can use a pretty printer, and then you have to use one or two commands to make should let ConTeXt use know about it (this has already been done for the fileincluded formatters).

This maps the command <code>\starttyping[option=PHP]</code> to the<tt>php</tt> pretty printer. The first argument is the option as passed to \starttyping, the second argument is an uppercase version of the pretty printer name(''e.g.'' <tt>xxxx</tt> ) (thus allowing ConTeXt to find the file),.

Because that allows <code>\startPHP ... \stopPHP</code> as a shortcut to <tt>\setuptypingstarttyping[option=PHP]... \stoptyping</tt>. === How to write the pretty printer? ===For MkII, there seems to be no real documentation here. You should takea good look at the existing formatters and base your work off those.However, if you really need custom pretty printing, you might be betterof to look at MkIV instead, since that allows you to write a prettyprinter in lua, which is a lot less painful than writing them in plainTeX.

Unless you need that highlighting urgently, I would wait for LuaTeX == Improved pretty printing == Default ConTeXt comment handling can be shown in the following sample: <context source="yes">\starttext\startbuffer[texcode]This is text. % and this is a comment\stopbuffer \startbuffer[xmlcode]<p>This is text.<!--and write it in lua this is a comment--></p>\stopbuffer \startbuffer[luacode]if code=="code" then (which --this is a comment --[[this is certainly less painful than writing it in plain TeX). But it's up to a multiline comment--]] ---[[but this isn’t a multiline comment--]]\stopbuffer \typebuffer[texcode][option=TEX]\typebuffer[xmlcode][option=XML]\typebuffer[luacode][option=LUA]\stoptext</context> If you. I found those TeX definitions too complicated want to even try improve Lua multiline comments and to understandcolor the whole comments (not only the comment marker), write <code>\usemodule[scite]</code> before <code>\starttext</code>. (I would never dare cannot show it here, since ConTeXt at the wiki seems to try writing one by myselfhave a problem with that. -- Mojca)

In technical documents it can be required to display some code listings with the line numbers. You can do this with ConTeXt, and even more. All the features shown here are also available when displaying external files with <{{cmd>|typefile</cmd>}}.

To have the line numbers in the text, change the linenumbering setup like this(<tt>location=text</tt> for mkiv resp.):

b) you have a large project involving many code snippet snippets to be inserted and colorized

It is not difficult at all fairly simple to write a little parser which takes as its input your source file and gives in output a .tex file containing the code plus the opportune commands for colorization. You can then include the resulting .tex file in the global ConTeXt document file.As an example, [http://www.cirmafonurgia.unito.it/andrea/sw/sc/scToConTeXt.py this] is a Python script for the SuperCollider language, which has a strict Smalltalk-like syntax. Fed with the following source code contained in e.g. example.sc file:

/BTEX{\color[SCred] {//// an example starting with a comment}/ETEX/BTEX{\color[SCgrey] {"this is a string"}/ETEX .postln ;

/BTEX{\color[SCgreen] \type{\}letterbackslash aSymbol}/ETEX ;

/BTEX{\color[SCblue] ThisClassDoesNotExist{ThisClassDoesNotExists}/ETEX ;

Note that inside the block the text is no more verbatim, so you have to define some string replacement replacements for special characters (e.g. _, %, $ , \, etc). The As an example, the problem of the slash backslash (\) is solved here by wrapping the character within a type commandreplacing it with \letterbackslash.  You can then insert example. tex in your ConTeXt file with <texcode>\input example</texcode>  The example .tex file uses some definitions (explained beforein the previous sections) which have to be put in the global ConTeXt file(use <tt>escape=yes</tt> instead of <tt>option=commands</tt> for mkiv).

alsoAlso, example.tex requires color definitions, which are created following SuperCollider colorization interpreter scheme and have to be inserted in the global ConTeXt filetoo:

You can then insert example.tex in The previous definitions will be used for all the global ConTeXt file code files inserted with <texcode>\input .After compiling, this is the result of the discussed example</texcode>:

/BTEX{\color[SCgreen] \type{\}letterbackslash aSymbol}/ETEX ;

/BTEX{\color[SCblue] ThisClassDoesNotExistThisClassDoesNotExists}/ETEX ;

If your document is inteded to provide code examples to be tested by the readers, the presence of format signs (e.g. line numbers) can create some troubles while copying and pasting the code text from your document to the language environment. More generally, the copy and paste approach, being slow and possbily possibly related to encodings, is not satisfying at all.

 So that you can have this structure for each code snippet: <texcode>\input example \useattachment[ex][example.sc]\attachment[ex]</texcode>  The commands embed example.sc in the pdf, so that it is accessible by double-clicking on a generated icon. In this case the icon is placed after the colorized code frame.If you use Acrobat Reader (Preview.app in MacOSX does not provide support for the behaviour) example.sc will be open in the related application (ie.eg. SuperCollider.appin the discussed case).