From: Nikolai Weibull <mailing-lists.context-users@rawuncut.elitemail.org>
Subject: Re: unic-033.tex and unic-034.tex
Date: Fri, 10 Jun 2005 13:37:44 +0200 [thread overview]
Message-ID: <20050610113744.GB5061@puritan.bredbandsbolaget.se> (raw)
In-Reply-To: <42A61333.3010203@elvenkind.com>
Taco Hoekwater wrote:
> Nikolai Weibull wrote:
> > For some reason one needs to do the "\numexpr(x+1) \unknownchar \or
> > ..." trick for things to work. Why?,
> Braces do not end the \numexpr parsing engine, only \relax does
> that (or something that does not fit the syntax). So it is
> 'normal' to use
>
> \numexpr x+1\relax \unknownchar
>
> instead.
Ah, thanks for clarifying,
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
next prev parent reply other threads:[~2005-06-10 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 20:37 Nikolai Weibull
2005-06-07 21:35 ` Taco Hoekwater
2005-06-10 11:37 ` Nikolai Weibull [this message]
2005-06-10 22:19 ` Hans Hagen
2005-06-10 22:47 ` Nikolai Weibull
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=20050610113744.GB5061@puritan.bredbandsbolaget.se \
--to=mailing-lists.context-users@rawuncut.elitemail.org \
--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).