From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: {{ double braces }}
Date: Tue, 12 Feb 2008 16:15:16 +0100 [thread overview]
Message-ID: <47B1B804.2020600@wxs.nl> (raw)
In-Reply-To: <3C90B1C8-F6D0-4313-A21A-B54141DBDC61@uni-bonn.de>
Thomas A. Schmitz wrote:
> Hi Aditya,
>
> now I need to apologize for being so slow to reply: thanks a lot, this
> looks really fascinating! I don't know how many things I've read on
> the web to understand if regexps can handle nested delimiters or not
> (I think the long and short of it was that on some mathematical
> principle it just isn't possible); there is some pretty obscure perl
> stuff that might be able to do it but is highly experimental. If gema
> really can do this, it should be a godsend for processing TeX files. I
> have it installed now on my OS X box (but couldn't build the gel
> binary) and am looking forward to experimenting with it.
lua's pattern matcher can hanle nested {} (syntax: %b{} and such)
more clever things can be done with lpeg, bla {bla\{bla} and such
if you're up to date you may try
mtxrun --script check sometexfile.tex
this is a (for the mooment simple) syntax checker i wrote a while ago
which shows the principles
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-02-12 15:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 14:45 Steffen Wolfrum
2008-01-21 15:02 ` Mikael Persson
2008-01-21 15:53 ` Steffen Wolfrum
2008-01-23 20:49 ` Peter Münster
2008-01-23 21:50 ` Peter Münster
2008-01-23 22:17 ` Thomas A. Schmitz
2008-01-23 23:19 ` Aditya Mahajan
2008-01-26 10:11 ` Thomas A. Schmitz
2008-02-06 7:01 ` Aditya Mahajan
2008-02-06 9:11 ` Steffen Wolfrum
2008-02-06 16:36 ` Aditya Mahajan
2008-02-06 19:20 ` Hans van der Meer
2008-02-06 20:01 ` Steffen Wolfrum
2008-02-06 20:16 ` Hans van der Meer
2008-02-06 20:17 ` Otared Kavian
2008-02-12 15:09 ` Thomas A. Schmitz
2008-02-12 15:15 ` Hans Hagen [this message]
2008-02-12 17:39 ` Aditya Mahajan
2008-02-13 8:39 ` Taco Hoekwater
2008-02-13 9:31 ` luigi scarso
2008-02-13 10:21 ` Taco Hoekwater
2008-02-13 10:38 ` luigi scarso
2008-01-26 10:52 ` Taco Hoekwater
2008-01-26 11:41 ` Taco Hoekwater
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=47B1B804.2020600@wxs.nl \
--to=pragma@wxs.nl \
--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).