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: Thu, 29 Apr 2021 00:11:41 +0300 Organization: LINKOV.NET Message-ID: <87fsza5c5e.fsf@mail.linkov.net> References: <87pmyisrlw.fsf@gmail.com> <87h7jul2va.fsf@mail.linkov.net> <87czuh1uhg.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="37576"; 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 Wed Apr 28 23:37:38 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 1lbrsI-0009gR-22 for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Apr 2021 23:37:38 +0200 Original-Received: from localhost ([::1]:57946 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lbrsF-0001hV-Q4 for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Apr 2021 17:37:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58460) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lbrnt-00075D-8s for emacs-devel@gnu.org; Wed, 28 Apr 2021 17:33:06 -0400 Original-Received: from relay1-d.mail.gandi.net ([217.70.183.193]:8437) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lbrnn-0005Nz-Ho for emacs-devel@gnu.org; Wed, 28 Apr 2021 17:33:05 -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 78067240005; Wed, 28 Apr 2021 21:32:54 +0000 (UTC) In-Reply-To: <87czuh1uhg.fsf@gmail.com> (Augusto Stoffel's message of "Mon, 26 Apr 2021 07:32:27 +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:268590 Archived-At: >> This is what 'M-n' bound to 'isearch-ring-advance' currently does >> to search for the next item in the search ring. > > But the top element is the oldest, the next one to be forgotten, right? > Why would this be remotely as interesting than first seeing the region, > word, symbol, sexp at point? Indeed, it would be nice to have 'C-s M-n' to get the next thing at point. > Speaking of the search ring(s): Now that the search mode is saved as > properties in the history elements, can we get rid of separate histories > for regexp and regular searches? The value of isearch-regexp is not saved as a property in the history. > I see at least two reasons for this: > > - If you use regexp search by default, it's very annoying to resume a > previous symbol-at-point search. Please elaborate. Do you rebind C-s to isearch-forward-regexp, then after using isearch-forward-symbol, can't repeat it with C-s? Does something like this do the right thing for you? (defvaralias 'regexp-search-ring 'search-ring) > - Given one regexp and one literal history item, you can't know which is > oldest. > > Now, of course you are going to say this needs to be a defcustom, so > I'm already going to ask: can it be on by default? Changing the default is a very sensitive topic.