Re: kill-whole-line = always
-- "Gary D. Foster" <Gary.Foster(a)corp.sun.com> spake thusly:
FWIW, I use it as "kill to the end of the line" all the
time. I do a
large amount of text editing and writing, as well as programming.
When I want to kill the entire line instead of to the end of the
line, I just C-A before C-K.
Just piping up because I don't see a lot of people stating that they
use the "kill to end of line" very much. I'm perfectly content with
the behavior being controlled by a variable, I'm also content with
adding keybindings. I'm not too keen on changing a current
keybinding, but I'm not totally opposed to the idea, I'll just have
to teach my fingers to do things differently.
I don't think Ben was advocating getting rid of the kill-whole-line
variable altogether, just getting rid of the kill-whole-line = always
feature. To clarify, there are six possible scenarios (if you ignore
using kill-line on a blank line, which always just kills it):
kill-whole-line position in line kills
nil beginning to end of line
nil middle to end of line
t beginning whole line
t middle to end of line
'always beginning whole line
'always middle while line
As I understand it (and please correct me if I'm wrong), Ben is simply
suggesting getting rid of the last two lines in that table. I don't
care one way or the other because I have kill-whole-line set to t, not
'always.
Attachments:
- attachment.sig (application/pgp-signature — 232 bytes)