From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Doubled annotation content
Date: Fri, 7 Dec 2012 14:04:27 +0100 [thread overview]
Message-ID: <C7022E09-1474-4B2F-AC63-8B18FE9CC085@gmail.com> (raw)
In-Reply-To: <20121207092608.GE26897@homerow>
[-- Attachment #1.1: Type: text/plain, Size: 1194 bytes --]
Am 07.12.2012 um 10:26 schrieb Marco Patzer <homerow@lavabit.com>:
> On 2012–12–07 Wolfgang Schuster wrote:
>
>> The argument for the command keys has to be a macro with two parameters,
>> the first parameters contains the formatted header and the second argument
>> the formatted content of the environment.
>
> That's how I used it in the past, but after an update I got an error
> which vanished after I removed the two arguments. I thought the
> interface might have changed.
>
> I used it as follows. What's wrong with that?
>
> %% macros=mkvi
> \usemodule [annotation]
>
> \defineannotation
> [myannotation]
> [alternative=command,
> command=\cmd]
>
> \starttexdefinition cmd #first #second
> \placeannotationcontent
> \stoptexdefinition
Commands need to be unexpandable because when you use the “command”.
This is necessary because I check for a command and this needs \unexpanded\def to work.
You can create a unexpandable command with \starttexdefintion by adding
the unexpanded keyword as first argument to the environment.
\starttexdefinition unexpanded cmd #first #second
\placeannotationcontent
\stoptexdefinition
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2042 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-12-07 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 20:24 Marco Patzer
2012-12-06 20:59 ` Otared Kavian
2012-12-06 22:00 ` Marco Patzer
2012-12-06 22:27 ` Aditya Mahajan
2012-12-07 5:51 ` Wolfgang Schuster
2012-12-07 5:38 ` Wolfgang Schuster
2012-12-07 9:26 ` Marco Patzer
2012-12-07 13:04 ` Wolfgang Schuster [this message]
2012-12-07 13:21 ` Marco Patzer
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=C7022E09-1474-4B2F-AC63-8B18FE9CC085@gmail.com \
--to=wolfgang.schuster@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).