From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105])
	by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id q0VBLnXw013943
	for <caml-list@sympa-roc.inria.fr>; Tue, 31 Jan 2012 12:21:49 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoUEAEjOJ0/RVdS2kGdsb2JhbABDgihlgX6oV3UIIgEBAQEJCQ0HFAQhgXIBAQEEEgIPHQEbHAIDDAYFCw0CAgUWCwICCQMCAQIBEREBBQEcEwYCAQEeh12bVAqLJEiCcIUJP4hxAgULgSSHcYFxAQUCAgIIAQEEDQQGAUeCchkEAwwDFAVXCgs8ggaBFgSVIIVXgTmHBz2EAA
X-IronPort-AV: E=Sophos;i="4.71,595,1320620400"; 
   d="scan'208";a="129527902"
Received: from mail-wi0-f182.google.com ([209.85.212.182])
  by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 31 Jan 2012 12:21:49 +0100
Received: by wibhn14 with SMTP id hn14so6779535wib.27
        for <caml-list@inria.fr>; Tue, 31 Jan 2012 03:21:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=LAHBmb4Ytc27RRDehE2NYJocwdUtnQ2gCGAZ6eh8xFs=;
        b=VxL7q36nkHYcse5uuBeDuBfYeffE+nGQ9WZW1C0Zm/CS0cBDOrnrBX7b2dmdr777GG
         dt+l8YgkGlvCfgniM0Nvqkz/tuqaO15lIMtoLvHGTA8hdsHstooN7vV/x/v2/vDgZOKw
         0FkbLrlZX95Y1Sa3YiRV+eBMSoFuzlrEZuzWs=
Received: by 10.180.99.100 with SMTP id ep4mr33891809wib.7.1328008909080;
        Tue, 31 Jan 2012 03:21:49 -0800 (PST)
Received: from [172.27.6.159] ([213.106.240.92])
        by mx.google.com with ESMTPS id y1sm10305781wiw.6.2012.01.31.03.21.48
        (version=SSLv3 cipher=OTHER);
        Tue, 31 Jan 2012 03:21:48 -0800 (PST)
Message-ID: <4F27CECC.1010500@gmail.com>
Date: Tue, 31 Jan 2012 11:21:48 +0000
From: =?UTF-8?B?TWF0ZWogS2/FocOtaw==?=
 <5764c029b688c1c0d24a2e97cd764f@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: caml-list@inria.fr
References: <471204069.596560.1327958835658.JavaMail.root@zmbs2.inria.fr> <1898845183.596573.1327958954685.JavaMail.root@zmbs2.inria.fr> <20120131100224.GA4413@siouxsie> <CAP5QFJn3ozfsmOooQF2bjF1F-3nNydAQ99oEDkFA9nMomGOwXA@mail.gmail.com>
In-Reply-To: <CAP5QFJn3ozfsmOooQF2bjF1F-3nNydAQ99oEDkFA9nMomGOwXA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Caml-list] [ANN] Vim plugin

On 01/31/2012 11:08 AM, Adrien wrote:
> On 31/01/2012, oliver <oliver@first.in-berlin.de> wrote:
>> Sometimes I had problems with syntax highlighting in OCaml.
>> The end of comments was not always displayed correctly colored.
>> This was the case, when long and nested comments were used.
>> Then the non-comment section sometimes was displayed as
>> if it were a comment.
>>
>> Someone also knows that problem?
>>
>> Maybe that is another issue that you might be able and interested
>> to fix...?!
> 
> Hello,
> 
> I've had the issue with long comments too but I think it's not
> specific to the ocaml highlighting: if you move around (forcing some
> kind of refresh when doing so), you will probably recover the proper
> highlighting (gg'' might be enough).

I can confirm this.

Probably a related problem is that if you go to an end of some
long-enough function (you can try 300-lines-long function); if you leave
vim; reenter vim (or switch to another buffer and switch back), you will
be viewing again end of the long function but syntax-highlighting will
be "out of sync". As if syntax-highlighter did not go backward enough to
be able to interprete meaning of the tokens that you are viewing.