DOCSLIB.ORG

GNU Texinfo Reference Card @Contents Print a Complete Table of Contents

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
GNU Texinfo Reference Card @Contents Print a Complete Table of Contents GNU Texinfo Reference Card @contents Print a complete table of contents. Has no effect in @subsubheading title Print an unnumbered subsubsection-like (for Texinfo version 4.13) Info, which uses menus instead. heading. http://www.gnu.org/software/texinfo/ @setcontentsaftertitlepage Put the table of contents after the `@end titlepage' even if the @contents is at the end. Menus Texinfo document skeleton @setshortcontentsaftertitlepage Place the short table @menu Mark the beginning of a menu of nodes in Info. No effect of contents after the `@end titlepage' command even if the in a printed manual. Pair with @end menu. Texinfo source files are plain text; standard extensions are @shortcontents command is at the end. @detailmenu Mark the (optional) detailed node listing in a master `.texinfo', `.texi', and `.txi'. A Texinfo file must begin with menu. lines like this: Nodes \input texinfo @node name, next, previous, up Begin a new node. The Cross references @setfilename info-file-name next, previous, and up pointers are usually omitted in a Within the Info system @settitle name-of-manual normally-structured document. @xref {node, [entry] , [node-title] , [info-file] , [manual] } Makes ::: the contents of the Texinfo document follow, ending with: @top title Mark the topmost @node in the file, which must be a reference that starts with `See' in a printed manual. Follow @bye defined on the line immediately preceding @top. The title is command with punctuation. Only the first argument is formatted as a chapter-level heading. The entire top node, mandatory. Texinfo @-commands including the @node and @top lines, are normally enclosed with @pxref {node, [entry] , [node-title] , [info-file] , [manual] } Like @ifnottex ... @end ifnottex. @xref, but starts with `see' instead of `See', and must be used Beginning a Texinfo document @anchor {name} Define name as the current location, for use as a inside parentheses. The commands in this section are given approximately in the cross-reference target. @ref {node, [entry] , [node-title] , [info-file] , [manual] } Like @xref, order in which they conventionally appear. @novalidate Suppress validation of node references and omit but produces only the bare reference without `See' or `see'; must @setfilename info-file-name Provide a name to be used for the creation of auxiliary files with TEX. Use before @setfilename. be followed by a punctuation mark. output files. This command is essential for TEX formatting as Chapter structuring @inforef {node, [entry-name] , info-file} Make a cross reference to well, even though it produces no output. Should be the first an Info file for which there is no printed manual. command in the input. @lowersections Change subsequent chapters to sections, sections to subsections, and so on. Outside of Info @settitle title Specify document title. @raisesections Change subsequent sections to chapters, @url {url, [displayed-text] , [replacement] } Make a hyperlink Internationalization subsections to sections, and so on. reference to a uniform resource locator. @uref is a synonym. enc Declare the input encoding to be enc; use @documentencoding Numbered, included in contents @cite {title} Indicate the name of a book or other reference that right after @setfilename. Default is US-ASCII; other possibilities: has no Info file; no hyperlink. UTF-8, ISO-8859-1, koi8-r, ::: @chapter title Begin a numbered chapter; title appears in the table of contents. @documentlanguage LL[_CC] Declare the current language as the Marking words and phrases title Like , with chapter title centered. two-character ISO-639 abbreviation LL, optionally followed by @centerchap @chapter Markup for regular text an underscore and a two-letter ISO 3166 two-letter country code Context-dependent, included in contents @emph {text} Emphasize text, by using italics where possible, and (CC). Default is en_US. @section title Begin a section within a chapter. Within @chapter enclosing in asterisks in Info. Info directory specifications and @appendix, the section is numbered; within @unnumbered, it is @strong {text} Emphasize text even more strongly, by using bold @dircategory category name Specify an Info directory section unnumbered. where possible; still enclosed in asterisks in Info. for this file’s entries. Can be repeated. We try to follow the @subsection title Begin a subsection within a section. Same @var {metasyntactic-variable} Indicate a meta variable (a name categories in the Free Software Directory. context-dependent numbering as @section. that stands for another piece of text). @direntry Begin the Info directory menu entries for this file. Pair @subsubsection title Begin a numbered subsubsection within a @dfn {term} Indicate the introductory or defining use of a with @end direntry. subsection. Same context-dependent numbering as @section. technical term. HTML document description Unnumbered, included in contents @acronym {acronym} Indicate an acronym written in all captial letters, such as `NASA'. @documentdescription Set the document description text for @unnumbered title Begin an unnumbered chapter. abbreviation Indicate a general abbreviation, such as HTML; default is just the title of the document. Pair with @end @unnumberedsec title Begin an unnumbered section. @abbr { } documentdescription. @unnumberedsubsec title Begin an unnumbered subsection. `Comput.' Title pages @unnumberedsubsubsec title Begin an unnumbered subsubsection. Markup for literal text @shorttitlepage title Generate a minimal title page, generally for Lettered and numbered, included in contents @code {sample-code} Indicate an expression, a syntactically complete token, or a program name. Unquoted in Info output. the first page of output in a long printed manual. @appendix title Begin an appendix. @file {filename} Indicate the name of a file, buffer, node, @center line-of-text Center line-of-text, usually for titles. @appendixsec title Begin an appendix section within an appendix; directory, etc. @titlefont {text} In a printed manual, print text in a larger than @appendixsection is a synonym. command-name Indicate a system command name, normal font. Ignored in Info. @appendixsubsec title Begin an appendix subsection; @command { } such as . @titlepage Begin the title page. Write the command on a line of @appendixsubsection is a synonym. ls its own, paired with @end titlepage. Ignored in Info. @appendixsubsubsec title Begin an appendix subsubsection; @env {environment-variable} Indicate an environment variable @title title Within @titlepage, display title appropriately. @appendixsubsubsection is a synonym. name, such as PATH. @subtitle subtitle Within @titlepage, display subtitle. @option {option-name} Indicate a command-line option, such as Unnumbered, not in contents, no new page -v and --help. @author author Within @titlepage, display author. @chapheading title Print an unnumbered chapter-like heading. @kbd {keyboard-characters} Indicate characters of input to be Tables of contents @majorheading title Like @chapheading, but generate additional typed by users. @shortcontents Print a short table of contents (chapter-level vertical whitespace before the heading. @key {key-name} Indicate the name of a key on a keyboard. entries only). Not relevant to Info. @heading title Print an unnumbered section-like heading. @email {address, [displayed-text] } Indicate an email address. @summarycontents Synonym for @shortcontents. @subheading title Print an unnumbered subsection-like heading. @indicateurl {url} Indicate a uniform resource locator, but Lists and tables @syncodeindex from-index to-index Merge the contents of without creating any hyperlink. @itemize mark-command Begin an unordered list, using @item for from-index into to-index, formatting the entries in from-index @samp {text} Indicate a sequence of literal characters, in general. each entry, which consist of indented paragraphs, with a mark with @code. Quoted in Info output. such as @bullet inside the left margin at the beginning of each @synindex from-index to-index Merge the contents of from-index @verb {delimchar literal-text delimchar} Output literal-text, item. Pair with @end itemize. into to-index; no special formatting. delimited by the single character delimchar, exactly as is, @enumerate [number-or-letter] Begin a numbered list, using @item @printindex index-name Generate an alphabetized index (using including any whitespace or Texinfo special characters. Example: for each entry. Optionally, start list with number-or-letter and two columns in a printed manual). @verb{|@ @}|}. count from there; by default, number consecutively from `1'. Pair Insertions within a paragraph Explicit font selection with @end enumerate. @table formatting-command Begin a two-column table Characters special to Texinfo @sc {text} Set text in a small caps font in printed output, and (description list), using for each entry. Write each first uppercase in Info. No other font command has any effect in Info. @item @@ Insert an at sign, `@'. column entry on the same line as @item. formatting-command is Insert a left brace, `f'. @r {text} Set text in the regular roman font. @{ applied to each first column entry. Pair with @end table. Insert a right brace, `g'. @i {text} Set text in an italic font. @} @ftable formatting-command Like @table, but automatically Insert a comma character; needed only when a literal @slanted {text} Set text in a slanted (oblique) font if possible. @comma {} enter each first column entry in the function index. comma would be an argument separator, as in @xref. @b {text} Set text in a bold font. @vtable formatting-command
Load more

