Difference between revisions of "Command/ReadFile"

From ConTeXt wiki
Jump to navigationJump to search
(Created page for \ReadFile)
 
 
Line 1: Line 1:
 
{{Reference
 
{{Reference
|name=ReadFile|attributes=
+
|name=ReadFile
 +
|attributes=
 
}}
 
}}
 +
 +
== [[Help:Reference|Syntax]] (autogenerated) ==
 +
<syntax>ReadFile</syntax>
  
 
== [[Help:Reference|Syntax]] ==
 
== [[Help:Reference|Syntax]] ==

Latest revision as of 16:26, 11 November 2019

\ReadFile

Syntax (autogenerated)


Syntax

\ReadFile {file}
file name of the file

Description

The command \ReadFile {filename} is replaced by the content of the text file filename, if it exists. If it does not exist, no error message is generated and the compile process continues.

When no file extension is specified, the extension .tex is assumed.

Similar to the case with project structure commands such as \environment, \ReadFile causes ConTeXt to look in ancestor directories for the specified file.

Example

We have a chapter 1 file, but no chapter 2 file:

% chapter-01.tex
\subject{Chapter 1}

This is the first chapter.

The book file attempts to incorporate both chapters, using \ReadFile{filename}:

% complete-book.tex
\starttext

% No extension specified, so .tex assumed
\ReadFile{chapter-01}
\ReadFile{chapter-02}

\stoptext

Compiling book.tex produces the following:

No error message is generated for the missing chapter 2, and the compilation completes successfully.

See also

  • \input: Similar to \ReadFile but the filename is not specified as an argument.
  • \readfile: Similar to \ReadFile with additional options when file is not found.
  • \getbuffer: Get back the "formatted" content of a buffer.
  • \typebuffer: Get back the content of a buffer as verbatim text.
  • \typefile: Print a file verbatim
  • \component and \environment for input commands with more descriptive names.
  • Dummy text for other ways to produce filler text

Help from ConTeXt-Mailinglist/Forum

All issues with: