[NTG-context] Re: Typing in new command problems

2003-09-23 Thread Patrick Gundlach 
^Nitram^ [EMAIL PROTECTED] writes:

Hi,

 I try to define new command with typing in this way:
 \def\Command#1%
 {
  \framed[options]
  {
   \starttyping
   #1
   \stoptyping
  }
 }

Don't mess with verbatim stuff in commands. Don't ask why, just don't
do it ;-)


And: TeX != C. Don't write C-like TeX-braces: 

{
 \this
  {
  \that
   {

This will give you a hard time looking for unwanted spaces.

Use % or better: write 

\def\Command#1%
 {\framed[...]%


 How I can do it - put ConTeXt code to own frame ?...

\definetyping
   [nitram]
   [before=\startframedtext,
after=\stopframedtext]
\starttext
\startnitram
crazy
\stopnitram
\stoptext


Patrick
-- 
Silent is the goldfish in its bowl
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] Re: Typing in new command problems

2003-09-23 Thread Patrick Gundlach 
Hans Hagen [EMAIL PROTECTED] writes:

Hello Hans,

 \unprotect

 \def\beginmacro{\catcode`\^^M=\@@ignore}
 \def\endmacro  {\catcode`\^^M=\@@endofline}

 \protect

 \beginmacro

 \def\patrickneedsatexchallengeeachday#1
{Does he?
 (#1)
 Why's That?}

 \endmacro

without trying it, I guess it will write 
Does he?(...)Why's That

hmm, I'll try... Yes :)

OK, ready for the next challenge :)


Patrick

(Perhaps I *do* have built TeX into my brain one day)
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context