From: Aditya Mahajan <adityam@umich.edu>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Stange behavior of \startluacode
Date: Tue, 5 Oct 2010 19:36:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1010051936000.7795@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4CA85BC7.2030300@wxs.nl>
On Sun, 3 Oct 2010, Hans Hagen wrote:
> On 3-10-2010 1:46, Aditya Mahajan wrote:
>> Hi,
>>
>> The following snippet
>>
>> \startluacode
>> -- \undefined why should a comment matter
>> a = 10
>> \stopluacode
>>
>> fails with
>>
>> system > error on line 4 in file bug.tex: Undefined control sequence ...
>> -- \undefined
>> why should a comment matt a = 10
>> \dodostartluacode ...and \directlua \zerocount {#1
>> }}
>> l.4 \stopluacode
>>
>>
>> Bug or limitation?
>
> feature ... the content gets expanded
>
> texnically I could catch comments but it's not worth the effort (and
> slowdown)
OK. I documented this on the wiki.
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-10-05 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 23:46 Aditya Mahajan
2010-10-03 6:30 ` Wolfgang Schuster
2010-10-03 6:33 ` Wolfgang Schuster
2010-10-04 7:17 ` Procházka Lukáš Ing. - Pontex s. r. o.
2010-10-04 7:19 ` Procházka Lukáš Ing. - Pontex s. r. o.
2010-10-04 8:00 ` Hans Hagen
2010-10-03 8:28 ` luigi scarso
2010-10-03 9:02 ` Wolfgang Schuster
2010-10-03 9:12 ` Wolfgang Schuster
2010-10-03 10:32 ` Hans Hagen
2010-10-05 23:36 ` Aditya Mahajan [this message]
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.1010051936000.7795@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).