Edgar Lee

Using frontend inputs: ```sh [+] Building 52.5s (12/12) FINISHED => docker-image://docker.io/hinshun/pack:latest 1.8s => => resolve docker.io/hinshun/pack:latest 1.0s => => sha256:35fbfde1e69df646b751ccab6b6633b0ad4eea17c85affbb5f960e059be48256 527B / 527B 0.0s => => sha256:0b5847db36f6804492ae01b480f4f5ba2f381aeddb7bb2faebd45300412539ea 8.21MB / 8.21MB...

I think `go-expect` definitely have a long way to go in terms of ease of debugging. Unfortunately because `go test` hides away your raw `os.Stdout`, `os.Stdin`, it's hard to provide...

`go-expect` tests are skipped on windows: https://github.com/AlecAivazis/survey/blob/master/survey_windows_test.go Prior to the introduction of `go-expect`, `survey` was manually tested from files here: https://github.com/AlecAivazis/survey/tree/master/tests

@ceymard Perhaps done better in participle, but currently we use `io.TeeReader` before we pass into the participle parser to keep the original text. We use this to construct error reporting...

Do the `Tokens` include the ones from nested structs if the nested structs also have `Tokens []lexer.Token`?

Hi @prietyc123, thanks for this PR. Can you get the travis job for windows working?

Since this PR's goal is to execute tests on windows successfully, I would like it working on travis (for windows) in the same PR.

Hi @singhrasster, sorry only seeing this now. I personally don't use or have a need for Windows hence why it doesn't support it, but I'd be happy to review any...

Send `os.Stdin` into the `expect.Console`. This library is a bit lower level so we expect users to decide how to manage the IO and spawn the child processes.

Hi @psparago, so the problem here is that you're calling `c.ExpectEOF` in a goroutine at the same time as calling other `c.ExpectString`, etc. I think what you want is to...