From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: where is completecontent defined?
Date: Tue, 16 Apr 2013 21:28:29 +0200 [thread overview]
Message-ID: <516DA65D.5010306@wxs.nl> (raw)
In-Reply-To: <D03704B1-1706-4C75-9692-92F22C3EE1DE@uva.nl>
On 4/16/2013 9:12 PM, Meer, H. van der wrote:
> Your statement doesn't seem true. In neither of the files you mentioned is there a string 'completecontent' to be found. Always assuming I can trust my BBEdit search, of course.
> In fact 'completecontent' occurs in one place only, as %\completecontent in strc-pag.mkiv, that is all. I excluded mkii files in order not to mix things up between mkii and mkiv.
context has a multi lingual interface so for such things you need to
grep for
e!complete
in *.mkiv and *.mkvi as the command is made out of "complete" and
"content" with the first being a command snippet (e!) and the second a
tag (of the list)
that approach is pretty old so also present in mkii
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-04-16 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 15:51 Meer, H. van der
2013-04-16 15:57 ` Wolfgang Schuster
2013-04-16 19:12 ` Meer, H. van der
2013-04-16 19:28 ` Hans Hagen [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=516DA65D.5010306@wxs.nl \
--to=pragma@wxs.nl \
--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).