caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anthony Tavener <anthony.tavener@gmail.com>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Vim syntax supporting first-class modules?
Date: Sat, 30 Jun 2012 16:31:27 -0600	[thread overview]
Message-ID: <CAN=ouMRrDBY9djR9CZaFf6zzrgwe17ZAyuLrLNBb4XF5Vr8B-A@mail.gmail.com> (raw)
In-Reply-To: <CAP_800p+VtTn9bnKzk8GusZabGo3ErDbD69+EwQb5xYXJEOVRA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

On Sat, Jun 30, 2012 at 4:13 PM, Markus Mottl <markus.mottl@gmail.com>wrote:

> On Sat, Jun 30, 2012 at 3:12 PM, Anthony Tavener
> <anthony.tavener@gmail.com> wrote:
> > After first-class modules were introduced there were some questions
> whether
> > anyone had updates for ocaml.vim.
> >
> > About one year later I finally have use for first-class modules but can't
> > find Vim syntax support. Spend a couple hours now delving into the
> arcana of
> > syntax and particularly the module section of ocaml.vim. I've turned back
> > for fear of my sanity.
> >
> > Has anyone else slain this beast already? :)
>
> Though Vim has fairly powerful syntax highlighting features, its
> highlighting language is also not exactly easy to reason about.
> Frankly, a lot of my syntax file, which is probably what you are
> referring to when speaking of insanity, was developed using a heavy
> dose of trial and error, especially when it comes to module syntax.
> Even before first-class modules it was far from perfect.  Feel free to
> risk your sanity and send fixes... ;)
>
> Regards,
> Markus
>
> --
> Markus Mottl        http://www.ocaml.info        markus.mottl@gmail.com
>

Oh, I understand. Certainly I meant no slight on you! I can see how the
syntax definitions lead to a very complex state machine, and I'm often
surprised when the highlighting is correct in the face of complex
language features.

If no one else has, I might venture forward. Though I do wonder what
all those Vim folks at Janestreet are doing? I guess just suffer looking
at some confused highlighting in presence of first-class modules if they
are rare enough anyway.

[-- Attachment #2: Type: text/html, Size: 2361 bytes --]

  reply	other threads:[~2012-06-30 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-30 19:12 Anthony Tavener
2012-06-30 22:13 ` Markus Mottl
2012-06-30 22:31   ` Anthony Tavener [this message]
2012-06-30 23:57     ` Markus Mottl

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='CAN=ouMRrDBY9djR9CZaFf6zzrgwe17ZAyuLrLNBb4XF5Vr8B-A@mail.gmail.com' \
    --to=anthony.tavener@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=markus.mottl@gmail.com \
    /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).