From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: core-buf.tex?
Date: Thu, 27 Jul 2006 10:18:15 +0200 [thread overview]
Message-ID: <44C876C7.4040905@elvenkind.com> (raw)
In-Reply-To: <9CFD2D6A-150E-4BA4-8146-997639C1B973@cox.net>
David Arnold wrote:
> All,
>
> In looking at core-buf.tex to see if I could find anything about
> subblocks, I came across at line 518:
>
> \def\setblocklevel#1% sign
> {\global\advance\blocklevel #11
> \ifcase\blocklevel\doingblocksfalse\else\doingblockstrue\fi}
>
> Is that 11 correct?
That is not 11, that is #1 followed by 1, and it is called
with #1 == + or #1 == -, so the expansion becomes
\global\advance\blocklevel + 1
or
\global\advance\blocklevel - 1
Cheers, taco
prev parent reply other threads:[~2006-07-27 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 7:44 core-buf.tex? David Arnold
2006-07-27 8:18 ` 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=44C876C7.4040905@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).