From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: most recent manual
Date: Tue, 3 Jan 2012 10:02:37 +0100 [thread overview]
Message-ID: <DFC8CF32-6EDD-4A2C-BE80-3260341A1F5D@googlemail.com> (raw)
In-Reply-To: <CAHJRaA7Hjy3Gs2K5JYvB2h7zXV2+iSx8dJubJPuK_O_mPqdHhQ@mail.gmail.com>
Am 03.01.2012 um 04:10 schrieb Chris Lott:
> I'm working my way through the ConTeXt manual/reference. I discovered
> the draft of a new manual at:
> http://wiki.contextgarden.net/manual_being_revised -- is this the
> latest available anywhere? I'm finding a lot of things that are out of
> date in the new draft (for instance, using \setupnote[footnote]
> instead of \setupfootnotes) which generally means doing it wrong,
> searching google and the wiki for information, and finding out that
> things have changed :) Is this the best way?
\setupfootnote == \setupnote[footnote]
The second form is the recommended way and commands like \setupfootnote
are there for backward compatibility but for new functions it’s always
\setupXXX[<environment>].
Wolfgang
___________________________________________________________________________________
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:[~2012-01-03 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 3:10 Chris Lott
2012-01-03 8:52 ` Chris Lott
2012-01-03 9:18 ` luigi scarso
2012-01-03 9:02 ` Wolfgang Schuster [this message]
2012-01-03 17:40 ` Chris Lott
2012-01-03 18:10 ` Wolfgang Schuster
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=DFC8CF32-6EDD-4A2C-BE80-3260341A1F5D@googlemail.com \
--to=schuster.wolfgang@googlemail.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).