From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Davis Herring Newsgroups: gmane.emacs.devel Subject: Re: Isearch interaction model Date: Thu, 1 Mar 2018 17:19:52 -0700 Organization: XCP-1 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 1519949986 3331 195.159.176.226 (2 Mar 2018 00:19:46 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 2 Mar 2018 00:19:46 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 Cc: Emacs developers , Juri Linkov To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 02 01:19:42 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 1erYQI-0000Ls-3p for ged-emacs-devel@m.gmane.org; Fri, 02 Mar 2018 01:19:42 +0100 Original-Received: from localhost ([::1]:59859 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1erYSK-0007cS-GG for ged-emacs-devel@m.gmane.org; Thu, 01 Mar 2018 19:21:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50721) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1erYRf-0007c8-CO for emacs-devel@gnu.org; Thu, 01 Mar 2018 19:21:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1erYRc-0005jo-5j for emacs-devel@gnu.org; Thu, 01 Mar 2018 19:21:07 -0500 Original-Received: from proofpoint7.lanl.gov ([204.121.3.46]:55154) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1erYRb-0005ig-SB for emacs-devel@gnu.org; Thu, 01 Mar 2018 19:21:04 -0500 Original-Received: from pps.filterd (proofpoint7.lanl.gov [127.0.0.1]) by proofpoint7.lanl.gov (8.16.0.21/8.16.0.21) with SMTP id w220IFK1006031; Thu, 1 Mar 2018 17:19:52 -0700 Original-Received: from mailrelay2.lanl.gov (mailrelay2.lanl.gov [128.165.4.103]) by proofpoint7.lanl.gov with ESMTP id 2gb7afejsh-1; Thu, 01 Mar 2018 17:19:52 -0700 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by mailrelay2.lanl.gov (Postfix) with ESMTP id A942EEFBC2E; Thu, 1 Mar 2018 17:19:52 -0700 (MST) X-NIE-2-Virus-Scanner: amavisd-new at mailrelay2.lanl.gov Original-Received: from bismuth.lanl.gov (bismuth.lanl.gov [128.165.246.103]) by mailrelay2.lanl.gov (Postfix) with ESMTP id 84A19EFBC25; Thu, 1 Mar 2018 17:19:52 -0700 (MST) In-Reply-To: Content-Language: en-US X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-01_13:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=809 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803020001 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 204.121.3.46 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:223207 Archived-At: > 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. But "repeating" a search for \_ as a non-regexp search is useless. > 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? I think the answer is to have one history which records the mode used for each search, so that it is reused correctly. (When it makes sense, the user can change the search mode after selecting the history element.) >> keeping toggled parameters in later searches? ...Which fits nicely with the idea that the parameters are "sticky" (either to a history element or to the user's current state). Davis -- This product is sold by volume, not by mass. If it appears too dense or too sparse, it is because mass-energy conversion has occurred during shipping.