-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not display option and select option when run azd init
by GoLand
#4311
Comments
@rujche I haven't looked into how the With #4318, we'll give you the ability to specify If you have spare time and would love to help us, you can run the code snippet from the library we're using to investigate why the terminal detection logic isn't working as expected -- and what we may want to contribute upstream (issue or code) to fix this behavior. package main
import (
"fmt"
"github.com/mattn/go-isatty"
"os"
)
func main() {
if isatty.IsTerminal(os.Stdout.Fd()) {
fmt.Println("Is Terminal")
} else if isatty.IsCygwinTerminal(os.Stdout.Fd()) {
fmt.Println("Is Cygwin/MSYS2 Terminal")
} else {
fmt.Println("Is Not Terminal")
}
} |
Hi, @weikanglim Thanks for the reply.
|
Hi, @weikanglim After adding the changed in your PR, it returns the new error: |
It looks like Once thing that could help -- there's a new beta GoLand terminal that you could try here. I'm not sure if they changed things underneath that could fix the experience here. |
In this change, we introduce `AZD_FORCE_TTY` as a mechanism to force TTY output behavior. We removed an environment variable `AZD_TERM_SKIP_CI_DETECT` since `AZD_FORCE_TTY` is the higher-level override. Helps with #4311
Issue addressed via #4318 |
/unresolve |
Describe the problem
Can not display option and select option when run by GoLand
To Reproduce
cli/azd/main.go
by GoLand.Initializing an app to run on Azure (azd init) How do you want to initialize your app?
, but no option displayed.Expected behavior
Options displayed and can be selected.
Environment
Information on your environment:
The text was updated successfully, but these errors were encountered: