GNU bug report logs - #38392
zap-up-to-char should appear in "Deletion and Killing" Emacs info section and "Command Index"

Previous Next

Package: emacs;

Reported by: Justin Paston-Cooper <paston.cooper <at> gmail.com>

Date: Tue, 26 Nov 2019 19:37:02 UTC

Severity: normal

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #32 received at 38392 <at> debbugs.gnu.org (full text, mbox):

From: Justin Paston-Cooper <paston.cooper <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 38392 <at> debbugs.gnu.org
Subject: Re: bug#38392: zap-up-to-char should appear in "Deletion and Killing"
 Emacs info section and "Command Index"
Date: Wed, 27 Nov 2019 17:05:41 +0100
What about near, through and far?

On Wed, 27 Nov 2019 at 17:04, Drew Adams <drew.adams <at> oracle.com> wrote:
>
> > What about having a class of inclusivity modifiers of the form `C-I
> > element` (I is isomorphic to set of inclusivities {before, through,
>                                                      ^^^^^^
> > after}),
>   ^^^^^
> > element is either RET for defining inclusivity alone, or a
> > `regexp RET` for including a certain pattern, similar to C-u, which
> > would pass an argument to things like C-f, C-b, C-s and do the
> > appropriate?
>
> Just a comment about "before" and "after":
>
> Those terms should be used only if the functionality
> really does proceed in a particular buffer direction.
>
> For example, the proposed Isearch commands I
> mentioned, which have names with "through", can
> work in either forward or backward direction, so
> in their case "after" or "before" would be wrong,
> for the command name.




This bug report was last modified 5 years and 230 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.