all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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:42:56 +0300	[thread overview]
Message-ID: <83v963rtn3.fsf@gnu.org> (raw)
In-Reply-To: <87mtrff7ao.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu,  24 Jun 2021 20:26:23 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 24 Jun 2021 20:26:23 +0200
> Cc: 49194@debbugs.gnu.org
> 
> 積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
> 
> > No. I'm just saying that a bonus newline should be added to what gets
> > copied (so later, upon C-y, it is present.)
> 
> I think that sounds like really surprising behaviour, but I guess if
> it's hidden behind a new `kill-whole-line' value, I guess I don't have
> any objections to adding it.  Any other opinions?

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.





  parent reply	other threads:[~2021-06-24 18:42 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 [this message]
2021-06-24 18:46         ` Lars Ingebrigtsen
2021-06-24 18:51           ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83v963rtn3.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 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.