ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: pragma@wxs.nl (Hans Hagen)
Subject: Re: Commands in verbatim
Date: Tue, 21 Dec 1999 17:37:19 +0100	[thread overview]
Message-ID: <3.0.6.32.19991221173719.016511d0@pop.wxs.nl> (raw)
In-Reply-To: <199912211208.NAA24702@fly.srk.fer.hr>

At 01:08 PM 12/21/99 +0100, Zeljko Vrba wrote:
>I put this in my file:
>\setuptyping[option=commands,escape=?]
>(I want ? to be escape character because it will not interfere with other
>characters I'll be using in verbatim)
>
>then this:
>\starttyping
>	?underbar{if} expr ..
>\stoptyping
>
>and get this error message:
>
>! Undefined control sequence.
><argument>     \underbar{if}

Since all chars are letters, the {} are not handled. Another escape is
using <<if>> and option=slanted. 

>regular cmr font. BTW, /bf (?bf) works fine. ?underbar if just places a
>single underbar, like this:
>	_if
>(this is typeset by ?underbar if). I'd like
>	if
>	--
>Is it possible to do it?

You could try: 

  \def\Key#1#2x{\underbar{#2}}

(the spaces are important)

  .... ?Key ifx 

that way the x acts as sentinel. 

Even better: 

\def\IfKey{\underbar{if}}

  .... ?IfKey .... 

I would go for the last alternative. 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------


       reply	other threads:[~1999-12-21 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3.0.6.32.19991220165848.007e95c0@pop.wxs.nl>
     [not found] ` <199912211208.NAA24702@fly.srk.fer.hr>
1999-12-21 16:37   ` Hans Hagen [this message]
1999-12-17 14:01 Zeljko Vrba

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=3.0.6.32.19991221173719.016511d0@pop.wxs.nl \
    --to=pragma@wxs.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).