ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nikolai Weibull <mailing-lists.context-users@rawuncut.elitemail.org>
Subject: Re: some highlighted \type-ing
Date: Wed, 7 Sep 2005 18:13:06 +0200	[thread overview]
Message-ID: <20050907161306.GB8829@puritan.pnetwork> (raw)
In-Reply-To: <6faad9f0050907075370287cab@mail.gmail.com>

Mojca Miklavec wrote:

> But, I finally understand why I was confused yesterday.
> 
>     \setupcolors[state=start]
>     \setuptype[option=TEX]
>     \type{\a}
> 
> does nothing (and this was what I first tried and thought that this is
> not supported yet; non-existing options never raise an error anyway).

I reported this bug back in April but no one replied.  The problem is
that the first character is read and then not given back the right
catcode so that the typing stuff can process it correctly.

This mainly affected me when I was trying to write inline C code, such
as \type{int a}, because the int wouldn't be highlighted as a keyword.

> I'm thinking about piping the code to vim, letting the vim process it
> and return something like
>     \highlight[Conditional]{if}\highlight[Delimiter]{(}\highlight[Identifier]{i}
> ...
> One should modify the 2html.vim file (vim can already nicely transform
> the highlighted code into HTML, so ConTeXt shouldn't be so difficult).
> Vim already has over 400 sytax file definitions (probably equivalent
> to some hundred thousans lines of syntax definitions in ConTeXt).
> Well, I don't know (yet) how to do it, but if someone on the list has
> more experience with vim, please feel free to contribute.

Yes, this would definitely be a good alternative way of getting
highlighting (for free).  Writing a converter shouldn't be that hard,
and writing ConTeXt code shouldn't be impossible either.  Alas, I don't
have time at the moment.  I need to find myself a job first; which sadly
probably won't be found in Sweden...Sweden is such a boring place when
it comes to IT,
        nikolai

-- 
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

  reply	other threads:[~2005-09-07 16:13 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 [this message]
2005-09-08  9:55         ` Taco Hoekwater
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=20050907161306.GB8829@puritan.pnetwork \
    --to=mailing-lists.context-users@rawuncut.elitemail.org \
    --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).