From: Lukasz Stafiniak <lukstafi@gmail.com>
To: Francois Berenger <berenger@riken.jp>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] long lines in some OCaml code
Date: Thu, 3 Oct 2013 10:09:32 +0200 [thread overview]
Message-ID: <CAJMfKEXAshQMfG_ujUO5qMyyJHKWuNuUnBvTfpLxB2VkUuPv-g@mail.gmail.com> (raw)
In-Reply-To: <524D15AE.3050600@riken.jp>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
On Thu, Oct 3, 2013 at 8:58 AM, Francois Berenger <berenger@riken.jp> wrote:
> Is there a way to automatically cut all long lines
> in a code base (and indent the cut part correctly)?
>
>
If I wanted to do it I would write a script in Emacs. (Sorry for unhelpful
answer, but the other answers were also unhelpful...) I use
`auto-fill-mode' in Emacs: when I insert a space beyond a given column, it
automatically breaks the line at a previous space.
[-- Attachment #2: Type: text/html, Size: 853 bytes --]
prev parent reply other threads:[~2013-10-03 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 6:58 Francois Berenger
2013-10-03 7:07 ` Adrien Nader
2013-10-03 7:09 ` David House
2013-10-03 8:09 ` Lukasz Stafiniak [this message]
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=CAJMfKEXAshQMfG_ujUO5qMyyJHKWuNuUnBvTfpLxB2VkUuPv-g@mail.gmail.com \
--to=lukstafi@gmail.com \
--cc=berenger@riken.jp \
--cc=caml-list@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