Default 'Y' on confirm() is a bad default and breaking change.

@littledivy I don't see anything about defaulting to Y in the linked issues. I wouldn't conceptualize the reverted behavior as "defaulting" to Y (the default if !isatty is still false); rather, it's mirroring in-browser behavior by registering an Enter keypress as true.

@lionel-rowe we'll be more than happy to give it another go, but we probably should improve it using low level APIs and not relying on rustyline crate.

@bartlomieju sure, I'll probably take another crack at it sometime, but not sure when. Possibly rustyline can be customized sufficiently; if not, using low-level APIs for prompt would likely require re-implementing a decent chunk of rustyline's functionality (consider line wrapping, including double/zero-width characters, cross-platform compat, handling of copied/pasted text, navigation with arrow keys, various modifier keys, etc.)

I wouldn't conceptualize the reverted behavior as "defaulting" to Y

I agree with that after seeing how other CLIs handle confirm. It was a breaking change nonetheless, It changed behaviour of a project creation tool I was using where I usually hold enter all the way to respond "n". I wouldn't block any work on this for this reason though.