Recommended publications
  • Bringing GNU Emacs to Native Code
    Bringing GNU Emacs to Native Code Andrea Corallo Luca Nassi Nicola Manca [email protected] [email protected] [email protected] CNR-SPIN Genoa, Italy ABSTRACT such a long-standing project. Although this makes it didactic, some Emacs Lisp (Elisp) is the Lisp dialect used by the Emacs text editor limitations prevent the current implementation of Emacs Lisp to family. GNU Emacs can currently execute Elisp code either inter- be appealing for broader use. In this context, performance issues preted or byte-interpreted after it has been compiled to byte-code. represent the main bottleneck, which can be broken down in three In this work we discuss the implementation of an optimizing com- main sub-problems: piler approach for Elisp targeting native code. The native compiler • lack of true multi-threading support, employs the byte-compiler’s internal representation as input and • garbage collection speed, exploits libgccjit to achieve code generation using the GNU Com- • code execution speed. piler Collection (GCC) infrastructure. Generated executables are From now on we will focus on the last of these issues, which con- stored as binary files and can be loaded and unloaded dynamically. stitutes the topic of this work. Most of the functionality of the compiler is written in Elisp itself, The current implementation traditionally approaches the prob- including several optimization passes, paired with a C back-end lem of code execution speed in two ways: to interface with the GNU Emacs core and libgccjit. Though still a work in progress, our implementation is able to bootstrap a func- • Implementing a large number of performance-sensitive prim- tional Emacs and compile all lexically scoped Elisp files, including itive functions (also known as subr) in C.
    [Show full text]
  • Downloads." the Open Information Security Foundation
    Performance Testing Suricata The Effect of Configuration Variables On Offline Suricata Performance A Project Completed for CS 6266 Under Jonathon T. Giffin, Assistant Professor, Georgia Institute of Technology by Winston H Messer Project Advisor: Matt Jonkman, President, Open Information Security Foundation December 2011 Messer ii Abstract The Suricata IDS/IPS engine, a viable alternative to Snort, has a multitude of potential configurations. A simplified automated testing system was devised for the purpose of performance testing Suricata in an offline environment. Of the available configuration variables, seventeen were analyzed independently by testing in fifty-six configurations. Of these, three variables were found to have a statistically significant effect on performance: Detect Engine Profile, Multi Pattern Algorithm, and CPU affinity. Acknowledgements In writing the final report on this endeavor, I would like to start by thanking four people who made this project possible: Matt Jonkman, President, Open Information Security Foundation: For allowing me the opportunity to carry out this project under his supervision. Victor Julien, Lead Programmer, Open Information Security Foundation and Anne-Fleur Koolstra, Documentation Specialist, Open Information Security Foundation: For their willingness to share their wisdom and experience of Suricata via email for the past four months. John M. Weathersby, Jr., Executive Director, Open Source Software Institute: For allowing me the use of Institute equipment for the creation of a suitable testing
    [Show full text]
  • GNU Wget 1.10 the Non-Interactive Download Utility Updated for Wget 1.10, Apr 2005
    GNU Wget 1.10 The non-interactive download utility Updated for Wget 1.10, Apr 2005 by Hrvoje Nikˇsi´cand the developers Copyright c 1996–2005, Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License” and “GNU Free Documentation License”, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. Chapter 1: Overview 1 1 Overview GNU Wget is a free utility for non-interactive download of files from the Web. It supports http, https, and ftp protocols, as well as retrieval through http proxies. This chapter is a partial overview of Wget’s features. • Wget is non-interactive, meaning that it can work in the background, while the user is not logged on. This allows you to start a retrieval and disconnect from the system, letting Wget finish the work. By contrast, most of the Web browsers require constant user’s presence, which can be a great hindrance when transferring a lot of data. • Wget can follow links in html and xhtml pages and create local versions of remote web sites, fully recreating the directory structure of the original site. This is sometimes referred to as “recursive downloading.” While doing that, Wget respects the Robot Exclusion Standard (‘/robots.txt’). Wget can be instructed to convert the links in downloaded html files to the local files for offline viewing.
    [Show full text]
  • Emacs Speaks Statistics (ESS): a Multi-Platform, Multi-Package Intelligent Environment for Statistical Analysis
    Emacs Speaks Statistics (ESS): A multi-platform, multi-package intelligent environment for statistical analysis A.J. Rossini Richard M. Heiberger Rodney A. Sparapani Martin Machler¨ Kurt Hornik ∗ Date: 2003/10/22 17:34:04 Revision: 1.255 Abstract Computer programming is an important component of statistics research and data analysis. This skill is necessary for using sophisticated statistical packages as well as for writing custom software for data analysis. Emacs Speaks Statistics (ESS) provides an intelligent and consistent interface between the user and software. ESS interfaces with SAS, S-PLUS, R, and other statistics packages under the Unix, Microsoft Windows, and Apple Mac operating systems. ESS extends the Emacs text editor and uses its many features to streamline the creation and use of statistical software. ESS understands the syntax for each data analysis language it works with and provides consistent display and editing features across packages. ESS assists in the interactive or batch execution by the statistics packages of statements written in their languages. Some statistics packages can be run as a subprocess of Emacs, allowing the user to work directly from the editor and thereby retain a consistent and constant look- and-feel. We discuss how ESS works and how it increases statistical programming efficiency. Keywords: Data Analysis, Programming, S, SAS, S-PLUS, R, XLISPSTAT,STATA, BUGS, Open Source Software, Cross-platform User Interface. ∗A.J. Rossini is Research Assistant Professor in the Department of Biostatistics, University of Washington and Joint Assis- tant Member at the Fred Hutchinson Cancer Research Center, Seattle, WA, USA mailto:[email protected]; Richard M.
    [Show full text]
  • 1 What Is Gimp? 3 2 Default Short Cuts and Dynamic Keybinding 9
    GUM The Gimp User Manual version 1.0.0 Karin Kylander & Olof S Kylander legalities Legalities The Gimp user manual may be reproduced and distributed, subject to the fol- lowing conditions: Copyright © 1997 1998 by Karin Kylander Copyright © 1998 by Olof S Kylander E-mail: [email protected] (summer 98 [email protected]) The Gimp User Manual is an open document; you may reproduce it under the terms of the Graphic Documentation Project Copying Licence (aka GDPL) as published by Frozenriver. This document is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANT- ABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the Graphic Documentation Project Copying License for more details. GRAPHIC DOCUMENTATION PROJECT COPYING LICENSE The following copyright license applies to all works by the Graphic Docu- mentation Project. Please read the license carefully---it is similar to the GNU General Public License, but there are several conditions in it that differ from what you may be used to. The Graphic Documentation Project manuals may be reproduced and distrib- uted in whole, subject to the following conditions: The Gimp User Manual Page i Legalities All Graphic Documentation Project manuals are copyrighted by their respective authors. THEY ARE NOT IN THE PUBLIC DOMAIN. • The copyright notice above and this permission notice must be preserved complete. • All work done under the Graphic Documentation Project Copying License must be available in source code for anyone who wants to obtain it. The source code for a work means the preferred form of the work for making modifications to it.
    [Show full text]
  • Miktex Manual Revision 2.0 (Miktex 2.0) December 2000
    MiKTEX Manual Revision 2.0 (MiKTEX 2.0) December 2000 Christian Schenk <[email protected]> Copyright c 2000 Christian Schenk Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Chapter 1: What is MiKTEX? 1 1 What is MiKTEX? 1.1 MiKTEX Features MiKTEX is a TEX distribution for Windows (95/98/NT/2000). Its main features include: • Native Windows implementation with support for long file names. • On-the-fly generation of missing fonts. • TDS (TEX directory structure) compliant. • Open Source. • Advanced TEX compiler features: -TEX can insert source file information (aka source specials) into the DVI file. This feature improves Editor/Previewer interaction. -TEX is able to read compressed (gzipped) input files. - The input encoding can be changed via TCX tables. • Previewer features: - Supports graphics (PostScript, BMP, WMF, TPIC, . .) - Supports colored text (through color specials) - Supports PostScript fonts - Supports TrueType fonts - Understands HyperTEX(html:) specials - Understands source (src:) specials - Customizable magnifying glasses • MiKTEX is network friendly: - integrates into a heterogeneous TEX environment - supports UNC file names - supports multiple TEXMF directory trees - uses a file name database for efficient file access - Setup Wizard can be run unattended The MiKTEX distribution consists of the following components: • TEX: The traditional TEX compiler.
    [Show full text]
  • Tugboat, Volume 33 (2012), No. 1 53 TEX on Windows: Miktex Or TEX Live? Joseph Wright on Windows, There Are Two Actively-Develop
    TUGboat, Volume 33 (2012), No. 1 53 TEX on Windows: MiKTEX or TEX Live? A reminder that MiKTEX and TEX Live are not the only choices. W32TEX (Kakuto, 2012) is popular Joseph Wright in the far east. As well as being a TEX system in On Windows, there are two actively-developed free its own right, it is the source of the Windows binar- TEX systems with similar coverage: MiKTEX (Schenk, ies for TEX Live, and TEX Live acquires more CJK 2011) and TEX Live (TEX Users Group, 2011). The support from it every year. For users focussed on good news is that there is a lot of similarity between ConTEXt, ConTEXt standalone (Pragma ADE, 2012) the two systems, so for most users both systems is probably the best way to go (it uses the W32TEX are equally usable, and (LA)TEX documents are port- binaries on Windows). There are also the commer- able between them. However, there are differences cial options, for example BaKoMa TEX (BaKoMa and depending on what you need these might be Soft., 2011) or PCTEX (Personal TEX, Inc., 2011). important. However, for most users it comes down to a choice between the ‘big two’. • The default settings install everything for TEX Live, but only a minimal set of packages for References MiKT X. MiKT X will then install extra pack- E E BaKoMa Soft. “BaKoMa T X 9.77”. ages ‘on the fly’, while T X Live does not (there E E http://www.bakoma-tex.com/, 2011. is a package to do that in TEX Live, but it is aimed at GNU/Linux users).
    [Show full text]
  • Name Synopsis Description Options
    GPGTAR(1) GNU Privacy Guard 2.2 GPGTAR(1) NAME gpgtar −Encrypt or sign files into an archive SYNOPSIS gpgtar [options] filename1 [ filename2, ... ] directory1 [ directory2, ... ] DESCRIPTION gpgtar encrypts or signs files into an archive.Itisangpg-ized tar using the same format as used by PGP’s PGP Zip. OPTIONS gpgtar understands these options: --create Put givenfiles and directories into a vanilla ‘‘ustar’’archive. --extract Extract all files from a vanilla ‘‘ustar’’archive. --encrypt -e Encrypt givenfiles and directories into an archive.This option may be combined with option --symmetric for an archive that may be decrypted via a secret key orapassphrase. --decrypt -d Extract all files from an encrypted archive. --sign -s Makeasigned archive from the givenfiles and directories. This can be combined with option --encrypt to create a signed and then encrypted archive. --list-archive -t List the contents of the specified archive. --symmetric -c Encrypt with a symmetric cipher using a passphrase. The default symmetric cipher used is AES-128, but may be chosen with the --cipher-algo option to gpg. --recipient user -r user Encrypt for user id user.For details see gpg. --local-user user -u user Use user as the key tosign with. Fordetails see gpg. --output file -o file Write the archive tothe specified file file. --verbose -v Enable extra informational output. GnuPG 2.2.12 2018-12-11 1 GPGTAR(1) GNU Privacy Guard 2.2 GPGTAR(1) --quiet -q Trytobeasquiet as possible. --skip-crypto Skip all crypto operations and create or extract vanilla ‘‘ustar’’archives. --dry-run Do not actually output the extracted files.
    [Show full text]
  • With Yocto/Openembedded
    PORTING NEW CODE TO RISC-V WITH YOCTO/OPENEMBEDDED Martin Maas ([email protected]) 1st RISC-V Workshop, January 15, 2015 Monterey, CA WHY WE NEED A LINUX DISTRIBUTION • To build an application for RISC-V, you need to: – Download and build the RISC-V toolchain + Linux – Download, patch and build application + dependencies – Create an image and run it in QEMU or on hardware • Problems with this approach: – Error-prone: Easy to corrupt FS or get a step wrong – Reproducibility: Others can’t easily reuse your work – Rigidity: If a dependency changes, need to do it all over • We need a Linux distribution! – Automatic build process with dependency tracking – Ability to distribute binary packages and SDKs 2 RISCV-POKY: A PORT OF THE YOCTO PROJECT • We ported the Yocto Project – Official Linux Foundation Workgroup, supported by a large number of industry partners – Part I: Collection of hundreds of recipes (scripts that describe how to build packages for different platforms), shared with OpenEmbedded project – Part II: Bitbake, a parallel build system that takes recipes and fetches, patches, cross-compiles and produces packages (RPM/DEB), images, SDKs, etc. • Focus on build process and customizability 3 GETTING STARTED WITH RISCV-POKY • Let’s build a full Linux system including the GCC toolchain, Linux, QEMU + a large set of packages (including bash, ssh, python, perl, apt, wget,…) • Step I: Clone riscv-poky: git clone [email protected]:ucb-bar/riscv-poky.git • Step II: Set up the build system: source oe-init-build-env • Step III: Build an image (may
    [Show full text]
  • Replacing PGP 2.X with Gnupg
    Replacing PGP 2.x with GnuPG This article is based on an earlier PGP 2.x/GnuPG compatability guide (http://www.toehold.com/~kyle/pgp- compat.html) written by Kyle Hasselbacher (<[email protected]>). Mike Ashley (<[email protected]>) edited and expanded it. Michael Fischer v. Mollard (<[email protected]>) transformed the HTML source to Doc- Book SGML and also expanded it further. Some of the details described here came from the gnupg-devel and gnupg-user mailing lists. The workaround for both signing with and encrypting to an RSA key were taken from Gero Treuner’s compatability script (http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/changes.html). Please direct questions, bug reports, or suggesstions to the maintainer, Mike Ashley. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Introduction This document describes how to communicate with people still using old versions of PGP 2.x GnuPG can be used as a nearly complete replacement for PGP 2.x. You may encrypt and decrypt PGP 2.x messages using imported old keys, but you cannot generate PGP 2.x keys. This document demonstrates how to extend the standard distribution of GnuPG to support PGP 2.x keys as well as what options must be used to ensure inter- operation with PGP 2.x users.
    [Show full text]
  • A User's Guide to the Lout Document Formatting System
    A User’s Guide to the Lout Document Formatting System Jeffrey H. Kingston Version 3.40 June 2013 Copyright 1991, 2013 Jeffrey H. Kingston, School of Information Technologies, The University of Sydney 2006, Australia. ISBN 0 86758 9515. Preface This User’s Guide brings together in one document everything needed for the day-to-day use of Version 3 of the Lout document formatting system. There are three other documents describing Lout: the Expert’s Guide [5], which you need if you want to add new features to Lout; a journal paper on the design and implementation of Lout [3]; and a set of overhead transparencies [4]that cover much the same ground as this Guide. These documents are all distributed with the software. Lout is distributed free of charge under the GNU Public License. The primary source is ftp://ftp.it.usyd.edu.au/jeff/lout containing a gzipped tar file of the current version, and various other things including a PostScript version of this guide. The distribution contains source code, libraries,documentation, license, and installation instructions. A mailing list has been set up for discussion of all topics related to Lout. To subscribe (or unsubscribe), visit http://lists.nongnu.org/mailman/listinfo/lout-users After subscribing, to post an item send email to [email protected]; it will be forwarded to all subscribers via email. There is also a web site at http://savannah.nongnu.org/projects/lout. Lout began in 1984 as a research project into the design of a high-level language for document formatting.
    [Show full text]
  • Luametatex Reference Manual
    LuaMetaTEX Reference Manual February 2021 Version 2.08.16 LuaMetaTEX Reference Manual copyright : LuaTEX development team :CONTEXT development team more info : www.luatex.org : contextgarden.net version : February 20, 2021 Contents Introduction 11 1 The internals 15 2 Differences with LUATEX 19 3 The original engines 25 3.1 The merged engines 25 3.1.1 The rationale 25 3.1.2 Changes from TEX 3.1415926... 25 3.1.3 Changes from 휀-TEX 2.2 26 3.1.4 Changes from PDFTEX 1.40 27 3.1.5 Changes from ALEPH RC4 28 3.1.6 Changes from standard WEB2C 28 3.2 Implementation notes 29 3.2.1 Memory allocation 29 3.2.2 Sparse arrays 29 3.2.3 Simple single-character csnames 29 3.2.4 Binary file reading 29 3.2.5 Tabs and spaces 30 3.2.6 Logging 30 3.2.7 Parsing 30 4 Using LUAMETATEX 33 4.1 Initialization 33 4.1.1 LUAMETATEX as a LUA interpreter 33 4.1.2 Other commandline processing 33 4.2 LUA behaviour 35 4.2.1 The LUA version 35 4.2.2 Locales 35 4.3 LUA modules 35 4.4 Testing 36 5 Basic TEX enhancements 37 5.1 Introduction 37 5.1.1 Primitive behaviour 37 5.1.2 Version information 37 5.2 UNICODE text support 38 5.2.1 Extended ranges 38 5.2.2 \Uchar 39 5.2.3 Extended tables 39 1 5.3 Attributes 41 5.3.1 Nodes 41 5.3.2 Attribute registers 42 5.3.3 Box attributes 42 5.4 LUA related primitives 44 5.4.1 \directlua 44 5.4.2 \luaescapestring 45 5.4.3 \luafunction, \luafunctioncall and \luadef 45 5.4.4 \luabytecode and \luabytecodecall 46 5.5 Catcode tables 47 5.5.1 Catcodes 47 5.5.2 \catcodetable 47 5.5.3 \initcatcodetable 47 5.5.4 \savecatcodetable 48 5.6 Tokens, commands
    [Show full text]