From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: specific document layout with ConTeXt
Date: Sun, 28 Dec 2008 14:50:02 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.00.0812281440460.16071@nqv-yncgbc> (raw)
In-Reply-To: <87abag5dex.fsf@cordelia.devereux.me.uk>
On Sun, 28 Dec 2008, John Devereux wrote:
> Aditya Mahajan <adityam@umich.edu> writes:
>
> In general I find other peoples "templates" very educational.
>
>> PS: In your environment file you have
>>
>> \setuplayout[
>> header = 0pt,
>> footer = 0pt,
>> headerdistance = 0pt,
>> footerdistance = 0pt,
>> top = 1.125in,
>> topdistance = 0pt,
>> bottom = 1.125in,
>> bottomdistance = 0pt,
>> leftedge = 0.85in,
>> rightedge = 0.85in,
>> height = fit]
>>
>> ConTeXt will silently ignore all of this. You must not have space
>> between keywords and options. Write this as
>
> I've been using context, on and off, for 5 years and I did not know
> that!
>
> Does anyone know if there is a way to get context to stop when it sees
> an unknown option, instead of silently ignoring it?
The way this is dealt with in the core is by specifying options using
\c!header, etc. This has two advantages: First we get a multi-lingual
interface for free. Second any typos in the keys are caught. This does not
catch "mistakes" like giving an new option to a command, for example
specifying headstyle=something to \setuphead (headstyle is valid for
\setupitemgroup, but not for \setuphead).
There is, however, no way of catching "errors" like
height= fit,
Here context thinks that height is set to " fit" (with the space), and
this does not match any of the cases in the code, so is ignored.
Aditya
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-12-28 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 1:36 Brecht Machiels
2008-12-28 14:00 ` Martin Schröder
[not found] ` <alpine.LNX.2.00.0812281040040.16071@nqv-yncgbc>
2008-12-28 16:06 ` Wolfgang Schuster
2008-12-28 19:40 ` Aditya Mahajan
2008-12-28 19:04 ` John Devereux
2008-12-28 19:50 ` Aditya Mahajan [this message]
2008-12-28 21:42 ` Andrea Valle
2008-12-28 23:56 Brecht Machiels
2008-12-29 15:45 ` Wolfgang Schuster
2008-12-29 17:55 ` Brecht Machiels
2008-12-29 18:09 ` Wolfgang Schuster
2008-12-29 18:52 ` Brecht Machiels
2008-12-29 19:06 ` Wolfgang Schuster
[not found] <mailman.3940.1230479853.19169.ntg-context@ntg.nl>
2009-01-05 8:20 ` richard.stephens
2009-01-05 13:44 ` Aditya Mahajan
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=alpine.LNX.2.00.0812281440460.16071@nqv-yncgbc \
--to=adityam@umich.edu \
--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).