From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: Simple isearch concerns Date: Tue, 06 Apr 2021 22:11:13 +0300 Organization: LINKOV.NET Message-ID: <875z0zw9hq.fsf@mail.linkov.net> References: <20210403001539.x4rb55dvh46rmhb3.ref@Ergus> <20210403001539.x4rb55dvh46rmhb3@Ergus> <878s5wmsjp.fsf@mail.linkov.net> <87pmz8h0sn.fsf@mail.linkov.net> <20210405223743.omtkzgomchz4o4ly@Ergus> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2619"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: Drew Adams , "emacs-devel@gnu.org" To: Ergus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Apr 06 21:26:04 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 1lTrKu-0000Ys-Gf for ged-emacs-devel@m.gmane-mx.org; Tue, 06 Apr 2021 21:26:04 +0200 Original-Received: from localhost ([::1]:45898 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lTrKt-0003Qi-GC for ged-emacs-devel@m.gmane-mx.org; Tue, 06 Apr 2021 15:26:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43310) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lTrHp-0008LM-Gi for emacs-devel@gnu.org; Tue, 06 Apr 2021 15:22:53 -0400 Original-Received: from relay1-d.mail.gandi.net ([217.70.183.193]:59665) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lTrHm-0004KI-0Q for emacs-devel@gnu.org; Tue, 06 Apr 2021 15:22:53 -0400 X-Originating-IP: 91.129.107.223 Original-Received: from mail.gandi.net (m91-129-107-223.cust.tele2.ee [91.129.107.223]) (Authenticated sender: juri@linkov.net) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id 6B628240002; Tue, 6 Apr 2021 19:22:45 +0000 (UTC) In-Reply-To: <20210405223743.omtkzgomchz4o4ly@Ergus> (Ergus's message of "Tue, 6 Apr 2021 00:37:43 +0200") Received-SPF: pass client-ip=217.70.183.193; envelope-from=juri@linkov.net; helo=relay1-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:267490 Archived-At: > Is it possible to make this in a way that some commands could be bound > in a way that the prefix M-s won't be needed sometimes when isearch is > active? (I mean a custom option of course) > > That could be more handy for some users. Because `M-s C-RET` is not > faster than `C-r RET`. > > The same applies to `M-s M-<` and `M-s M->`. And maybe for some future > commands like the ones Gregory mentioned some days ago like go to > candidate outside visible the page and so on in M-v and C-v. > > Maybe we can add a map with some extra commands and then bind the map > in the isearch-mode-map with and without prefix conditionally? Does it > makes sense?. I already bound them to shorter keys because `M-s M-<` is harder to type: (define-key isearch-mode-map "\M-<" 'isearch-beginning-of-buffer) (define-key isearch-mode-map "\M->" 'isearch-end-of-buffer) The problem is that by default most keys including `M-<` should exit isearch. But maybe when search-exit-option is customized to nil, or when isearch-allow-scroll is customized to 'unlimited', or when the third option added by Gregory isearch-allow-match-scroll is customized to t, then remap motion commands to navigate isearch matches. Should then forward-char be remapped to isearch-repeat to go to the next match? Then also remap next-line to go to the next line with matches, etc. The logic should be quite simple: isearch-allow-scroll could have a new option similar to 'unlimited'. Let's name it 'sync'. It should allow typing a motion key, then afterwards it will call isearch-repeat to find the next match after moving to new location.