From: Florian Hars <hars@bik-gmbh.de>
To: caml-list@yquem.inria.fr
Subject: tuareg, parens and indentation
Date: Tue, 21 Nov 2006 21:09:35 +0100 [thread overview]
Message-ID: <45635CFF.7010403@bik-gmbh.de> (raw)
I can't seem to be able to get the same indentation from tuareg 1.46 that
I got from 1.45. While 1.46.1 is considerably less broken in this regard
than 1.46.0, it still messes up "one true paren style"
and matches (at least I couldn't find the parameter to get rid of
the two additional spaces). Code like this (from 1.45.2):
match foo with
| None ->
do_something ();
| Some bar -> (
match bar with
| `A -> ()
| `B -> ()
)
or
if cond then (
do_something ();
do_something_else ();
) else
do_yet_another_thing ();
ends up as:
match foo with
| None ->
do_something ();
| Some bar -> (
match bar with
| `A -> ()
| `B -> ()
)
and
if cond then (
do_something ();
do_something_else ();
) else
do_yet_another_thing ();
which is not only ugly (code at the same nesting level ends up on different
indentation levels), but also litters my repository with extensive, useless
whitespace-only patches.
Yours, Florian.
next reply other threads:[~2006-11-21 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 20:09 Florian Hars [this message]
2006-11-22 7:56 ` [Caml-list] " Hendrik Tews
2006-11-23 16:15 ` Albert Cohen
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=45635CFF.7010403@bik-gmbh.de \
--to=hars@bik-gmbh.de \
--cc=caml-list@yquem.inria.fr \
/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