From: "Zhichu Chen" <zhichu.chen@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: \startvariables failed after the current update
Date: Tue, 28 Oct 2008 08:49:19 +0000 [thread overview]
Message-ID: <769ba7780810280149l6fbceed6gb7bf86faafa856fe@mail.gmail.com> (raw)
In-Reply-To: <4906CDBE.3050706@wxs.nl>
Oops. Thanks. Although I think it would be much simpler if we can do this
by using comma lists.
On Tue, Oct 28, 2008 at 8:30 AM, Hans Hagen <pragma@wxs.nl> wrote:
> Zhichu Chen wrote:
>> Hi there,
>>
>> I haven't updated my ConTeXt distribution for a very long time (for
>> the internet connection problem here) and somehow my network
>> worked, so I use ctxtools --update to make an update. During the
>> updating, I got some error message like "I can't find mult-def.tex"
>> and some other files more. Weird, because I do have those files
>> and kpsewhich can locate them. I just input the needed files WITH
>> the path and seemed OK. To make sure, I made another ctxtools --update
>> and this time no error messages.
>>
>> Anyway, I compiled a used-to-be-working file and failed because
>> some "Undefined control sequence" and I found the "undefined"
>> macros are the \c!xxx and \v!yyy macros which I defined them
>> in
>> \startvariables all
>> yyy: yyy
>> \stopvariables
>>
>> \startconstants all
>> xxx: xxx
>> \stopconstants
>>
>> any explanations?
>
> sure, that interface has gone
>
> \setinterfacevariable{yyy}{yyy}
> \setinterfaceconstant{xxx}{xxx}
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
Best Regards
Chen
----------------------------------------------------------------
Zhi-chu Chen | Shanghai Synchrotron Radiation Facility
No. 2019 | Jialuo Rd. | Jiading | Shanghai | P.R. China
tel: 086 21 5955 3405 | zhichu.chen.googlepages.com
| www.sinap.ac.cn
----------------------------------------------------------------
___________________________________________________________________________________
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-10-28 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 7:35 Zhichu Chen
2008-10-28 8:30 ` Hans Hagen
2008-10-28 8:49 ` Zhichu Chen [this message]
2008-10-28 9:57 ` Hans Hagen
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=769ba7780810280149l6fbceed6gb7bf86faafa856fe@mail.gmail.com \
--to=zhichu.chen@gmail.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).