From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 49194@debbugs.gnu.org
Subject: bug#49194: kill-whole-line 'plus-newline-even-if-none-in-reality
Date: Fri, 25 Jun 2021 04:20:50 +0800 [thread overview]
Message-ID: <874kdnnhel.5.fsf@jidanni.org> (raw)
In-Reply-To: <87tuloegsa.5.fsf@jidanni.org>
>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
EZ> That makes no sense to me: the command kills a line of buffer text, it
EZ> doesn't (and shouldn't) invent characters out of thin air. When there
EZ> _is_ a newline at EOL, setting kill-whole-line will cause C-k to kill
EZ> that newline as well; but if there's no newline there, why should this
EZ> particular command with that option invent such a newline and save it
EZ> in kill-ring?
1. There may not be a newline yet, but there will be upon sending the
message, or saving the file, depending on other settings.
2. That allows consistent yanking later. C-k ... C-y now will always
have a newline. Else even though C-k appears to behave the same at the
end of file, C-y depends different later.
Anyway, just try making a bunch of lines like this:
^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^
at the end of your reply, without extra fuss when copying the first!
next prev parent reply other threads:[~2021-06-24 20:20 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
2021-06-24 20:20 ` 積丹尼 Dan Jacobson [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kdnnhel.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=49194@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.