they're legacy by definition of being pre-existing users. if you're used to that setting, you have a legacy of using it a new user would not expect git bash to

they're legacy by definition of being pre-existing users. if you're used to that setting, you have a legacy of using it a new user would not expect git bash to have shift-insert as paste, and that is an unnecessary inconvenience, especially considering that git bash is more the rule than the exception in doing this, with a variety of different routes to the same goal I think they should be opt-in instead of opt-out or forced. standards save time and energy and they should be respected, especially in something so common, especially if the legacy alternatives are so easily maintained