From: "Lance Larsen" <lance.c.larsen@gmail.com>
To: <ntg-context@ntg.nl>
Subject: Re: How to hack the lua files
Date: Fri, 7 Jun 2013 07:13:28 -0600 [thread overview]
Message-ID: <51b1dc7a.caef440a.3a4a.ffffea86@mx.google.com> (raw)
In-Reply-To: <mailman.1195.1370589979.2084.ntg-context@ntg.nl>
Hans,
Your reply below was very helpful. I looked at the context command line
options and saw 'make'. After running this, the code changes took effect.
Thankyou.
I could still use help in identifying where equation numbers are defined in
the code so that I can add a tracker. Do you have a suggestion of which
function (or at least lua file) I should look in for this?
I am also curious how hooks are defined, so that I can identify them in the
code and see if there is one that would meek my purpose - also where the
hook scripts are placed so that context can find them.
Thanks again for the reply which got me over the first hurdle.
-Lance
------------------------------
Message: 4
Date: Fri, 07 Jun 2013 09:25:36 +0200
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] How to hack the lua files
Message-ID: <51B18AF0.5010206@wxs.nl>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 6/7/2013 1:20 AM, Lance Larsen wrote:
> I have a version of context standalone installed, and I am trying to
> add some functionality I need to strc-ref.lua. As a simple test to see
> if modifying the file was working, I enabled the
> ?structures.referencing.identifying? tracker and verified that I was
> getting messages from this tracker in the log. I then modified the log
> statement in strc-ref.lua and processed the document again. The
> changes I made to the lua file did not seem to be active. I verified
> that there is only one log statement that matches the output I am
> seeing. Why would my lua code change not be active? Is the lua code
> cached somehow? (I am running this from windows if that matters).
>
> The code I modified is under the path:
>
> context\tex\texmf-context\tex\context\base\ strc-ref.lua
if you patch files that way you need to remake the format file
I don't know what you patch, but changing something in a core file is no
guarantee for the future. It's not a problem to add functionality (lots of
hooks for that) but best do that in a local module that gets loaded at
runtime then.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-06-07 13:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1195.1370589979.2084.ntg-context@ntg.nl>
2013-06-07 13:00 ` Lance Larsen
2013-06-07 13:03 ` luigi scarso
2013-06-07 15:27 ` Sietse Brouwer
2013-06-07 15:36 ` Hans Hagen
2013-06-07 15:36 ` Wolfgang Schuster
2013-06-07 15:42 ` luigi scarso
2013-06-07 15:49 ` Sietse Brouwer
2013-06-07 16:21 ` luigi scarso
2013-06-07 13:17 ` luigi scarso
2013-06-07 13:48 ` Wolfgang Schuster
2013-06-07 13:13 ` Lance Larsen [this message]
2013-06-07 13:48 ` Hans Hagen
[not found] <mailman.1201.1370610850.2084.ntg-context@ntg.nl>
2013-06-07 14:01 ` Lance Larsen
2013-06-07 14:10 ` Hans Hagen
2013-06-06 23:20 Lance Larsen
2013-06-07 7:25 ` 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=51b1dc7a.caef440a.3a4a.ffffea86@mx.google.com \
--to=lance.c.larsen@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).