ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andre Caldas <andre.em.caldas@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Current source directory.
Date: Fri, 28 Sep 2012 09:34:34 -0300	[thread overview]
Message-ID: <CADVh14UW=FiVWLWEzLC8QtMp3jQ-=EbGjZHEWB6C9GV=9njqvA@mail.gmail.com> (raw)
In-Reply-To: <CAF=dkzzKv9wPd+QTuAfDDOiFWhsnh=zz5uFWYBJS2d=wS8itKQ@mail.gmail.com>

Dear Sietse,

Thanks a lot!!!

> Finally found it, after lots of trial-and-erroring through
> likely-looking table names in file-job.lua: the stack of input files
> is kept in resolvers.inputstack.

I don't program any "lua". But I was taking a look at "file-job.lua"
myself. I have a lot to learn!! :-)


> Assuming (absolute path of invocation
> dir) + (path of file relative to invocation dir) = the desired path,

I don't mind this assumption.
Actually, I don't mind having a path relative to the currdir.


> the following should work.
>
>     \cldcontext{
>         environment.runpath .. '/'  ..
>             file.pathpart(resolvers.inputstack[#resolvers.inputstack])
>     }

I will try this now.


> You may or may not want to parse out any ./ and ../ components.

No, I don't need that.

> (If you do: helpful filename manipulation functions (such as
> file.pathpart, indeed) may be found in l-file.lua.)

Thanks for the tip. Might be useful someday.


> Hope this helps,

It does! :-)
Although, I think there should be a "luatex" command for this. That
is, something not related to ConTeXt.


Thank you,
André Caldas.
___________________________________________________________________________________
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:[~2012-09-28 12:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 20:28 Andre Caldas
2012-09-24 21:37 ` Peter Münster
2012-09-24 21:43   ` Peter Münster
2012-09-27 22:38   ` Andre Caldas
2012-09-28  1:15     ` Sietse Brouwer
2012-09-28 12:34       ` Andre Caldas [this message]
2012-09-28 12:46         ` Hans Hagen
2012-09-28 19:17       ` Andre Caldas
2012-09-28 19:38         ` Sietse Brouwer
2012-09-28 19:53           ` Andre Caldas
2012-09-28 21:38             ` Sietse Brouwer
2012-09-28 21:56               ` Andre Caldas
2012-09-28 22:42                 ` Hans Hagen
2012-09-29  9:38                 ` Sietse Brouwer
2012-09-29 13:36                   ` Andre Caldas

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='CADVh14UW=FiVWLWEzLC8QtMp3jQ-=EbGjZHEWB6C9GV=9njqvA@mail.gmail.com' \
    --to=andre.em.caldas@gmail.com \
    --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).