From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Malicious little bugger
Date: Mon, 03 Jul 2006 08:26:25 +0200 [thread overview]
Message-ID: <44A8B891.7090903@elvenkind.com> (raw)
In-Reply-To: <7FA1F8C5-D8CA-4B90-AC50-A866B0E1127F@cox.net>
David Arnold wrote:
> Sanjoy,
>
> Of course. Thanks.
>
> But how about an example in latex or tex where a function eats a
> brace and crashes, as what happens with this context code:
>
> \placeformula[-]
> \startformula
> [9,\infty)=\{x:\,x\ge 9\}
> \stopformula
>
> I know I've seen this in Latex before, but I can't remember where.
LaTeX's newline -- \\ -- command is infamous for this, esp. because
non-expert users tend to forget it even has an optional argument.
Greetings, Taco
prev parent reply other threads:[~2006-07-03 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 4:36 David Arnold
2006-07-02 11:23 ` Hans Hagen
2006-07-02 18:15 ` Peter Münster
2006-07-02 19:01 ` Taco Hoekwater
2006-07-02 19:53 ` Hans Hagen
2006-07-02 20:25 ` Peter Münster
2006-07-02 23:35 ` David Arnold
2006-07-03 2:29 ` Sanjoy Mahajan
2006-07-03 2:32 ` David Arnold
2006-07-03 5:17 ` Aditya Mahajan
2006-07-03 8:43 ` Hans Hagen
2006-07-03 6:26 ` Taco Hoekwater [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=44A8B891.7090903@elvenkind.com \
--to=taco@elvenkind.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).