From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: unic-037
Date: Thu, 16 Feb 2006 19:38:10 +0100 [thread overview]
Message-ID: <43F4C692.4060705@elvenkind.com> (raw)
In-Reply-To: <fe8d59da0602161019r68a3b699t1efba912c39c1f32@mail.gmail.com>
luigi scarso wrote:
> 2) \ifcase\numexpr(#1+1)\or %% a trick to avoid #1=000
> seem to works ,
> \ifcase\numexpr(#1+0) %%
> no
> Why?
I am not sure what you want and what exactly doesn't work,
but it is better to use numexpr like this:
\ifcase \numexpr #1+0\relax
because the closing ) does not actually cause it to stop
scanning forward (it stops in the first case because the
\or cannot be part of \numexpr).
Cheers, Taco
next prev parent reply other threads:[~2006-02-16 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 9:10 unic-037 luigi scarso
2006-02-16 9:50 ` unic-037 Adam Lindsay
2006-02-16 10:18 ` unic-037 luigi scarso
2006-02-16 14:20 ` unic-037 Hans Hagen
2006-02-16 18:19 ` unic-037 luigi scarso
2006-02-16 18:38 ` Taco Hoekwater [this message]
2006-02-16 19:06 ` unic-037 luigi scarso
2006-02-16 21:34 ` unic-037 Hans Hagen
2006-02-16 21:35 ` unic-037 Hans Hagen
2006-02-17 7:49 ` unic-037 luigi scarso
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=43F4C692.4060705@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).