From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug with headcommand=type in definedescription?
Date: Sun, 29 Jan 2012 13:05:34 +0100 [thread overview]
Message-ID: <41E26CE9-7779-4E1F-8791-23F59D54E44D@googlemail.com> (raw)
In-Reply-To: <4F253003.5050509@web.de>
Am 29.01.2012 um 12:39 schrieb Pablo Rodríguez:
> Hi there,
>
> I have the following sample that works with \type:
>
> \definedescription[abc][headcommand=\tfa]
> \starttext
> \abc{\type{\startext}} not working
> \stoptext
>
> But if I use the headcommand=type option:
>
> \definedescription[abc][headcommand=\type]
> \starttext
> \abc{\startext} not working
> \stoptext
>
> it gives an error.
>
> Am I doing something wrong or have I hit a bug?
The \type has to change the meaning of "\” to make it a normal symbol
but when you use it with headcommand it is to late. A better command
to show command is \tex{…} which appends a save version of "\” in front
of the argument.
\definedescription[abc][headcommand=\tex]
\starttext
\abc{startext} not working
\stoptext
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-29 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 11:39 Pablo Rodríguez
2012-01-29 12:05 ` Wolfgang Schuster [this message]
2012-01-29 15:17 ` Pablo Rodríguez
2012-01-29 16:49 ` Aditya Mahajan
2012-01-29 17:08 ` Pablo Rodríguez
2012-01-29 17:24 ` Wolfgang Schuster
2012-01-29 17:42 ` Pablo Rodríguez
2012-01-29 18:09 ` Wolfgang Schuster
2012-01-29 18:19 ` Pablo Rodríguez
2012-01-29 18:38 ` Aditya Mahajan
2012-01-29 18:53 ` 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=41E26CE9-7779-4E1F-8791-23F59D54E44D@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).