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: Some further ideas for Isearch Date: Sun, 25 Apr 2021 20:36:25 +0300 Organization: LINKOV.NET Message-ID: <87h7jul2va.fsf@mail.linkov.net> References: <87pmyisrlw.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2732"; 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: emacs-devel@gnu.org To: Augusto Stoffel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 25 19:49:24 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 1laism-0000Yk-PN for ged-emacs-devel@m.gmane-mx.org; Sun, 25 Apr 2021 19:49:24 +0200 Original-Received: from localhost ([::1]:43176 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1laisl-0006gu-Q4 for ged-emacs-devel@m.gmane-mx.org; Sun, 25 Apr 2021 13:49:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43250) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lairN-0005Qr-UN for emacs-devel@gnu.org; Sun, 25 Apr 2021 13:48:01 -0400 Original-Received: from relay1-d.mail.gandi.net ([217.70.183.193]:15993) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lairH-0007yr-Mv for emacs-devel@gnu.org; Sun, 25 Apr 2021 13:47:57 -0400 X-Originating-IP: 91.129.102.166 Original-Received: from mail.gandi.net (m91-129-102-166.cust.tele2.ee [91.129.102.166]) (Authenticated sender: juri@linkov.net) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id 48EB9240005; Sun, 25 Apr 2021 17:47:47 +0000 (UTC) In-Reply-To: <87pmyisrlw.fsf@gmail.com> (Augusto Stoffel's message of "Sun, 25 Apr 2021 10:20:11 +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.01, RCVD_IN_MSPIKE_WL=-0.01, 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:268402 Archived-At: > Here are some further ideas for Isearch, partially inspired by the > alternative buffer search packages out there: Thanks for more ideas that hopefully will find a path to isearch. > Future history > -------------- > > Pressing `C-s M-n M-n ...' could present a few useful search > candidates, controlled for instance by the > `isearch-forward-thing-at-point' variable. This would be more > flexible and more mnemonic than the recently introduced > `isearch-forward-thing-at-point' command. The problem is that the isearch history is a ring, so maybe the users already expect that typing 'C-s M-n' should get the top element of the isearch ring. This is what 'M-n' bound to 'isearch-ring-advance' currently does to search for the next item in the search ring. > Resume canceled searches > ------------------------ > > `C-s C-s' recovers the last history element, so it's more or less > equivalent to `C-s M-p'. It would be nice to have the ability to > resume a canceled search, i.e., make `C-s C-s' look into > `isearch-cmds' instead. This feature was proposed in https://debbugs.gnu.org/11378#71 > Fuzzy search > ------------ > > By this I mean a search mode where `search-whitespace-regexp' is set > to ".*?". > > Implementing this wouldn't be completely trivial because, unlike case > sensitivity, the whitespace laxness settings are not local to each > Isearch session. (As a quick check, note that `M-s c' changes > case-sensitivity for the current search only, but `M-s SPC' changes > whitespace laxness for future searches as well.) > > The whitespace regexp should also be saved as a property in the > search-ring elements. As the first step, this regexp could be added as a new option to the search-whitespace-regexp defcustom. Then later `M-s SPC' could cycle between different options. > Whole words vs lax whitespace > ----------------------------- > > The word search mode (M-s w) does two things at once: it wraps the > search string around "\\< ... \\>" and treats whitespace as "\\W+". It > would be nice to make these two aspects orthogonal. > > Sometimes, one might want to search whole words with literal spaces. > Much more often, however, one might want "\\W+" whitespace but not the > whole-word restriction. > > I'm not sure what a good UI would be, but one idea is to make `M-s SPC' > cycle between a few useful whitespace regexps (e.g., nil, "\\s-+", > "\\W+" and ".*?"). Maybe not `M-s SPC', but `M-s w' could cycle between different versions of 'word-search-regexp' assigned to 'isearch-regexp-function'?