ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nikolai Weibull <mailing-lists.context-users@rawuncut.elitemail.org>
Subject: Re: An idea
Date: Fri, 2 Dec 2005 19:43:37 +0100	[thread overview]
Message-ID: <20051202184337.GB8858@puritan.petwork> (raw)
In-Reply-To: <20051202174653.GB3376@fly.srk.fer.hr>

Zeljko Vrba wrote:

> On Fri, Dec 02, 2005 at 05:56:36PM +0100, Nikolai Weibull wrote:

> > We were planning on using Vim for preprocessing things like this
> > instead

> Vim for preprocessing? Isn't it a bit too painful compared to using a
> "real" programming language?

You misunderstand.  Vim can easily be made to output the highlighting it
would apply to a document on the display to something else, e.g.,
outputting TeX directives instead.

A subthread on the subject can be found here:

http://www.ntg.nl/pipermail/ntg-context/2005/012885.html

It would require very little programming.  syntax/2html.vim, which
converts the buffer to a HTML document with syntax highlighting, is 526
lines in the current CVS incarnation.  A syntax/2context.vim would be
even shorter, perhaps 150 to 200 lines.  If I find the time I’ll write
something this weekend.  I’m catching a could though, so I might not
:-(.

(Note: This would thus allow highlighted code for any format Vim
understand, which is currently over 450!)

        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-12-02 18:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 16:29 Zeljko Vrba
2005-12-02 14:14 ` Hans Hagen
2005-12-02 17:43   ` Zeljko Vrba
2005-12-02 16:56 ` Nikolai Weibull
2005-12-02 17:04   ` Taco Hoekwater
2005-12-02 19:15     ` Re[2]: " Giuseppe Bilotta
2005-12-02 17:46   ` Zeljko Vrba
2005-12-02 18:43     ` Nikolai Weibull [this message]
2005-12-03 19:45       ` Nikolai Weibull
2005-12-03 22:48         ` Christopher Creutzig
2005-12-04 17:57           ` Nikolai Weibull
2005-12-04 19:00           ` Hans Hagen
2005-12-11 21:17             ` Christopher Creutzig
2005-12-04 18:59         ` Hans Hagen
2005-12-04 19:14           ` Nikolai Weibull
2005-12-04 20:38             ` Hans Hagen
2005-12-05 20:48               ` Nikolai Weibull
2005-12-06  9:11                 ` Hans Hagen
2005-12-05 19: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=20051202184337.GB8858@puritan.petwork \
    --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).