pty.start()

[zhuchangfei]

why i cat use pty.start()?it point out that "undefined: pty.Start"

[creack]

Can you provide a sample snippet to reproduce?

[lmorg]

I only get that when trying to compile on Windows. The run.go file (which is the only reference of func Start(...)) has +build !windows at the top so any code that references your pty package will fail to build on Windows.

This should shouldn't be a huge surprise to anyone given the nature of this library. For my own project I just fell back to Golang's core libraries if the target OS is Windows. As you know, it would be pretty easy to do the same in this package to save users working around that; but again given the nature of this package, it could be argued a pointless exercise (which is why I didn't raise a pull request).

[creack]

Feel free to open a PR and we can discuss about it there :)

[kopinions]

@imorg how can you fall bell back to golang core libraries? can you give me a example?

[lmorg]

I just did the switching inside my own package by having the PTY package called from its own .go file with // +build !windows prefixing the code. You can see the difference in the two environments if you look at the project code: https://github.com/lmorg/murex/tree/master/lang/proc

The relevant code is inside func ShellExecute in posix.go (PTY) and windows.go (Go standard libs).

Hope this helps

[virtuald]

It's worth noting that https://github.com/containerd/console has a console implementation for Windows. There's quite a bit of overlap with this library.

[dingdayu]

The same prompt suddenly appeared yesterday。

[creack]

Closing in favor of the more generic #95