From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Jean-Christophe Helary Newsgroups: gmane.emacs.help Subject: Re: killing the result of isearch Date: Fri, 10 Nov 2017 22:11:30 +0900 Message-ID: <2348DA86-8BEF-46E5-A19D-DE8306D47D95@gmail.com> References: <433bd3d0-a506-4d89-9d10-dcbfb0e23be0@default> <852BAA28-2A50-4AD9-B8D6-9F06905A4395@gmail.com> <87r2tava5x.fsf@hornfels.zedat.fu-berlin.de> <87y3nigy86.fsf@hornfels.zedat.fu-berlin.de> <87wp32f7os.fsf@hornfels.zedat.fu-berlin.de> <29AEE45F-D0CA-442F-8F46-E290C40782B4@gmail.com> <87k1z02yth.fsf@fliptop> <4EA90B44-DF92-43C3-B8D0-6C42D1D6F1DA@gmail.com> <87h8u32kw6.fsf@fliptop> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: blaine.gmane.org 1510320956 567 195.159.176.226 (10 Nov 2017 13:35:56 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 10 Nov 2017 13:35:56 +0000 (UTC) To: Help Gnu Emacs mailing list Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Nov 10 14:35:49 2017 Return-path: Envelope-to: geh-help-gnu-emacs@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 1eD9TH-0008Ao-S3 for geh-help-gnu-emacs@m.gmane.org; Fri, 10 Nov 2017 14:35:48 +0100 Original-Received: from localhost ([::1]:41762 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eD9TN-0008E4-Dm for geh-help-gnu-emacs@m.gmane.org; Fri, 10 Nov 2017 08:35:53 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eD9Sg-00089n-UQ for help-gnu-emacs@gnu.org; Fri, 10 Nov 2017 08:35:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eD9Sc-0007OR-MN for help-gnu-emacs@gnu.org; Fri, 10 Nov 2017 08:35:10 -0500 Original-Received: from mail-pg0-x231.google.com ([2607:f8b0:400e:c05::231]:45436) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eD9Sc-0007Mg-GU for help-gnu-emacs@gnu.org; Fri, 10 Nov 2017 08:35:06 -0500 Original-Received: by mail-pg0-x231.google.com with SMTP id l19so4834937pgo.2 for ; Fri, 10 Nov 2017 05:35:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:mime-version:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=10NPHc/M6vbdIWbpCV4K49qpSIkbWjBeKBGLJAc9/Gk=; b=BYCHiibJkBKd/4OTNc+pdhH9eXLUc0H+lo04v9zTIhG/ytSTKe4r9HQcHX8Nx9Ydrh lGJCB9LrV+9YPrgEqc78lCy8WYMRoUwEc9wGx8i6KP5nT8T+ksU78WVpQMSzU8H0470t f+E0T52VJ5MT9IbzgNV+WudyR+9ktxoh4nWyTTzrzVoAIZa2TYiP36Z7mnNRG9fRDpAp evhx2B9tcnWHgvUiGdPVQ17vQq9XsvlEL5AD3clVT0d2b+tkmpXe26ZCspxKzDp22XyI 4wXAw+XqwfSCwFJu1lK1k9ordqSyiPcwtUmNJwNv5mFBVK3oEVdGwQLLTX+2vLHGR0MO EcWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=10NPHc/M6vbdIWbpCV4K49qpSIkbWjBeKBGLJAc9/Gk=; b=owzWwh6VaiO5q5nS9Lw5joowcGjAlv+4Kkg/abscWFq6LIazRPyZYmEeQwNe5hcfCs ecZ9kwBKiciU2oO9uCrVy/336XmW+CXNMSllMfywPHQ5Z660+AH0KuLmZXAhtVseYJgt Rjg8fZmssyTIPFlKgIyP/70us7N622GoiPc35uCr8GrNIhnjDsgK1eHZrzcB4WfVllpf aoGIteO/uAfTnxWHqWm4jH85ndR6jje01+Gi0qV9+8F43rmws699BJhQBmiOu0a+DcVe IZd5XfbJSb+iRDvy5uu7N83yXQYcXdyKe7Z5CCctqLL+0j7kqy12JjOnrNDkTb2p7Rcn c73A== X-Gm-Message-State: AJaThX5eUt1D1HqrumJrtqdg1MVBIA/ZiAhIOsr407viFgRfW19qonfe lCygYq4gwICLvSP/A0kBjD/5R7R5 X-Google-Smtp-Source: AGs4zMb++OX2fNrjMxQU7OqyWzgx2ChSews9pg8QnHsay78VAYISC1nRKs7u06+5Lw/7s+iauhmO9w== X-Received: by 10.84.229.77 with SMTP id d13mr364513pln.397.1510320904810; Fri, 10 Nov 2017 05:35:04 -0800 (PST) Original-Received: from [192.168.24.52] (pl27304.ag0304.nttpc.ne.jp. [128.53.17.168]) by smtp.gmail.com with ESMTPSA id h6sm18030151pgn.63.2017.11.10.05.35.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Nov 2017 05:35:03 -0800 (PST) X-Apple-Auto-Saved: 1 X-Apple-Mail-Remote-Attachments: YES X-Apple-Mail-Plain-Text-Draft: yes X-Apple-Base-Url: x-msg://7/ In-Reply-To: <87h8u32kw6.fsf@fliptop> X-Apple-Windows-Friendly: 1 X-Apple-Mail-Signature: SKIP_SIGNATURE X-Uniform-Type-Identifier: com.apple.mail-draft X-Mailer: Apple Mail (2.3445.4.7) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400e:c05::231 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:114830 Archived-At: Thank you Thomas for the reply. Ok, in a couple of posts it looked like the lack of possibility to just delete the thing highlighted was the main distraction. I also got the impression it is the subject of the thread. In a way, but because I thought I was seeing a region, which was not the case as I eventually understood. I don't want to upset anyone, and I didn't have that intention. My wording was maybe unnecessarily short. Don't worry. Things happen. Thank you for getting back to me. Anyway, I think I was reacting on the UI promise wording. I don't know there is such promise. There are expectations of course, based on peoples habits and prior experience. I agree that in most other applications, a highlighted region will get replaced by the next character you insert, or deleted if that is the action. I'm with you here. The problem here is that the result of search is *only* to move point and *not* to create a region of the highlighted matching string. So what appears on the screen carries actually very little meaning *because* with vanilla emacs, there is not isearch function (or any other search function for that matter) that creates a region out of that match. So it really is only a decoration. That's what I eventually understood, and that's why I wrote that it creates wrong UI expectations. If something should be highlighted, it should be the position of point, not how point found its way there, or at least the full region created by the search. Anything else has little meaning in the context of isearch. About the incremental search thing. I agree that it *could* be useful maybe to add an in-search command like Type C-l to toggle isearch-lock-string. The current search string is frozen and next self-insert-command or DEL will operate in the current buffer. C-l again from this state will revert to normal isearch. In this mode you can hit C-s again to get at the next mach. But then again, I don't know it would save so many key-strokes. If I want to search and delete, I find it rather fast anyway to just hit C-s again two times to get to the next match. You're right. Any solution that adds a layer between selecting the match and acting on it is not efficient. There should be a new function that acts directly on the match. Jean-Christophe Helary ----------------------------------------------- @brandelune http://mac4translators.blogspot.com