From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX syntax -- a guide?
Date: Thu, 25 Feb 2010 22:39:37 +0100 [thread overview]
Message-ID: <B6CEDAF3-E1F8-4F25-B6D5-C92859EA8E73@uni-bonn.de> (raw)
In-Reply-To: <771da05a1002251239m1c776aday35037db145c030a6@mail.gmail.com>
On Feb 25, 2010, at 9:39 PM, James Fisher wrote:
> Hi,
>
>
> After a few days working in "do what the tutorials say" mode, I now want to understand TeX from a programmer's mindset. I have not been able just by practise to work out what the syntactic rules of TeX are, and I am hoping that there is a sensible guide to this somewhere. However, searches for things like "tex syntax" draw a blank. Some of the things I want to understand, for example, are: (1) what is the distinction between square brackets and curly brackets after a command? (2) Why are there sometimes lists of square-bracketed lists after a command, each with lists of seeming arguments inside them? (2) What exactly are the "variables" in a TeX file? (I've seen variable-like things sometimes referred to just plainly, sometimes with preceding backslashes as if they were commands/mac
ros). (4) Why can't I end a square-bracketed section with a final square-bracket on a line of its own, as I may do in other programming languages? (5) How are things like \subsection, \sub
subsection, \subsubsubsection, ... implemented? I am used to languages in which there is only a finite set of commands; why is the logic here not more like \section[level=1], \section[level=2], ... ? (6) Perhaps I'm misunderstanding things and all this isn't actually the fundamental syntax of TeX but just adhoc syntax defined by various macros doing different things -- is this the case; to what degree can macros define syntax?
>
> Obviously I don't expect answers to all these here, but can someone point me to somewhere on the 'net that could answer them? The only other possibilities I can see are buying an expensive copy of the TeXbook, etc.
>
First, you're confusing two things: TeX syntax and ConTeXt syntax. Most of what you're asking here has to do with the way ConTeXt implements things. For starters, I would recommend http://wiki.contextgarden.net/Inside_ConTeXt, especially the overview about System Macros.
But if you want to actually write your own macros (or simply understand the way ConTeXt works) you will indeed need some understanding of TeX. Complaining about the price of the TeXbook doesn't sit very well with most TeXies (most of us think the price is reasonable, we're using this incredibly software for free, and if you're really poor, you can always go to a library), but there's an absolutely wonderful book which you can download for free, TeX by topic, http://eijkhout.net/texbytopic/texbytopic.html Personally, I find it more accessible than the TeXbook.
HTH
Thomas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-02-25 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 20:39 James Fisher
2010-02-25 21:39 ` Thomas A. Schmitz [this message]
2010-02-25 21:51 ` Aditya Mahajan
2010-02-26 1:04 ` James Fisher
2010-02-26 6:25 ` Peter Münster
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=B6CEDAF3-E1F8-4F25-B6D5-C92859EA8E73@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).