From: Hans Hagen <pragma@wxs.nl>
Cc: Pawel Jackowski na Onet <jackos1@poczta.onet.pl>
Subject: Re: Typing in new command problems
Date: Tue, 23 Sep 2003 23:28:30 +0200 [thread overview]
Message-ID: <5.2.0.9.1.20030923232807.02291008@localhost> (raw)
In-Reply-To: <95a64885.488595a6@poczta.teleton.pl>
At 16:00 23/09/2003 +0200, you wrote:
>Hi,
>
>I try to define new command with typing in this way:
>\def\Command#1%
>{
> \framed[options]
> {
> \starttyping
> #1
> \stoptyping
> }
>}
>and use it in this way:
>\Command{\getbuffer[name]}
>but I have an error:
>! Argument of \copyverbatimline has an extra }.
>
>If I change to \def\Command#1#2%
>I have:
>! Paragraph ended before \Command was complete.
>
>How I can do it - put ConTeXt code to own frame ?...
definetyping
[MyCode]
[before=\startMyFrame,
after=\stopMyFrame]
\defineframedtext
[MyFrame]
[width=fit]
\startMyCode
\Command{\getbuffer[name]}
\stopMyCode
(btw, this kind of framed texts knwo quite well how to get rid of white space)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-09-23 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 14:00 ^Nitram^
2003-09-23 14:33 ` Patrick Gundlach
2003-09-23 16:37 ` Hans Hagen
2003-09-23 16:56 ` Patrick Gundlach
2003-09-23 21:28 ` Hans Hagen [this message]
2003-09-24 10:45 ^Nitram^
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=5.2.0.9.1.20030923232807.02291008@localhost \
--to=pragma@wxs.nl \
--cc=jackos1@poczta.onet.pl \
--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).