From: "Frans Goddijn" <frans@goddijn.com>
Subject: Re: 'capacity exceeded' ConTeXt over Win2k
Date: Mon, 24 Sep 2001 17:35:48 +0200 [thread overview]
Message-ID: <001a01c1450e$b3e9fec0$6601a8c0@lap> (raw)
In-Reply-To: <1001340154.3baf3cfa206bd@imp.free.fr>
Can you also provide the .tex file causing the error? It looks like a
forgotten } somewhere.
Frans
----- Original Message -----
From: Michael Hallgren <m.hallgren@free.fr>
> > ! TeX capacity exceeded, sorry [number of strings=100].
> > <recently read> \endcsname
next prev parent reply other threads:[~2001-09-24 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 19:51 \type with spaces Johannes Huesing
2001-09-21 8:17 ` Hans Hagen
2001-09-22 6:37 ` Johannes Huesing
2001-09-22 18:34 ` Hans Hagen
2001-09-23 18:12 ` Johannes Huesing
2001-09-24 12:47 ` Michael Hallgren
2001-09-24 14:02 ` 'capacity exceeded' ConTeXt over Win2k -- Was: [Re: \type with spaces] Michael Hallgren
2001-09-24 15:35 ` Frans Goddijn [this message]
2001-09-24 18:54 ` 'capacity exceeded' ConTeXt over Win2k Michael Hallgren
2001-09-29 12:50 ` \type with spaces 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='001a01c1450e$b3e9fec0$6601a8c0@lap' \
--to=frans@goddijn.com \
/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).