ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Use date of the tex file in the document
Date: Thu, 24 Mar 2011 12:12:30 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.01.1103241210290.7470@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <AANLkTikyW3FFrOqfSyJ+TzkMnubTD24tFkGxPFe5doFD@mail.gmail.com>

On Thu, 24 Mar 2011, Cecil Westerhof wrote:

> 2011/3/24 Marco <netuse@lavabit.com>
>
>> On 2011-03-24 Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de> wrote:
>>
>> This should also work:
>>
>> \starttext
>>
>> \startluacode
>>  function modification_date (file)
>>    local f = file
>>    local attr = lfs.attributes (f)
>>    assert (type(attr) == "table")
>>    if attr.mode ~= "directory" then
>>      return os.date("%Y-%m-%d %H:%M",attr.modification)
>>    end
>>  end
>> \stopluacode
>>
>> \unexpanded\def\getdate{%
>>  \ctxlua{context(modification_date ("\jobname.tex"))}%
>> }
>>
>> \getdate
>>
>> \stoptext
>>
>
> I would like to do something like the following:
>    \getdate would return os.date("%Y-%m-%d",attr.modification)
> and
>    \getdate{"long"} would return os.date("%Y-%m-%d
> %H:%M",attr.modification)
>
> I have looked at lua, but do not see how to do it. (Something else to
> learn.)

Untested:

\def\getdate%
   {\dosinglegroupempty\dogetdate}

\def\dogetdate#1%
    {context{modification_date("\jobname.tex", "#1")}}

and then in the lua code

function modification_date(file, format)
....
if format == "long" then
....
else
...
end

end

Aditya
___________________________________________________________________________________
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:[~2011-03-24 16:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24  9:26 Cecil Westerhof
2011-03-24 10:22 ` Philipp Gesang
2011-03-24 10:56   ` Cecil Westerhof
2011-03-24 11:00   ` Marco
2011-03-24 16:09     ` Cecil Westerhof
2011-03-24 16:12       ` Aditya Mahajan [this message]
2011-03-24 16:29         ` Cecil Westerhof
2011-03-24 16:33           ` Wolfgang Schuster
2011-03-24 17:15             ` Cecil Westerhof
2011-03-24 17:29               ` Philipp Gesang
2011-03-24 17:42                 ` Cecil Westerhof
2011-03-24 17:50                   ` Philipp Gesang
2011-03-24 20:41                     ` Cecil Westerhof
2011-03-24 23:08                   ` Cecil Westerhof
2011-03-24 23:30                     ` Hans Hagen
2011-03-25  0:33                       ` Philipp Gesang
2011-03-24 17:30               ` Marco
2011-03-24 18:35                 ` Hans Hagen
2011-03-24 17:42             ` Florian Wobbe
2011-03-24 17:47               ` Aditya Mahajan
2011-03-24 17:59                 ` Florian Wobbe
2011-03-24 20:49                   ` Aditya Mahajan
2011-03-24 21:43                     ` Florian Wobbe

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=alpine.LNX.2.01.1103241210290.7470@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).