unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: pent <pent@aparamon.msk.ru>,
	rfrancoise@debian.org, 3755@debbugs.gnu.org,
	3754@debbugs.gnu.org
Subject: bug#3754: bug#3755: 23.0.95; Wish: please provide kill-whole-visual-line function
Date: Wed, 18 Nov 2020 18:31:26 -0800	[thread overview]
Message-ID: <CADwFkmmMQfc2gPKoR=_ij==V4h=fjGDN1+RFKSW3=_fC+Cbf8g@mail.gmail.com> (raw)
In-Reply-To: <87sgodajaz.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 30 Sep 2019 17:35:32 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> pent <pent@aparamon.msk.ru> writes:
>
>> The new Emacs provides function kill-visual-line, which is bound to
>> C-k in Visual Lines Mode. It would be nice if Emacs also provided
>> function kill-whole-visual-line similar to kill-whole-line, bound to
>> C-S-backspace in Visual Lines Mode:
>>
>> (kill-whole-visual-line &optional arg)
>
> (I'm going through old bug reports that unfortunately didn't get any
> response at the time.)
>
> That seems like a logical addition, but I wonder whether there may be
> users who are used to `C-S-backspace' killing the entire physical line
> in visual line mode, too.
>
> The utility of having that keystroke killing just the visual line seems
> limited -- that functionality is already as `C-a C-k', which is about as
> many keys, while having `C-S-backspace' do that it does now seems more
> useful.
>
> So I'm inclined to not alter the behaviour here.  Anybody got an
> opinion?

Yeah, I tend to agree with you.  So is this a wontfix?





  reply	other threads:[~2020-11-19  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-04 20:37 bug#3755: 23.0.95; Wish: please provide kill-whole-visual-line function pent
2019-09-30 15:35 ` bug#3754: " Lars Ingebrigtsen
2020-11-19  2:31   ` Stefan Kangas [this message]
2020-11-24  5:55     ` Lars Ingebrigtsen

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='CADwFkmmMQfc2gPKoR=_ij==V4h=fjGDN1+RFKSW3=_fC+Cbf8g@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=3754@debbugs.gnu.org \
    --cc=3755@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=pent@aparamon.msk.ru \
    --cc=rfrancoise@debian.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).