GNU bug report logs - #49194
kill-whole-line 'plus-newline-even-if-none-in-reality

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 49194 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: bug#49194: kill-whole-line 'plus-newline-even-if-none-in-reality
Date: Thu, 24 Jun 2021 21:51:42 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: jidanni <at> jidanni.org,  49194 <at> debbugs.gnu.org
> Date: Thu, 24 Jun 2021 20:46:37 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > AFAIU, what the OP wants already happens: the newline is saved in
> > kill-ring together with the line, and is yanked back with C-y.  So I
> > don't think I understand the request.
> 
> He wants to kill the final line in a buffer (that might not have a
> newline character at the end), but end up with a string in the kill ring
> that does have a newline at the end.

That makes no sense to me: the command kills a line of buffer text, it
doesn't (and shouldn't) invent characters out of thin air.  When there
_is_ a newline at EOL, setting kill-whole-line will cause C-k to kill
that newline as well; but if there's no newline there, why should this
particular command with that option invent such a newline and save it
in kill-ring?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.