> I noticed that ~C stopped working in my -current, from last Saturday, > holding the message "commandline disabled". The rest of the ~-escapes > work tho, and ~C is no longer present in ~?. Went to check the code, > currenlty sitting on Git commit e0b284df3ba7772329d85f200545e3bc5a84d54e > only to find out that there are no instances of that message in it. A > `make` later, the "classic" behaviour is restored.
There is a patch being tested, which will probably land soon because the experiment in the community has gone very well. It took almost 2 weeks for anyone in snapshots to notice, so this proves how few people are using a set of features. We have good reason to collect facts from the community because there are often people who are outraged, OUTRAGED, when a feature goes away or changes. > 1. For how long this experiment is going to last? Is there a way to > disable it? I tried with `permitlocalcommand=yes` with no success. A new "enablecommandline" configuration option re-enables those particular features, and the diff later on will show why we feel these features should be optional. That configuration option is also the snapshot diff, so you can use it right away. > 2. Can I see the patch? And more generally, is there a way to know of > this experiments other than running into them? Sometimes you can see the patch on a list. This one isn't being handled that way. There is no firm rule. We could do it a different way, by always commiting them first. And then if they break things backing them out. Annoying and painful churn. This is a simply different process of getting diffs tested.
