ghci: output is not on a new line

L

lubos

Hello,

I am using the Haskell interpreter ghci under FreeBSD. I am not sure whether it is the proper behavior, but any output is not written on a new line, but the current line is rewritten. For example after
[CMD="ghci>"]5+5[/CMD]
I see
Code: 
10ci>
on the same line... Can I change it somehow?

Thank you in advance,

Lubos
 
lubos said:
I am not sure whether it is the proper behavior, but any output is not written on a new line, but the current line is rewritten.
Click to expand...
That's certainly not proper behaviour. I seem unable to reproduce your problem (in other words: it works fine for me), so I can only guess at what's causing it. I think it's either a bug in lang/ghc itself or a faulty terminal setting.

Where/how are you running ghci? On the console or in a terminal emulator? In the latter case, which one? What does % printenv TERM (or your shell's equivalent thereof if you're not using tcsh) say? Are you logged in directly or via SSH? In the former case, did you start ghci manually from a shell or did you launch it from a WM/DE menu of some sort? Does the problem still occur when you run ghci in another way (e.g. on the console instead of a terminal emulator, or in a different terminal emulator, or from a shell instead of a WM/DE menu, etc.), in other words: does it always happen?

If you're certain that the problem is not caused by a faulty terminal setting, I'd suggest updating your ports tree and rebuilding lang/ghc. That might take a while, though.

Fonz
 
fonz said:
Where/how are you running ghci? On the console or in a terminal emulator? In the latter case, which one?
Click to expand...

Thanks for your reply. I am using cons25. I have figured out that - no matter on which shell - after clearing screen with CTRL+L this behavior disappears until reaching the bottom of the screen again.

Knowing this, it is easy for me to avoid that and it does not bring such inconvenience.
 
I did some more tests with lang/ghc built from a freshly updated ports tree on 8.2-RELEASE. The problem appears to only occur with cons25.

@lubos: As a workaround, you could set $TERM to something else (vt100, xterm, etc.) before starting ghci.

Fonz
 
You must log in or register to reply here.
Back
Top