ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: Peter Rolf <indiego@gmx.net>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xml and lua again
Date: Sun, 23 Oct 2011 16:37:56 +0200	[thread overview]
Message-ID: <4EA426C4.1000909@uni-bonn.de> (raw)
In-Reply-To: <4EA41EF4.6090704@gmx.net>

Hi Peter,

thanks for your reply, and I'll keep the bit about goat milk in mind :-).


> "frame=" .. tostring(framestate)

It has the advantage of making the example compile. It has the drawback 
of not doing anything :-)

> seems to work. Anyhow, if you are planning to do some more complex
> stuff, you should separate the lua from the tex code.
>
> The advantages are
> - no catcode limitations
>    Then you can use nice stuff like
>    string.format("frame=%s",framestate)
> - in case of lua errors you get the real line number
> - lua syntax check is possible
>
> Load the lua code at the beginning of your tex file with
>
> \registerctxluafile{filename_without_suffix}{version number or empty}
>
> One last but important tip: if you get lua errors like 'undefined
> whatever', check your lua file with 'luatexc -p foo.lua' (lua compiler).
> A single syntax error in the lua file and all of its content is ignored!
> Can be quite frustrating to find the error cause, if all of your lua
> code is undefined right from the beginning.

OK, that sounds like very good advice - I'll see if I can manage to 
apply this for xml style sheets.

Thanks a lot, and best wishes

Thomas
___________________________________________________________________________________
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-10-23 14:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22 16:46 Thomas A. Schmitz
2011-10-23 14:04 ` Peter Rolf
2011-10-23 14:37   ` Thomas A. Schmitz [this message]
2011-10-23 15:25     ` Peter Rolf
2011-10-23 18:15 ` Peter Rolf
2011-10-24 10:17 ` Hans Hagen
2011-10-24 12:18   ` Thomas A. Schmitz
2011-10-24 12:26     ` Hans Hagen
2011-10-24 17:00       ` Thomas A. Schmitz
2011-10-24 18:48         ` Hans Hagen
2011-10-25  9:43           ` Thomas A. Schmitz
2011-10-25 10:10             ` Wolfgang Schuster
2011-10-25 10:17             ` Hans Hagen
2011-10-25 10:27               ` Thomas A. Schmitz
2011-10-27  9:23                 ` Thomas A. Schmitz
2011-10-27  9:53                   ` Wolfgang Schuster
2011-10-27 10:32                     ` Thomas A. Schmitz
2011-10-27 11:05                       ` Hans Hagen
2011-10-28  6:23                         ` Thomas A. Schmitz
2011-10-28  6:37                           ` luigi scarso
2011-10-28  6:43                             ` luigi scarso
2011-10-28  6:44                           ` Patrick Gundlach
2011-10-28  6:55                             ` Thomas A. Schmitz
2011-10-28  8:35                               ` Wolfgang Schuster
2011-10-28  8:59                                 ` Hans Hagen
2011-10-28  8:56                               ` Hans Hagen
2011-10-28 10:48                                 ` Thomas A. Schmitz
2011-10-28 11:23                                 ` luigi scarso
2011-10-28 11:42                                   ` 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=4EA426C4.1000909@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --cc=indiego@gmx.net \
    --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).