Re: Not yet: kill-whole-line = always

steve, from what i gather, the people who use M-k are all experienced users, and can trivially find where kill-sentence has moved and change my M-shift-K binding to M-k. novices, on the other hand, are never going to be aware of any kill-whole-line functionality unless it's in an obvious location. if a change like this is well announced and documented, it should cause hardly any pain. imho we have to put a limit on the amount of contortions we're going to make to avoid changing any existing key bindings. it is late, though, and you have a point. a third alternative would be: remove kill-whole-line = always remove historical-kill-line create kill-whole-line function, not bound to any keys. sample.init.el binds it to M-k and moves kill-sentence to M-K [shift k]. PROVIDED THAT we go ahead and do the movement suggested in sample.init.el in the next development branch. that way, there will be time for people to get used to the bindings, and propose alternative solutions. [provided that the solutions take everything into account, not just a Kyle-type "don't you dare change that binding because i like it where it is and don't want it moved" type of curmudgeonly response.] sound good? "Stephen J. Turnbull" wrote: -- ben I'm sometimes slow in getting around to reading my mail, so if you want to reach me faster, call 520-661-6661. See http://www.666.com/ben/chronic-pain/ for the hell I've been through.