ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <philipp.gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Simple question: how do I get the filename in the footer
Date: Sun, 20 Jan 2013 16:09:28 +0100	[thread overview]
Message-ID: <20130120150928.GC1285@phlegethon.router_intern> (raw)
In-Reply-To: <5CA35152-641F-41AE-A7BA-5427C6852CD4@rna.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1599 bytes --]

···<date: 2013-01-20, Sunday>···<from: Gerben Wierda>···

> On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
> 
> > Hi Gerben,
> > 
> > ···<date: 2013-01-20, Sunday>···<from: Gerben Wierda>···
> > 
> >> how do I get the filename (full path not needed) in the footer
> >> of my document? I want it there while writing the book and remove
> >> it in the final stages. I am using MKII (TeXLive 2011 still)
> > 
> > if the name of the main file suffices, then the TeX command
> > \jobname is what you are looking for.
> 
> Thanks but that is not the one. Because I use the standard project setup, and the job is always to typeset the file prd_book.tex, but I want the chapter file names (e.g. "chapter1.tex") in the footer.
> 
> So, prd_book contains:
> 
> \startbodymatter
>  \component chapter1
>  \component chapter2
>  \component chapter3
> \stopbodymatter
> 
> And I want "chapter1.tex" (maybe full path) in the footer.

If the component identifier matches the file name (e.g. if you
use the asterisk instead of a name), you can use
\currentcomponent. So the main file foo.tex would look like:

    \setuppagenumbering[location=]
    %% footer:                    main file->component file
    \setupfootertexts[pagenumber][{\jobname->\currentcomponent}]
    \startproduct *
      \input ward \page
      \component bar
    \stopproduct

And bar.tex:

    \startcomponent *
      \input knuth \page
    \stopcomponent

Hth
Philipp



-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2013-01-20 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-20 11:37 Gerben Wierda
2013-01-20 11:57 ` Philipp Gesang
2013-01-20 14:44   ` Gerben Wierda
2013-01-20 15:09     ` Philipp Gesang [this message]
2013-01-20 17:06       ` Gerben Wierda
2013-01-20 17:34         ` Wolfgang Schuster
2013-01-20 20:41           ` Gerben Wierda
2013-01-20 21:32             ` Aditya Mahajan
2013-01-22 20:36               ` Gerben Wierda

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=20130120150928.GC1285@phlegethon.router_intern \
    --to=philipp.gesang@alumni.uni-heidelberg.de \
    --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).