From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: unwanted extra space in type definition
Date: Mon, 26 May 2014 19:03:29 +0200 [thread overview]
Message-ID: <538373E1.4040505@gmx.es> (raw)
In-Reply-To: <3C93CEFE-7C89-454D-B164-DA34FDA39CD8@gmail.com>
On 05/26/2014 06:08 PM, Wolfgang Schuster wrote:
> Am 26.05.2014 um 18:00 schrieb Pablo Rodriguez:
>> \def\arg#1{\TeXcode{{#1}}}
>> [...]
>> I don’t know what is wrong defined in \arg that inserts an extra space
>> after \em?
>
> You can’t do this form a definition for a verbatim command because TeX has its own rules
> for such a situation (search for a description about catcodes), when you want a copy of
> \TeXcode add
>
> \definetype[arg][TeXcode]
>
> to your document.
>
> BTW: \arg is a predefined command and you should avoid to redefine it
Many thanks for your reply, Wolfgang.
Is there no way that I have the already predefined \arg with colored
contents (braces included)?
Even with defining another command, the problem is that left and right
aren’t covered by option=TEX.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2014-05-26 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 16:00 Pablo Rodriguez
2014-05-26 16:08 ` Wolfgang Schuster
2014-05-26 17:03 ` Pablo Rodriguez [this message]
2014-05-26 16:55 ` luigi scarso
2014-05-26 19:00 ` Pablo Rodriguez
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=538373E1.4040505@gmx.es \
--to=oinos@gmx.es \
--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).