ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: some highlighted \type-ing
Date: Thu, 08 Sep 2005 11:55:47 +0200	[thread overview]
Message-ID: <43200AA3.1010908@elvenkind.com> (raw)
In-Reply-To: <6faad9f0050907075370287cab@mail.gmail.com>



Mojca Miklavec wrote:
> Taco, you sent some patch for XML syntax highlighting some time ago.
> 
> I don't know if you fixed this one as well:
>     <!-- some text -->
> The both minus signs in "-->" are highlighted wrong as well. The code
> inside <!-- ... --> is gray, but it would be great to have both
> delimiters highligted as "comment" as well.

With this simple patch (only two new commands),  both sets of dashes
are blue:

   \input verb-xml
   \unprotect
   \gdef\dododoXMLtypeonefive#1#2%
     {\getprettydata{#2}%
      \ifnum\prettytype=11
      \endofpretty
      \beginofpretty[\!!prettythree]%TH: NEW
      \getpretty{\prev}#1\empty
      \endofpretty                  %TH: NEW
      \global\inXMLcommentfalse#2%
      \else
      \getpretty{\prev}#1#2%
      \fi}
   \protect

This makes comments behave like PI instructions, but maybe
you want the entire comment grey, including the leading
'<!' and trailing '>' ?
That would be require a much larger patch though.

Taco

  parent reply	other threads:[~2005-09-08  9:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 15:26 Mojca Miklavec
2005-09-06 15:40 ` Taco Hoekwater
2005-09-06 16:01   ` Mojca Miklavec
2005-09-06 16:21     ` Taco Hoekwater
2005-09-07  9:35     ` Taco Hoekwater
2005-09-07 14:53       ` Mojca Miklavec
2005-09-07 16:13         ` Nikolai Weibull
2005-09-08  9:55         ` Taco Hoekwater [this message]
2005-09-08 11:25           ` Adobe reader 7.0.1 for linux luigi.scarso
2005-09-08 12:05             ` Taco Hoekwater
2005-09-08 13:41             ` Hans Hagen
2005-09-06 16:36   ` some highlighted \type-ing Hans Hagen
2005-09-07 15:27     ` Mojca Miklavec

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=43200AA3.1010908@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).