From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.9 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id A68B1BB84 for ; Sun, 23 Nov 2008 16:34:38 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhYCAHsGKUnUnw4TgWdsb2JhbACCPJEgAQELCQoHEwO5T4J8 X-IronPort-AV: E=Sophos;i="4.33,654,1220220000"; d="scan'208";a="31736645" Received: from pih-relay06.plus.net ([212.159.14.19]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/AES256-SHA; 23 Nov 2008 16:34:38 +0100 Received: from [87.114.133.237] (helo=leper.local) by pih-relay06.plus.net with esmtp (Exim) id 1L4Gyr-0004Sx-CT for caml-list@yquem.inria.fr; Sun, 23 Nov 2008 15:34:37 +0000 From: Jon Harrop Organization: Flying Frog Consultancy Ltd. To: caml-list@yquem.inria.fr Subject: Irritating top-level problem Date: Sun, 23 Nov 2008 16:37:15 +0000 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811231637.15807.jon@ffconsultancy.com> X-Plusnet-Relay: 71dae30ba0750d650795a479f48b91f3 X-Spam: no; 0.00; ocaml:01 frog:98 pairs:01 newline:02 newline:02 xemacs:02 top-level:03 top-level:03 indentation:04 spaces:04 spaces:04 problem:05 problem:05 reads:08 wrong:10 I often use the OCaml top-level by copying and pasting code from a XEmacs or KWrite window into a KTerm. However, there appears to be a synchronization problem where the top-level prints two spaces after each newline at a random point in time. So the indentation is not only wrong but the code has random pairs of spaces injected into it. I assume this is a race condition between printing due to the pasting and printing after the top-level reads a newline. Any ideas how to circumvent this problem? How is this synchronization supposed to occur? -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e