Unable to select or enter Yes when asked to run myst start

[VRConservation]

Latest version. Unable to enter Y/n when running myst (must init). Can't type anything in the (Y/n) is greyed out. Have tried uninstalling and reinstalling. This is in the anaconda CLI but I've tried running it in VS Code terminal and power shell. Thanks for any help.

[welcome[bot]]

Thanks for opening your first issue here! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.
If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).
Welcome to the EBP community! :tada:

[rowanc1]

Very strange, thanks for the report. As a stop gap you can pass in myst init -y. After you init there shouldn't be any prompts for myst start or myst build.

[VRConservation]

Thanks. If I pass "myst init -y" I get "error: unknown option '-y'". Below is the screenshot of passing myst or myst init and I'm unable to enter or type anything and have to close the cli. NPM does show above.

[A screenshot of a computer program Description automatically generated]

From: Rowan Cockett @.> Sent: Wednesday, May 1, 2024 4:00 PM To: executablebooks/mystmd @.> Cc: VRConservation @.>; Author @.> Subject: Re: [executablebooks/mystmd] Unable to select or enter Yes when asked to run myst start (Issue #1176)

Very strange, thanks for the report. As a stop gap you can pass in myst init -y. After you init there shouldn't be any prompts for myst start or myst build.

Reply to this email directly, view it on GitHubhttps://github.com/executablebooks/mystmd/issues/1176#issuecomment-2088592206, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOTZCQZKGM3JIJBCP5AEXVDZAD7PRAVCNFSM6AAAAABHCA5OLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYGU4TEMRQGY. You are receiving this because you authored the thread.Message ID: @.@.>>

[rowanc1]

The current work around to this is to install using npm, the problem turns out to be in the python wrapper.

[rowanc1]

I am closing this to continue the tracking in #1425.

[VRConservation]

The current work around to this is to install using npm, the problem turns out to be in the python wrapper.

Thank you!