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 #206 received at 69097 <at> debbugs.gnu.org (full text, mbox):
> From: Sean Whitton <spwhitton <at> spwhitton.name>
> Cc: philipk <at> posteo.net, stefankangas <at> gmail.com, acorallo <at> gnu.org,
> juri <at> linkov.net, rms <at> gnu.org, 69097 <at> debbugs.gnu.org
> Date: Fri, 06 Sep 2024 14:54:58 +0100
>
> +(defun forward-unix-word (arg &optional delim)
> + "Move forward ARG unix-words.
> +A unix-word is whitespace-delimited.
> +Interactively, ARG is the numeric prefix argument, defaulting to 1.
> +A negative ARG means go backwards to the beginning of unix-words.
I again ask whether we need this command. It is okay to have a
function (perhaps even an internal one) to move by Unix-words, but
what are the use cases for such a command?
> +(defun unix-filename-rubout (arg)
> + "Kill ARG unix-words backwards, also treating `/' as whitespace.
> +A unix-word is whitespace-delimited.
> +Interactively, ARG is the numeric prefix argument, defaulting to 1.
> +A negative ARG means to kill forwards.
> +
> +This is like `unix-word-rubout' (which see), but `/' is also considered
> +whitespace.
I'd say '/' is treated as word delimiter. "Considered whitespace"
sounds strange to me.
Should we also treat a backslash as delimiter, for MS-Windows?
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.