ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: prettyprinting
Date: Thu, 30 Aug 2001 18:40:27 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20010830183746.025cd660@server-1> (raw)
In-Reply-To: <200108301228.OAA13118@sol.cs.uni-dortmund.de>

At 02:28 PM 8/30/2001 +0200, Patrick Gundlach wrote:
>Hi,
>
>I have defined (like verb-jv.tex) a new prettyprinting style.
>Everything is fine, except for the / character.
>
>
>inst auth+ myauth {  // comment
>   target  = /home/users
>   subject = /noth/ing
>   action = open(), close()
>   }
>
>is an example of the language. I would like to use the / as a
>beginning of a single line comment (//) and for a double line
>comment (/*...*/) but also in the language but with the same
>appearance as the word home and users (second line). But now the
>/ appears as a green / and the other words black.
>These are the specials I have now.
>
>\gdef\PONsetspecials%
>   {\PLsetspecials
>     \setpretty`\+=62
>    \setpretty`\#=32
>    \setpretty`\%=41
>    \setpretty`\/=43
>    \setpretty`\*=44 }

maybe you should copy the verb-JV file and take that one as a starting 
point since it has a different / handler,

the following kind of demos what you should do; make sure you use the 
proper namespace

\gdef\PLtypeWHATEVER#1%
   {\endPLtypesix
    \xdef\PLprefix{\getpretty{#1}}%
    \ifinPLcomment
      \getpretty{#1}%
    \else\ifinPLsingle
      \getpretty{#1}%
    \else\ifinPLdouble
      \getprettydata{#1}%
      \ifnum\prettytype=21
        \beginofpretty[\!!prettytwo]\getpretty{#1}\endofpretty
      \else
        \getpretty{#1}%
      \fi
    \else
     %\beginofpretty[\!!prettytwo]    % THIS IS WHERE THE COLOR IS SET THAT 
YOU DONT WANT
      \getpretty{#1}%
     %\endofpretty
    \fi\fi\fi}

\gdef\doPLtypefourtwo#1#2%
   {\PLverbosefalse
    \getprettydata{#2}%
    \ifnum\prettytype=62
      \expandafter\PLtypeWHATEVER
    \else
      \expandafter\PLtypefourone
    \fi
    {#1}#2}

part of the complication has to do with the fact that keywords are parser

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
-------------------------------------------------------------------------


  reply	other threads:[~2001-08-30 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30 12:28 prettyprinting Patrick Gundlach
2001-08-30 16:40 ` Hans Hagen [this message]
2001-08-30 14:32 prettyprinting Patrick Gundlach

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.1.0.14.1.20010830183746.025cd660@server-1 \
    --to=pragma@wxs.nl \
    --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).