From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#15839: 24.3.50; `isearch-allow-scroll': be able to scroll point off screen temporarily Date: Mon, 26 Nov 2018 16:49:21 -0800 (PST) Message-ID: <8af20443-841d-4211-99ae-269e042a9a33@default> References: <51df60b6-e152-4989-a27e-70dadb9b7474@default> <8736rqgk6f.fsf@mail.linkov.net> <87y39gexdo.fsf@mail.linkov.net> <877egzmmyk.fsf@mail.linkov.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1543279689 31953 195.159.176.226 (27 Nov 2018 00:48:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 27 Nov 2018 00:48:09 +0000 (UTC) Cc: 15839@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Nov 27 01:48:05 2018 Return-path: Envelope-to: geb-bug-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 1gRRXo-0008CD-Tz for geb-bug-gnu-emacs@m.gmane.org; Tue, 27 Nov 2018 01:48:05 +0100 Original-Received: from localhost ([::1]:39522 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRRZv-0006GM-Dr for geb-bug-gnu-emacs@m.gmane.org; Mon, 26 Nov 2018 19:50:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33823) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRRZn-0006Db-Vo for bug-gnu-emacs@gnu.org; Mon, 26 Nov 2018 19:50:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gRRZj-0004pe-VP for bug-gnu-emacs@gnu.org; Mon, 26 Nov 2018 19:50:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:46006) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gRRZi-0004pD-8x for bug-gnu-emacs@gnu.org; Mon, 26 Nov 2018 19:50:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gRRZi-0000f1-3r for bug-gnu-emacs@gnu.org; Mon, 26 Nov 2018 19:50:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 27 Nov 2018 00:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15839 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15839-submit@debbugs.gnu.org id=B15839.15432797722500 (code B ref 15839); Tue, 27 Nov 2018 00:50:02 +0000 Original-Received: (at 15839) by debbugs.gnu.org; 27 Nov 2018 00:49:32 +0000 Original-Received: from localhost ([127.0.0.1]:50264 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gRRZE-0000eF-GB for submit@debbugs.gnu.org; Mon, 26 Nov 2018 19:49:32 -0500 Original-Received: from userp2130.oracle.com ([156.151.31.86]:42062) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gRRZC-0000e2-6d for 15839@debbugs.gnu.org; Mon, 26 Nov 2018 19:49:30 -0500 Original-Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id wAR0n4ja152451; Tue, 27 Nov 2018 00:49:24 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=YvMHFWlTx9C43CVmFMEGxv2KKLP5A95QWKW0f9Zn/hQ=; b=pyW5pMiCkFjz1PuimaHrP+r50SFehluaewjAhcQc8UumPlVVoCW3EAFSLOgzOji/VNYo DWUoyCRqAkGukisyMnt5xgptDdbOo3Kztd5G/TCKRXfOLGr78xext8ZU2aF+JfyX52cG 1QEfEVi/rwISozDaHM52csHvrEp4fMNLk5/3Sq4PmppY82ZdWS4HzsZzP49Jh3sr0qDp ZWLD1ILeEk+7aRPk0oaunwtBdDabhFpOBI9FBNgCaxL7gZ2IvEa2A9dzZjyKhjCKHafs UsPGQjKH6x054shFH/UMPC644xc5h3kQBuftd5kQeefv+69BJGLL2CNr1zL9tK93Cnje sA== Original-Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp2130.oracle.com with ESMTP id 2nxx2u12gk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 27 Nov 2018 00:49:24 +0000 Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id wAR0nNDB016688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 27 Nov 2018 00:49:23 GMT Original-Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id wAR0nMAO017653; Tue, 27 Nov 2018 00:49:22 GMT In-Reply-To: <877egzmmyk.fsf@mail.linkov.net> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4771.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9089 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811270004 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:152806 Archived-At: > > Sorry, but I don't really understand. > > > > There are several parts to this bug report. I don't know > > what "the first part" refers to. >=20 > It refers to your original request cited below: Thanks for clarifying what you meant. But those points 1,2,... in the bug report are not independent. They are meant to make a logical argument for what's being requested. They are all of a piece. They describe different, but related, aspects of the inconvenience that the requested feature would alleviate. I don't want to customize one variable to be able to scroll farther, and another variable to have what's shown by that scrolling have lazy-highlighting (especially if the latter requires lazy-highlighting the entire buffer, rather than just what I see when scrolling). I want to be able to use `isearch-allow-scroll' to let me scroll as far as I want, and see search hits lazy-highlighted in what parts of the buffer I scroll to. > > 1. Non-nil `isearch-allow-scroll' lets you use a scroll command > > (e.g. `C-v') without exiting Isearch. Unfortunately, this is coupled > > with the hard-coded behavior that you cannot scroll far enough in > > either direction that point would be moved off screen. > > > > That restriction is general for Emacs, and it generally makes sense. > > It does not necessarily make sense during Isearch, however. Why? > > > > Because the search position is one thing, and it is not lost. What > > you might want to look at temporarily is another thing. > > > > It's a bit like using `C-SPC' in a buffer, scrolling up a couple of > > screenfuls to look at something, and then using `C-u C-SPC' to > > return. But in Isearch there is no need for `C-SPC' or `C-u C-SPC': > > the search position is recorded. Search resumes from that same > > position, no matter how far away one might have scrolled. >=20 > This is implemented now with an option `nil' of the customizable > variable `search-exit-option'. It lets you use a scroll command > (e.g. `C-v') without exiting Isearch, so you can scroll far enough > in either direction that point would be moved off screen. >=20 > > 2. What's more, the lazy highlighting of search hits is even more > > limited currently. When you scroll to the current limit, there can > > be lots of search hits that are not highlighted. > > > > One of the reasons for scrolling is to see what search hits lie > > beyond the currently shown text. This is already partly defeated, > > in that even when you scroll some of the hits are not highlighted. > > This seems more like a bug, but if the enhancement of #1 is done > > then it should (it needs to) take care of #2 as well: Whatever > > text is shown should have all of its search hits highlighted with > > lazy highlighting. >=20 > This is implemented now with the customizable variable > `lazy-highlight-buffer'. I do appreciate your letting me know what's newly available; thanks. And thanks for making those improvements. But no, I don't think we have what I requested, and I don't think this bug (enhancement request) should be closed.