Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: "Emilio Jesús Gallego Arias" <gallego@cri.ensmp.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] How can I change the margin size in the toplevel?
Date: Wed, 23 Sep 2015 14:16:08 +0200	[thread overview]
Message-ID: <m2io71l4af.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <1443008077.4442.1.camel@e130.lan.sumadev.de> (Gerd Stolpmann's message of "Wed, 23 Sep 2015 13:34:37 +0200")

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

Hello,

On 2015-09-23 13:34, Gerd Stolpmann <info@gerd-stolpmann.de> writes:

> Am Mittwoch, den 23.09.2015, 12:25 +0200 schrieb Emilio Jesús Gallego
> Arias:
>> Hi Alan,
>> 
>> The code seems to have changed in the last months (likely due to color
>> support), but the corresponding code in trunk is at parsing/location.ml:335.
>> 
>> Indeed, this little hack works for me(TM):
>> 
>> 8<--------------------------------------------------------------------8<
>> Index: parsing/location.ml
>> ===================================================================
>> --- parsing/location.ml	(revision 16441)
>> +++ parsing/location.ml	(working copy)
>> @@ -333,6 +333,7 @@
>>  let pp_ksprintf ?before k fmt =
>>    let buf = Buffer.create 64 in
>>    let ppf = Format.formatter_of_buffer buf in
>> +  Format.pp_set_margin ppf (200 + 1);
>>    Misc.Color.set_color_tag_handling ppf;
>>    begin match before with
>>      | None -> ()
>> 8<--------------------------------------------------------------------8<
>> 
>> I don't know what would be the proper way to integrate it upstream.

Thank you for tracking down where the formatter is created. It makes
sense now why I was not able to change these margins.

> Maybe to propagate the margin?
>
> Format.pp_set_margin ppf (Format.pp_get_margin Format.std_formatter())
>
> Don't know whether std_formatter or err_formatter is the right one.

It’s not clear. The formatter for warnings is set by default to the
error formatter
(https://github.com/ocaml/ocaml/blob/b860d631458802c8685aa59c9d7b66a9225fcedb/parsing/location.ml#L309)
but the toplevel loop sets it to the std formatter (the loop is called
with std_formatter,
https://github.com/ocaml/ocaml/blob/b860d631458802c8685aa59c9d7b66a9225fcedb/parsing/location.ml#L309).
So a solution could be to reuse its value:

Format.pp_set_margin ppf (Format.pp_get_margin !formatter_for_warnings ())

Thanks again,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated September 22, 2015, Mauna Loa Obs.): 397.77 ppm

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

      reply	other threads:[~2015-09-23 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 14:20 Alan Schmitt
2015-09-22 17:14 ` Emilio Jesús Gallego Arias
2015-09-23  6:48   ` Alan Schmitt
2015-09-23  7:26     ` David MENTRE
2015-09-23 12:23       ` Alan Schmitt
2015-09-23 16:05         ` Alan Schmitt
2015-09-23 16:39           ` Gabriel Scherer
2015-09-23 10:25     ` Emilio Jesús Gallego Arias
2015-09-23 11:34       ` Gerd Stolpmann
2015-09-23 12:16         ` Alan Schmitt [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=m2io71l4af.fsf@charm-ecran.irisa.fr \
    --to=alan.schmitt@polytechnique.org \
    --cc=caml-list@inria.fr \
    --cc=gallego@cri.ensmp.fr \
    --cc=info@gerd-stolpmann.de \
    /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