-
Notifications
You must be signed in to change notification settings - Fork 701
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
Ask about (or at least signpost!) init --interactive #7100
Comments
👍 This should be an easy PR to do the "bare minimum" -- care to go for it? |
I'd argue that Consequently, since using For completeness, as you know there was quite a bit of controverisal discussion in #5902 which motivated for better or worse switching |
I would be more in favor of switching to back to interactive by default, and providing a note that tells you how to switch off the flag. Having non-interactive be the default is incredibly onerous to me because of the two contrasting workflows. Suppose each flag leaves a note about turning on/off their contrasting flag:
And for the record, yes i did switch the To get back on topic, I think as far as action items go, yes, leaving a note is better than the status quo. But i would like to reopen the discussion about whether that work is necessary in the first place. |
I believe that init is now back to interactive by default, so closing on that basis? |
Yes, it is, in 3.6. |
Wait, this doesn't appear to be the case in 3.6 after all? I'm very confused. |
@gbaz: you are right, I mixed up Edit: which, if it's right, probably means we should close this. But better to compile and check |
ok, just checked master and indeed its changed on master. closing again :-) |
I'm finding
cabal init
defaulting to non interactive insanely frustrating, particularly because there's no indication for users of how to get the interactive behavior. No note when the init happens, no documentation incabal --help
.If you want to, say, init a library, and don't have all the required fields memorized, you probably want to use "--interactive". This is a basic need. Making basic tinkering with libraries more difficult just creates a subclass of users who are unable to contribute.
What I think is best
Bare minimum
The text was updated successfully, but these errors were encountered: