From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: filename
Date: Wed, 23 Jun 2004 18:09:11 +0200 [thread overview]
Message-ID: <40D9AB27.4000200@wxs.nl> (raw)
In-Reply-To: <m2zn6uh5fm.fsf@levana.de>
Patrick Gundlach wrote:
>Hello Hans,
>
>
>
>>>Well, I don't think you can do this. You can only get the name of the
>>>main TeX file by using \jobname, but thats all. (Hopefully I didn't
>>>miss some secret.) Different approach: put some info in your file with
>>>a macro like \define\thisfile{/path/to/test.tex}. Or you can put some RCS
>>>information in your file for example.
>>>
>>>
>>>
>>of course you missed a few secret:
>>
>>\inputfilename
>>\outputfilename
>>\jobfilesuffix
>>
>>
>
>
>
>>don't look at the code, some catcode mess is involved
>>
>>
>
>OK, I didn't. But the above still gives me the name of the main file
>only:
>
>
there is also \currentfile
>\starttext
>\startlines
>\inputfilename
>\outputfilename
>\jobfilesuffix
>\stoplines
>\input included
>\readfile{included}{}{}
>\stoptext
>
>and in included.tex:
>Included file:
>\startlines
>\inputfilename
>\outputfilename
>\jobfilesuffix
>\stoplines
>
>gives me:
>
>test.tex
>test
>tex
>
>Included file:
>test.tex
>test
>tex
>
>Included file:
>test.tex
>test
>tex
>
>
>Patrick
>
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2004-06-23 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 13:51 filename Thomas Lohmann
2004-06-21 15:44 ` filename Patrick Gundlach
2004-06-21 16:01 ` filename Hans Hagen
2004-06-22 11:42 ` Thomas Lohmann
2004-06-23 11:36 ` filename Patrick Gundlach
2004-06-23 16:09 ` Hans Hagen [this message]
2004-06-23 16:37 ` filename Patrick Gundlach
2004-06-24 7:54 ` filename Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40D9AB27.4000200@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).