On Mon, Nov 10, 2008 at 6:49 PM, Hans Hagen <[EMAIL PROTECTED]> wrote:
> Aditya Mahajan wrote:
>
> >> \starttext
> >> \typefile{test-aditya-001.tex}
> >> \stoptext
> >
> > Ah, this also works here. The error only shows if the file does not have
Aditya Mahajan wrote:
>> \starttext
>> \typefile{test-aditya-001.tex}
>> \stoptext
>
> Ah, this also works here. The error only shows if the file does not have
> an extension.
this is fixed (hack, awaiting a proper split of supp-fil
On Thu, Oct 30, 2008 at 8:23 PM, Aditya Mahajan <[EMAIL PROTECTED]> wrote:
> On Thu, 30 Oct 2008, luigi scarso wrote:
>
> > On Thu, Oct 30, 2008 at 8:09 PM, Aditya Mahajan <[EMAIL PROTECTED]>
> wrote:
> >
> >> Hi,
> >>
> >>
On Thu, 30 Oct 2008, luigi scarso wrote:
> On Thu, Oct 30, 2008 at 8:09 PM, Aditya Mahajan <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> Something is wrong with \typefile in latest context in MKIV.
>>
>> \starttext
>> \typefile{somefile}
>
On Thu, Oct 30, 2008 at 8:09 PM, Aditya Mahajan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Something is wrong with \typefile in latest context in MKIV.
>
> \starttext
> \typefile{somefile}
> \stoptext
>
> (the file 'somefile' should exist)
>
> giv
Hi,
Something is wrong with \typefile in latest context in MKIV.
\starttext
\typefile{somefile}
\stoptext
(the file 'somefile' should exist)
gives
! Undefined control sequence.
\filepath
\pathplusfile #1#2->#1
\f!pathseparator #2
\mktypefileverbatim .
On Wednesday 19 July 2006 11:21, Taco Hoekwater wrote:
> John R. Culleton wrote:
> > The document compiles fine and displays fine in xpdf or kpdf
> > (Linux).
> > But Acrobat Reader 7.0 (Linux) comes up with the message "there was a
> > problem with this document" and displays two blank pages inst
John R. Culleton wrote:
> The document compiles fine and displays fine in xpdf or kpdf
> (Linux).
> But Acrobat Reader 7.0 (Linux) comes up with the message "there was a
> problem with this document" and displays two blank pages instead.
> It will however display the rest of the document if t
I use the lines:
\typefile {samp.tex}{samp.tex}
\page[yes]
\stoptext % For debugging purposes
The file samp.tex contains ascii tex from the sample files
knuth, zapf and tufte, concluded by the single tag \bye.
The document compiles fine and displays fine in xpdf or kpdf
(Linux).
But Acrobat
On Sun, 30 Apr 2006 18:59:53 +0200, Hans Hagen <[EMAIL PROTECTED]> wrote:
> nico wrote:
>> On Sun, 30 Apr 2006 15:22:49 +0200, Hans Hagen <[EMAIL PROTECTED]> wrote:
>>
>>
> what version of context do you run? i though that i added support for
> that some time ago
>
Version 2006.04
t;> not
>>>> sure to understand correctly the code.
>>>>
>>>>
>>> \tracefilestrue
>>>
>>>
>> Hm, verbatim seems not using the file interface: there's no trace about
>> file found or not related to typefile. Another thi
;>>
>>> \dodotypefile checks where the file is, but a following call to
>>> \makelocreadfilename seems to set improperly \readfilename, but I'm not
>>> sure to understand correctly the code.
>>>
>>>
>> \tracefilestrue
>>
>>
following call to
>> \makelocreadfilename seems to set improperly \readfilename, but I'm not
>> sure to understand correctly the code.
>>
> \tracefilestrue
>
Hm, verbatim seems not using the file interface: there's no trace about
file found or not related to
nico wrote:
> On Sun, 30 Apr 2006 12:33:20 +0200, Hans Hagen <[EMAIL PROTECTED]> wrote:
>
>
>> nico wrote:
>>
>>> Hello,
>>>
>>> \typefile does not output a file not in the current directory but
>>> available from a path define
On Sun, 30 Apr 2006 12:33:20 +0200, Hans Hagen <[EMAIL PROTECTED]> wrote:
> nico wrote:
>> Hello,
>>
>> \typefile does not output a file not in the current directory but
>> available from a path defined by \usepath. It sounds like a bug since
>> the
>&
nico wrote:
> Hello,
>
> \typefile does not output a file not in the current directory but
> available from a path defined by \usepath. It sounds like a bug since the
> file is actually found; if not, a message telling that the file does not
> exist would be printed.
>
Hello,
\typefile does not output a file not in the current directory but
available from a path defined by \usepath. It sounds like a bug since the
file is actually found; if not, a message telling that the file does not
exist would be printed.
Example:
\usepath[/path/to/my/file]
\typefile
Thomas A. Schmitz wrote:
> Yes, same here, the file is missing, so generating the formats runs
> into trouble:
>
> loading : MetaPost Graphics / Stand Alone Graphics
> ) (/usr/local/teTeX/share/texmf.local/tex/context/base/core-pos.tex
> loading : Context Positioning Support
> )
>
Yes, same here, the file is missing, so generating the formats runs
into trouble:
loading : MetaPost Graphics / Stand Alone Graphics
) (/usr/local/teTeX/share/texmf.local/tex/context/base/core-pos.tex
loading : Context Positioning Support
)
! I can't find file `core-bar.tex'.
l.2
On Fri, 24 Mar 2006 22:50:09 +0100, Hans Hagen <[EMAIL PROTECTED]> wrote:
> it's worse, more is wrong
>
> i'm uploading a fixed version; for the source readers:
>
> - page-str.tex
> - page-plg.tex
> - core-bar.tex
> - m-streams.tex
>
> are added; streams are rather experimental but promissing
Str
Peter Rolf wrote:
> Peter Rolf wrote:
>
>
>> \doifinset{\\currenttyping\c!option}{\v!commands,\v!slanted,\v!normal}
>>^^
>>
> looks like a bad placed marker :)
>
> The problem is the double backslash (should be
>
> ..{\currenttyping\c!option}..
>
it's worse, more is wro
Peter Rolf wrote:
> \doifinset{\\currenttyping\c!option}{\v!commands,\v!slanted,\v!normal}
>^^
looks like a bad placed marker :)
The problem is the double backslash (should be
..{\currenttyping\c!option}..
Peter
___
ntg-context mail
atimline
> \fi \fi \fi \fi
> \handlever...
>
> \processfileverbatim ...expandafter \readline \fi
> \closein
> \verbatiminput \e...
> ...
> l.39 \typefile{/dev/shm/tmp_0.9.xtls
ileverbatim ...expandafter \readline \fi
\closein
\verbatiminput \e...
...
l.39 \typefile{/dev/shm/tmp_0.9.xtls}
-
Tobias
For my current e-book project I use \typefile to import some TeX
files as examples. The syntax is color coded which is very
useful.
Unfortunately on my screen at least the % character is in yellow so faint
as to be unreadable. So I dug into the source code and discovered
that the name for this
101 - 125 of 125 matches
Mail list logo
