Currently, there is no indication that I pressed a letter to choose an
option after asked some question by darcs. If my computer is slow, it
can result in my being unsure whether I have pressed one, and pressing
it again. And that might possibly result in e.g. two hunks being
accepted, when I wanted only the first. Echoing the letter would make
it possible for me to see whether the key got there.

Keep up good work.

Thanks for the bug report! I'll just note here that this is windows-specific
behavior, as key presses are echoed on posix systems.

David

Adding to this note, the prompts just use getChar from the Prelude.  

This may be worth asking the Haskell community about (if anybody hangs out in
#haskell, for example).  Or maybe somebody here knows?

Can somebody tell me what this program does under Windows?

On Linux,

$ ./get-echo 
default echo status: True
sans echo
gimme a char and hit enter [with echo]: x

you said x
with echo
gimme a char and hit enter [sans echo]: 
you said y

Attachments

• get-echo.hs

Another thought: this may be related to the stuff Simon Marlow found here:
http://wiki.darcs.net/index.html/WindowsConsoles

Huh... so if I run my test program on the DOS prompt, I get this error
get-echo.exe: <stdout>: hSetEcho: failed (failed to set echoing)

If I redirect the stdout to a text file, it seems to work fine (and I get
echoing to screen)

It seems that this issue is not completely understood: If there is a solution to 
the problem reported, I am unable to see it. So I would like a volunteer with 
access to a Windows machine to take a further look at this, run kowey's program 
perhaps. And then decide on what to do about it.

Thanks and best regards
Thorkil

This bug solved in darcs 2.2.