[Bug]Strange bug when using fmt.Scanln after upgrade to v0.2.6

[bin3377]

Bug reports

A very strange bug. After upgrade to v0.2.6, seems using go-prompt in code will change some status of my shell (I'm using zsh on MacOSX) and breaking the function of fmt.Scanln() after that. The symptom is "Return" key will be recognized as "^M" so it will block on the input.

The code to repro:

var pr *prompt.Prompt

func main() {
	user := ""
	fmt.Printf("user: ")
	fmt.Scanln(&user)
	fmt.Printf("got %s\n", user)
	pr = prompt.New(
		func(_ string) {
			os.Exit(0)
		},
		func(d prompt.Document) []prompt.Suggest {
			return nil
		},
	)
	pr.Run()
}

And in the shell, 1st time it works as expected:

$ go run ./main.go
user: test
got test
>

But run it again, the input following user: will be broken:

$ go run ./main.go
user: test^M^M^M^M^M

go version go1.16.2 darwin/amd64

Downgrade to v0.2.5 and it works as expected

Expected Behavior

Should always run as the 1st time

Current Behavior and Steps to Reproduce

What is the current behavior? Please provide detailed steps for reproducing the issue.
A picture or gif animation tells a thousand words

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: Mac OSX 10.15.7
• Terminal Emulator: (i.e. iTerm2) iTerm2/zsh
• tag of go-prompt or commit revision: v0.2.6

[jsun-m]

any updates on this?