From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49194@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#49194: kill-whole-line 'plus-newline-even-if-none-in-reality
Date: Thu, 24 Jun 2021 21:51:42 +0300 [thread overview]
Message-ID: <83tulnrt8h.fsf@gnu.org> (raw)
In-Reply-To: <87im23f6cy.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 24 Jun 2021 20:46:37 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: jidanni@jidanni.org, 49194@debbugs.gnu.org
> Date: Thu, 24 Jun 2021 20:46:37 +0200
>
> Eli Zaretskii <eliz@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?
next prev parent reply other threads:[~2021-06-24 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 15:34 bug#49194: kill-whole-line 'plus-newline-even-if-none-in-reality 積丹尼 Dan Jacobson
2021-06-24 16:11 ` Lars Ingebrigtsen
2021-06-24 17:59 ` 積丹尼 Dan Jacobson
2021-06-24 18:26 ` Lars Ingebrigtsen
2021-06-24 18:42 ` 積丹尼 Dan Jacobson
2021-06-24 18:42 ` Eli Zaretskii
2021-06-24 18:46 ` Lars Ingebrigtsen
2021-06-24 18:51 ` Eli Zaretskii [this message]
2021-06-24 20:20 ` 積丹尼 Dan Jacobson
2021-06-25 6:01 ` Eli Zaretskii
2021-06-25 14:02 ` Lars Ingebrigtsen
2021-06-25 14:03 ` Eli Zaretskii
2021-06-26 17:12 ` 積丹尼 Dan Jacobson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tulnrt8h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49194@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).