brandon s allbery kf8nh

From experience (testing xmonad stuff at the repl), the answer to (4) is "no".

I was under the impression this feature is still somewhat experimental, and its further evolution depends on what early adopters find they would benefit from. So it could go either...

We've already retroactively edited release notes: https://github.com/haskell/cabal/pull/10134 I also note that we (deliberately) point people to the changelog files in `master` in preference to pregenerated files, e.g. on Hackage. In...

While `cabal check` should certainly check that names are valid for Hackage, this also points up that it's not the early 2000s any more: Hackage should probably accept UTF-8 these...

Yes, I figured that part, but plain ASCII is hard to defend in a Unicode world.

I think that change will be so invasive as to piss off a whole bunch of downstreams. I'm surprised we only got one major complaint about https://github.com/haskell/cabal/pull/9718, which was small...

I suspect the biggest problem will be getting it actually done; might require HF funding, _will_ require getting someone to actually do it. And yeh, `process` will definitely be a...

1. If you're using `tar`, you're using POSIX. 2. POSIX limits less than you think: only `NUL` and `/` are special. You can even use e.g. BIG5 with it. It's...

My own suggestions would be: 1. interactive can stay default _but_ should have only one question, what kind of project. (I do agree that the current default is a bad...

Right, I don't see either one affecting caching, so this should be okay modulo their not being part of the things we currently initialize from `cabal.project(.local)`.