From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Isearch interaction model Date: Thu, 1 Mar 2018 16:12:13 -0800 Message-ID: References: <87po4slrg4.fsf@mail.linkov.net> <2854ae14-ad4a-2fa2-ff0f-652e1501819e@dancol.org> <87fu5jh14h.fsf_-_@mail.linkov.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1519949431 7023 195.159.176.226 (2 Mar 2018 00:10:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 2 Mar 2018 00:10:31 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 Cc: Emacs developers To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 02 01:10:26 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1erYHK-0001Ad-0B for ged-emacs-devel@m.gmane.org; Fri, 02 Mar 2018 01:10:26 +0100 Original-Received: from localhost ([::1]:59840 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1erYJM-0005yc-5x for ged-emacs-devel@m.gmane.org; Thu, 01 Mar 2018 19:12:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45861) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1erYJG-0005yF-4y for emacs-devel@gnu.org; Thu, 01 Mar 2018 19:12:27 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1erYJC-0004jw-Qx for emacs-devel@gnu.org; Thu, 01 Mar 2018 19:12:26 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:45166) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1erYJC-0004iG-Gr for emacs-devel@gnu.org; Thu, 01 Mar 2018 19:12:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=qksNEN3LJx5/b8TAlWzZLeqJ27hCdS9GD1oBMtK7jNI=; b=YVNP6W0U91lbETP0AGdDV+MwrZkSZzKY8k2IyalFyOSOgrVxgqGy4q3QxiVYUbb7EuHZVKVEzDzTiD42qUjPglIbL8ctLL09FwCJIwkaxCEywzG/gqRjIfv9hYSa2yU0Vee7PvAghTW/A+fyxOCbhO9NEDXQ7W0KsUjaM5tRaT4PL0SWkAGlKxNsm4bWQlvPfHwrTsBWEw+T1YmOMwvcUJ4GueN1sxxcJJQtIMFpTclsOmTvENqsN71odM8v8MSDW5hBoiW4nWJIGOghEQcXXxO/jjagoXGpevmORiJHSYZYruo1LzwQ3Ugsq8+jW0XfrjU2ONs5WQxRsjhmsO/c3w==; Original-Received: from [172.92.145.124] (helo=[192.168.86.27]) by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1erYJB-0004pB-6C; Thu, 01 Mar 2018 16:12:21 -0800 In-Reply-To: <87fu5jh14h.fsf_-_@mail.linkov.net> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:223206 Archived-At: On 03/01/2018 02:39 PM, Juri Linkov wrote: >> Thanks. I'm looking for ways we can tweak the existing default interaction >> model, but I think we should take a broader look at how isearch works in >> the first place. IMHO, find-and-replace should be more closely integrated >> into isearch, > > I believe we could arrive to this goal gradually by adding more isearch > features to query-replace, and query-replace features to isearch, > i.e. like digging a tunnel from both ends to meet in the middle. Right. It should be easy to switch between isearch and query-replace. > As one of first simplest steps we could try to sync their keybindings > as much as possible, e.g. to add: > > (define-key query-replace-map "\C-s" 'skip) > (define-key query-replace-map "\C-r" 'backup) > (define-key query-replace-map "\M-e" 'edit-replacement) (y) > ... > >> we should have a unified history for regular and regex search, > > Not sure about this, I thought more in the direction of adding separate > histories for word search, symbol search, to be able to repeat the last > search of the same type. Why do you think histories should be shared? "What" versus "how". We have a search history because it's often the case that we want to repeat something we've recently done --- look up the same word, find the same function, and so on. It doesn't make sense to me that the exact mechanism we use to search for a particular thing should affect its recency or the way in which we recall it. It's very easy already to casually switch between literal and regex isearch with M-r. Why should this distinction affect the way in which we recall that search? >> and case-sensitivity, symbol-granularity, regex mode, etc. should all >> be independently toggleable peer flags. > > Do you mean customizing default search parameters, or keeping toggled > parameters in later searches? Both.