caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
* Re: [Caml-list] Irritating top-level problem
  2008-11-23 16:37 Irritating top-level problem Jon Harrop
@ 2008-11-23 16:27 ` Eric Cooper
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Cooper @ 2008-11-23 16:27 UTC (permalink / raw)
  To: caml-list

On Sun, Nov 23, 2008 at 04:37:15PM +0000, Jon Harrop wrote:
> Any ideas how to circumvent this problem?

In Emacs you can use Caml interactive mode to run the top level in a
buffer.  Then you can send expressions to be evaluated directly to the
process, rather than via cut & paste.

-- 
Eric Cooper             e c c @ c m u . e d u


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Irritating top-level problem
@ 2008-11-23 16:37 Jon Harrop
  2008-11-23 16:27 ` [Caml-list] " Eric Cooper
  0 siblings, 1 reply; 2+ messages in thread
From: Jon Harrop @ 2008-11-23 16:37 UTC (permalink / raw)
  To: caml-list


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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-11-23 16:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-11-23 16:37 Irritating top-level problem Jon Harrop
2008-11-23 16:27 ` [Caml-list] " Eric Cooper

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).