From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Simple isearch concerns Date: Sat, 10 Apr 2021 10:17:45 +0300 Message-ID: <83a6q67gme.fsf@gnu.org> References: <20210403001539.x4rb55dvh46rmhb3.ref@Ergus> <20210403001539.x4rb55dvh46rmhb3@Ergus> <878s5wmsjp.fsf@mail.linkov.net> <87mtubz4ls.fsf@mail.linkov.net> <8735w22s9b.fsf@mail.linkov.net> <3ec7e2e58a3733a48ae9@heytings.org> <878s5tc0rn.fsf@mail.linkov.net> <3ec7e2e58a49d4f0ec99@heytings.org> <878s5t9p1i.fsf@mail.linkov.net> <9ff81b52fad2911cc740@heytings.org> <87im4w1tgw.fsf@mail.linkov.net> <9ff81b52fa878cb35a86@heytings.org> <87pmz4zgn5.fsf@mail.linkov.net> <83eefk802u.fsf@gnu.org> <871rbjdea4.fsf@mail.linkov.net> <8335vz91en.fsf@gnu.org> <940751cee594ef1cf8a4@heytings.org> <83zgy77hep.fsf@gnu.org> <940751cee566285b8519@heytings.org> <83wntb7eli.fsf@gnu.org> <940751cee50d69f2231d@heytings.org> <83r1jj7bhg.fsf@gnu.org> <940751cee5acf0f913df@heytings.org> <83eefj705i.fsf@gnu.org> <940751cee53181aedd72@heytings.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21130"; mail-complaints-to="usenet@ciao.gmane.io" Cc: spacibba@aol.com, juri@linkov.net, emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 10 09:18:49 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lV7tJ-0005Oc-0k for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Apr 2021 09:18:49 +0200 Original-Received: from localhost ([::1]:44254 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lV7tI-0001KE-2S for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Apr 2021 03:18:48 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54298) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lV7sZ-0000sZ-VV for emacs-devel@gnu.org; Sat, 10 Apr 2021 03:18:03 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:40740) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lV7sX-00078U-Pn; Sat, 10 Apr 2021 03:18:01 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1192 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lV7sW-0000vb-VN; Sat, 10 Apr 2021 03:18:01 -0400 In-Reply-To: <940751cee53181aedd72@heytings.org> (message from Gregory Heytings on Fri, 09 Apr 2021 23:18:08 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:267773 Archived-At: > Date: Fri, 09 Apr 2021 23:18:08 +0000 > From: Gregory Heytings > 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.