Search results
Jump to navigation
Jump to search
Create the page "Command/Debugging" on this wiki! See also the search results found.
- ...ers/typesetters.suspects]]. See [[Visual Debugging]] for some other visual debugging aids. [[Category:Command/Debugging|enabletrackers]]1 KB (168 words) - 20:51, 13 January 2020
- [[Category:Command/Debugging|currentproject]] [[Category:Command/Projects|currentproject]]879 bytes (89 words) - 14:43, 15 November 2019
- [[Category:Command/Debugging|currentproduct]] [[Category:Command/Projects|currentproduct]]857 bytes (85 words) - 14:43, 15 November 2019
- [[Category:Command/Debugging|currentproject]] [[Category:Command/Projects|currentproject]]857 bytes (85 words) - 14:43, 15 November 2019
- ...de> prints information related to what one might call 'document and layout debugging': slugs behind overfull lines, and mentions of succesful and failed referen [[Category:Command/Miscellaneous|version]]2 KB (301 words) - 14:39, 15 November 2019
- [[Category:Command/Debugging|currentproject]] [[Category:Command/Projects|currentproject]]828 bytes (83 words) - 14:43, 15 November 2019
- [[Category:Command/Debugging|currentproject]] [[Category:Command/Projects|currentproject]]873 bytes (85 words) - 14:43, 15 November 2019
- [[Category:Command/Debugging|currentcomponent]] [[Category:Command/Projects|currentcomponent]]963 bytes (101 words) - 14:43, 15 November 2019
- The command <code>\texengineversion</code> provides the version number of the TeX compi [[Category:Command/Internals|texengineversion]]1 KB (123 words) - 16:30, 11 November 2019
- The command <code>\contextmark</code> provides the name of the engine used. [[Category:Command/Internals|contextmark]]1 KB (141 words) - 16:22, 11 November 2019
- The command <code>\contextversionnumber</code> provides the name of the engine used. [[Category:Command/Internals|contextversionnumber]]1 KB (162 words) - 07:24, 2 July 2020
- The command <code>\texenginename</code> provides the name of the engine used. To print LuajitTeX when used, one can define the following command:2 KB (208 words) - 16:30, 11 November 2019
- [[Category:Command/Debugging|ruledhbox]]1,009 bytes (126 words) - 20:51, 13 January 2020
- <h1 class="command">\input</h1> <div class="cd:shortdesc">The command <tt>\input</tt> inputs external files2 KB (317 words) - 08:39, 19 November 2021
- The command <code>\contextversion</code> provides the version number of the ConTeXt ins [[Category:Command/Internals|contextversion]]1 KB (170 words) - 16:22, 11 November 2019
- <h1 class="command">\setupfontexpansion</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->3 KB (372 words) - 08:40, 14 May 2023
- [[Category:Command/Debugging]] [[Category:Command/MkIV only]]1 KB (165 words) - 13:31, 8 June 2020
- ...er product (or component) the <code>context</code> or <code>texexec</code> command was invoked on. [[Category:Command/Internals|jobname]]2 KB (253 words) - 16:26, 11 November 2019
- ...are still the same. Work-in-progress page on current [[LMTX]] version is [[Debugging]]. ...with {{cmd|show...}} or {{cmd|trace...}}. While {{cmd|showsomething}} is a command that immediately inserts something, {{cmd|tracesomethingtrue}} or ...<tt>fa5 KB (619 words) - 11:05, 9 February 2021
- ...arguments|Commands with Key=Value arguments]]: (Topic: things like <code>\command[thiskey=thatvalue]</code>.) == Debugging ==8 KB (1,140 words) - 10:11, 16 December 2021
- === Debugging features === OpenType features can be complicated to understand or debug. One useful command to see how they are working is {{cmd|showotfcomposition}}.11 KB (1,564 words) - 08:29, 2 July 2022
- Implements a command that causes the commands specified in its argument to be expanded after the Provides a package which defines a command \fontsample (which will print a sample of the current font), and a document6 KB (806 words) - 18:47, 24 April 2024
- %Visual Debugging, to be commented out later: %\showlayout %for Debugging, to be commented out later25 KB (1,585 words) - 07:19, 14 March 2024
- == An extension for editing `/Command` subpages == ...o edit the ConTeXt command reference pages (the ones that live under the `/Command/` URL.11 KB (1,837 words) - 19:11, 5 September 2020
- Trackers print debugging information to the [[Log file|log file]]. They can be enabled with {{cmd|en ...e|trackers.register}} in the source code; it can also be produced from the command line with12 KB (1,564 words) - 15:42, 8 June 2020
- command=\MyChapterCommand, ...the copy-editing and production phase, I need to add some tools for visual debugging.9 KB (817 words) - 10:39, 11 February 2011
- ...ftware for manipulating digital images. Once installed on your system, the command ...vie, which is done with the free ''ffmpeg'' (https://ffmpeg.org) tool. The command11 KB (1,697 words) - 14:50, 23 April 2024
- ...es, bibliographies, indices, typesetting for [[Chemistry|chemistry]] and [[Command/unit|physics]], [[Modes|conditional compilation]], processing [[XML]] data, ...ommands, [[Trackers]], directives, code checking) included; no useless TeX command line stops any more.20 KB (3,041 words) - 18:34, 23 April 2024
- * {{code|x-setups}} ({{src|x-setups.mkiv}} etc.): load and typeset command syntax from interface files * {{code|m-visual}} ({{src|m-visual.mkiv}}): [[Visual Debugging]] (described in [[This_Way_-_My_Way#ThisWay|ThisWay]] no.7 [[magazine:0007|30 KB (4,080 words) - 10:44, 12 May 2024