GNU bug report logs -
#69097
[PATCH] Add 'kill-region-or-word' command
Previous Next
Reported by: Philip Kaludercic <philipk <at> posteo.net>
Date: Tue, 13 Feb 2024 09:57:02 UTC
Severity: normal
Tags: patch
Done: Sean Whitton <spwhitton <at> spwhitton.name>
Bug is archived. No further changes may be made.
Full log
Message #152 received at 69097 <at> debbugs.gnu.org (full text, mbox):
> From: Robert Pluim <rpluim <at> gmail.com>
> Cc: philipk <at> posteo.net, rms <at> gnu.org, 69097 <at> debbugs.gnu.org,
> juri <at> linkov.net, stefankangas <at> gmail.com, acorallo <at> gnu.org,
> spwhitton <at> spwhitton.name
> Date: Tue, 03 Sep 2024 16:55:29 +0200
>
> +(defcustom kill-word-if-no-region nil
> + "Behaviour when `kill-region' is invoked without an active region.
> +If set to nil (default), then an error occurs and nothing is killed. If
> +set to `emacs-word', then kill a the last word as defined by the current
> +major mode. If set to `unix-word', then kill the last word in the style
> +of a shell like Bash, disregarding the major mode. If set to a
> +function, call that function."
> + :type '(choice (const :tag "Kill a word like `backward-kill-word'" emacs-word)
> + (const :tag "Kill a word like Bash would" unix-word)
> + (const :tag "Do not kill anything" nil)
> + (symbol :tag "User function")
> + :group 'killing)
When and why would this be useful?
Since kill-region cannot be customized in this way, I wonder why this
new functionality should. If someone wants to replace kill-region
with their own function, they can always redefine it or advise it, no?
This bug report was last modified 243 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.