[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Simple isearch concerns
From: |
Eli Zaretskii |
Subject: |
Re: Simple isearch concerns |
Date: |
Sat, 10 Apr 2021 10:17:45 +0300 |
> Date: Fri, 09 Apr 2021 23:18:08 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: spacibba@aol.com, emacs-devel@gnu.org, juri@linkov.net
>
> +@vindex isearch-allow-motion
> +@vindex isearch-motion-changes-direction
> + Likewise, if you change the variable @code{isearch-allow-motion}
> +to a non-@code{nil} value, this enables the use of the keyboard motion
> +commands @kbd{M-<}, @kbd{M->}, @kbd{C-v} and @kbd{M-v}, to move
> +respectively to the first occurrence of the current search string in
> +the buffer, the last one, the first one after the current window,
> +and the last one before the current window. The search direction
> +does not change when these motion commands are used, unless you change
> +the variable @code{isearch-motion-changes-direction} to a non-@code{nil}
> +value.
This text doesn't explain how the search direction changes when
isearch-motion-changes-direction is non-nil. Also, the direction only
changes at BOB and EOB, right? IOW, C-v and M-v don't change the
direction, right? If so, the text leaves that unsaid.
> ++++
> +** New user options 'isearch-allow-motion' and
> +'isearch-motion-changes-direction'.
The heading should be a single line and a complete sentence, to
support reading in Outline mode. If needed, please reword to make it
short enough to fit a 80-column line.
> +(defcustom isearch-allow-motion nil
> + "Whether to allow movement between isearch matches by cursor motion
> commands.
> +If non-nil, the four motion commands `beginning-of-buffer', `end-of-buffer',
> +`scroll-up-command' and `scroll-down-command', when invoked during Isearch,
> +move respectively to the first occurrence of the current search string in the
> +buffer, the last one, the first one after the current window, and the last
> one
> +before the current window.
> +If nil, these motion commands normally exit Isearch and are executed.
> +See also the related option `isearch-allow-scroll'."
This odc string should also mention isearch-motion-changes-direction.
> +(defcustom isearch-motion-changes-direction nil
> + "Whether motion commands during incremental search change search direction.
> +If nil, the search direction (forward or backward) does not change when
> +motion commands are used during incremental search, except when wrapping."
This should explain how the direction changes when the value is
non-nil. It currently just says that the direction changes, but
doesn't say how.
Thanks.
- Re: Simple isearch concerns, (continued)
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/09
- Re: Simple isearch concerns, Eli Zaretskii, 2021/04/09
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/09
- Re: Simple isearch concerns, Eli Zaretskii, 2021/04/09
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/09
- Re: Simple isearch concerns, Eli Zaretskii, 2021/04/09
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/09
- Re: Simple isearch concerns, Eli Zaretskii, 2021/04/09
- RE: [External] : Re: Simple isearch concerns, Drew Adams, 2021/04/09
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/09
- Re: Simple isearch concerns,
Eli Zaretskii <=
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/10
- Re: Simple isearch concerns, Eli Zaretskii, 2021/04/10
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/10
- Re: Simple isearch concerns, Eli Zaretskii, 2021/04/10
- Now branch isearch-vertical, Ergus, 2021/04/10
- Re: Now branch isearch-vertical, Gregory Heytings, 2021/04/10
- Re: Simple isearch concerns, Juri Linkov, 2021/04/10
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/10
- Re: Simple isearch concerns, Eli Zaretskii, 2021/04/11
- Re: Simple isearch concerns, Gregory Heytings, 2021/04/11