From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 5F0377EE51 for ; Sun, 14 Apr 2013 20:19:34 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of jonathan.protzenko@gmail.com) identity=pra; client-ip=209.85.212.171; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jonathan.protzenko@gmail.com"; x-sender="jonathan.protzenko@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of jonathan.protzenko@gmail.com designates 209.85.212.171 as permitted sender) identity=mailfrom; client-ip=209.85.212.171; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jonathan.protzenko@gmail.com"; x-sender="jonathan.protzenko@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wi0-f171.google.com) identity=helo; client-ip=209.85.212.171; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jonathan.protzenko@gmail.com"; x-sender="postmaster@mail-wi0-f171.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvEBAAPyalHRVdSrjWdsb2JhbAA2GoJlV4MwvhCBBRYOAQEBAQcLCwkSBiSCHwEBBSMPAQ0BGxwBAQMMBgULDQICBRYLAgIJAwIBAgEREQEFARwGDQEHAQGHfQEDDwELL5wAi2BPgnuDXwoZJw1ZiH4BBQyBF410B4IugRMDlwWBIY4OP4Qw X-IPAS-Result: AvEBAAPyalHRVdSrjWdsb2JhbAA2GoJlV4MwvhCBBRYOAQEBAQcLCwkSBiSCHwEBBSMPAQ0BGxwBAQMMBgULDQICBRYLAgIJAwIBAgEREQEFARwGDQEHAQGHfQEDDwELL5wAi2BPgnuDXwoZJw1ZiH4BBQyBF410B4IugRMDlwWBIY4OP4Qw X-IronPort-AV: E=Sophos;i="4.87,471,1363129200"; d="scan'208";a="10913952" Received: from mail-wi0-f171.google.com ([209.85.212.171]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 14 Apr 2013 20:19:33 +0200 Received: by mail-wi0-f171.google.com with SMTP id hn17so902833wib.16 for ; Sun, 14 Apr 2013 11:19:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lqHL7zHbPbyUDfvVQWn01QKe9+2sED8qBFVfmVTFUIs=; b=wXsfndUNVlbrSVimieS8Nd/OzOhS80r+FEIpEvQnljuQTN1Fc1Y2V1GgC76r9Ff/Zq VG+stGfa2MejwRbv/hCan7boStKnyPf+ILJ26Lw+GZdt4gTzRJ14ozJLKgts0NCQq0Hl 8ZUrpOAZIk5N5FZVbdTFF43oe5WWyWUE6p0sUtGvjf3xnP3NPYrM70H5B5fnmtwoJlKi o3iQugonzTBrikqwP4G5qgO5Gsad4jQjcIEdjaO0D7KPAzPHY7V3jab9FfN7nDY800WY kI+/ai93Ms/ztr+dXjCjnsNTVqKdjcBOViYxyx6GwfFSyBzmGx3Z3L5NXrjSlF3g5tHy JYuw== X-Received: by 10.194.82.34 with SMTP id f2mr25739004wjy.25.1365963573412; Sun, 14 Apr 2013 11:19:33 -0700 (PDT) Received: from ?IPv6:2a01:e35:2f37:f210:5e26:aff:fe0c:c1d8? ([2a01:e35:2f37:f210:5e26:aff:fe0c:c1d8]) by mx.google.com with ESMTPS id er1sm9276789wib.5.2013.04.14.11.19.31 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 14 Apr 2013 11:19:32 -0700 (PDT) Message-ID: <516AF334.2040202@gmail.com> Date: Sun, 14 Apr 2013 20:19:32 +0200 From: Jonathan Protzenko User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: =?UTF-8?B?RGFuaWVsIELDvG56bGk=?= CC: William Smith , Caml-list , Gabriel Scherer References: <516AC928.9030400@emu-bark.com> <93F65479FCAB425282517E571DA027D9@erratique.ch> In-Reply-To: <93F65479FCAB425282517E571DA027D9@erratique.ch> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [Caml-list] modified error messages for ocamlc The OCaml mode for emacs that's distributed along with the OCaml sources contains (caml.el) : 796 ;; Newer emacs versions support line/char ranges 797 ;; We will adapt OCaml to output error messages in a compatible format. 798 ;; In the meantime we add the new format here in addition to the old one. 799 (defconst caml-error-regexp-newstyle 800 "^[ A-\377]+ \"\\([^\"\n]+\\)\", line \\([0-9]+\\), char \\([0-9]+\\) to line \\([0-9]+\\), char \\([0-9]+\\):" 801 "Regular expression matching the error messages produced by ocamlc/ocamlopt.") So there are provisions already in the Emacs mode for parsing multi-line error formats. What refrains us from switching directly to the format that's recognized by the already-distributed Caml mode ? Cheers, jonathan On Sun 14 Apr 2013 07:57:36 PM CEST, Daniel Bünzli wrote: > Le dimanche, 14 avril 2013 à 18:06, Gabriel Scherer a écrit : >>>> Would there be any interest in me making the change everywhere and submitting it as a patch? >>> >>> Not at all... >> I'm not sure if this is a language barrier thing, or sarcasm/irony >> that got lost on the wire, > > No, it was a true answer, I'm not interesting in having changes introduced in ocaml that break features that are useful to me *every* day. Namely the ability of compilation-mode to precisely hilight the span of an error in my source, without having to tweak my .emacs. (That's said I'd have nothing against an implementation of gnu's standard). > > >> On a related note, I have put in >> http://caml.inria.fr/mantis/view.php?id=5044 some hooks for Emacs >> compile-mode to parse additional error messages that are not supported >> by default, namely the backtrace format and the location printed in >> the 'assert false' error message. > > I still don't understand your issue here. For me everything works pefectly out of the box, character ranges included (or maybe I never fell on a specific case ?). > >> This is so convenient that I often >> feed "ocamlbuild test.byte && ./test.byte" as my compilation command >> in my edit-compile-test cycles. > > Yes, that's also what I do. > > Best, > > Daniel > > >