On Sun, 4 Feb 2024 at 15:17, Koichi Murase <myoga.mur...@gmail.com> wrote:
> 2024年2月4日(日) 12:59 Martin D Kealey <mar...@kurahaupo.gen.nz>: > > I am generally concerned about breaking changes that affect existing > scripts, but I see changes to readline as less problematic, > > I also assume shell scripts, but shell scripts for interactive settings. > Interactive settings can also be a large-scale shell script. That is a possibility that I hadn't considered. Thankyou for bringing it to my attention. > On reflection, this would be a fair compromise, at least in the short > term. > > Does it need to be short-term? Do we need to remove the feature? > Not necessarily; I just hadn't thought it through enough to convince myself that it should necessarily remain, so I didn't want to commit to the long term. > Might we offer guidance that distros include a new binding for M-C-e in > their supplied /etc/skel which would only affect new users, not existing > users? > > I have a native question. Why do people on this thread discuss changing > the behavior of "\M-\C-e" even though there is still a large space of key > combinations? "\M-\C-e" is already used [lots of places...] > I don't see a reason to introduce unnecessary conflicts when we can just > pick another key combination (e.g. "\M-\C-x") for > `shell-expand-and-requote-line'. > When you put it like that, it seems entirely reasonable that M-C-e should remain as-is. Consider all my previous suggestions to the contrary withdrawn. -Martin PS: Sadly M-C-r seems to be already taken, so I can't just hop one key over.
