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 mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id 7E3647ED7A for ; Wed, 12 Sep 2012 16:58:01 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of romain.bardou@inria.fr) identity=pra; client-ip=87.98.181.248; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="romain.bardou@inria.fr"; x-sender="romain.bardou@inria.fr"; x-conformance=sidf_compatible Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of romain.bardou@inria.fr) identity=mailfrom; client-ip=87.98.181.248; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="romain.bardou@inria.fr"; x-sender="romain.bardou@inria.fr"; x-conformance=sidf_compatible Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mo2.mail-out.ovh.net) identity=helo; client-ip=87.98.181.248; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="romain.bardou@inria.fr"; x-sender="postmaster@mo2.mail-out.ovh.net"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqwBACiiUFBXYrX4nGdsb2JhbABFu2IBAQEBAQgLCQkUJ4IZNRFAPRYYAwIBAgFYCAKFRYJEBJp8oWOOM4MfA4RCkR2TBw X-IronPort-AV: E=Sophos;i="4.80,410,1344204000"; d="scan'208";a="172872101" Received: from 5.mo2.mail-out.ovh.net (HELO mo2.mail-out.ovh.net) ([87.98.181.248]) by mail1-smtp-roc.national.inria.fr with ESMTP; 12 Sep 2012 16:58:01 +0200 Received: from mail27.ha.ovh.net (b6.ovh.net [213.186.33.56]) by mo2.mail-out.ovh.net (Postfix) with SMTP id 22DC1DC2131 for ; Wed, 12 Sep 2012 17:03:33 +0200 (CEST) Received: from b0.ovh.net (HELO queueout) (213.186.33.50) by b0.ovh.net with SMTP; 12 Sep 2012 16:41:28 +0200 Received: from guest-rocq-135212.inria.fr (HELO ?128.93.135.212?) (romain%bardou.fr@128.93.135.212) by ns0.ovh.net with SMTP; 12 Sep 2012 16:41:28 +0200 Message-ID: <5050A32C.9090809@inria.fr> Date: Wed, 12 Sep 2012 16:58:52 +0200 From: Romain Bardou User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6esrpre) Gecko/20120817 Icedove/10.0.6 MIME-Version: 1.0 To: caml-list@inria.fr X-Ovh-Mailout: 178.32.228.2 (mo2.mail-out.ovh.net) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Ovh-Tracer-Id: 11463912852043631136 X-Ovh-Remote: 128.93.135.212 (guest-rocq-135212.inria.fr) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-OVH-SPAMSTATE: OK X-OVH-SPAMSCORE: 0 X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeehtddrheekucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecunecuhfhrohhmpeftohhmrghinhcuuegrrhguohhuuceorhhomhgrihhnrdgsrghrughouhesihhnrhhirgdrfhhrqeenucfjughrpefkfffhfgggvffutgfgsehtjegrtddtfedu X-Spam-Check: DONE|U 0.578498/N X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeehtddrheekucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecunecuhfhrohhmpeftohhmrghinhcuuegrrhguohhuuceorhhomhgrihhnrdgsrghrughouhesihhnrhhirgdrfhhrqeenucfjughrpefkfffhfgggvffutgfgsehtjegrtddtfedu X-Validation-by: romain.bardou@inria.fr Subject: [Caml-list] Tuareg mode: Indentation of application arguments Hello Caml-list, I have finally took the time to configure tuareg to correctly indent after a "| ... ->" clause. After several years of doing it by hand, this feels soooo much better :) To do this I had to add "(setq tuareg-use-smie t)" to my .emacs (which I found a little confusing, by the way). However, now it's indentation of application arguments which is messed up (to my tastes). Let's say I am writing: a_very_long_function_name argument_1 argument_2 argument_3 argument_4 Now I want to put argument_4 on a new line. Before, I would obtain: a_very_long_function_name argument_1 argument_2 argument_3 argument_4 which I liked. Now, I obtain: a_very_long_function_name argument_1 argument_2 argument_3 argument_4 Note that if I put all arguments on their own lines, indentation does not depend on the function name: a_very_long_function_name argument_1 argument_2 argument_3 argument_4 I did not find any variable controlling this behavior in the tuareg group. Do you know how I can obtain my beloved behavior back? Or is it a bug, in which case I should submit a bug report? The reason I don't like this behavior is that it causes several issues: - changing one function name would imply that one would have to reindent everything (non-local indentation: bad!); - the indentation is not simply "indentation of previous line + N" where N is the same everywhere (complex indentation rule: bad!); - the indentation size may be very long (sudden-death indentation: bad!). My version of tuareg is 2.0.6. Cheers, -- Romain Bardou