From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: faq.texi Date: Fri, 17 Feb 2006 23:52:09 +0200 Organization: JURTA Message-ID: <877j7twp2e.fsf@jurta.org> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1140252472 1557 80.91.229.2 (18 Feb 2006 08:47:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 18 Feb 2006 08:47:52 +0000 (UTC) Cc: acm@muc.de, miles@gnu.org, rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 18 09:47:51 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FANks-0006ma-5X for ged-emacs-devel@m.gmane.org; Sat, 18 Feb 2006 09:47:50 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FANkr-0004UT-FN for ged-emacs-devel@m.gmane.org; Sat, 18 Feb 2006 03:47:49 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FAFQS-0004zK-GC for emacs-devel@gnu.org; Fri, 17 Feb 2006 18:54:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FAFK6-0001IS-6E for emacs-devel@gnu.org; Fri, 17 Feb 2006 18:48:06 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FAFJk-00016R-Ef for emacs-devel@gnu.org; Fri, 17 Feb 2006 18:47:18 -0500 Original-Received: from [194.126.101.111] (helo=mail.neti.ee) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FAFP5-0002ar-EU; Fri, 17 Feb 2006 18:52:47 -0500 Original-Received: from mail.neti.ee (80-235-41-12-dsl.mus.estpak.ee [80.235.41.12]) by Relayhost1.neti.ee (Postfix) with ESMTP id 2DCE14E33; Sat, 18 Feb 2006 01:47:06 +0200 (EET) Original-To: Andreas Schwab In-Reply-To: (Andreas Schwab's message of "Thu, 16 Feb 2006 23:16:19 +0100") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Virus-Scanned: by amavisd-new-2.2.1 (20041222) (Debian) at neti.ee X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:50692 Archived-At: >> But whatever, I still wouldn't want to lose C-y from within searches. >> Sometimes C-y followed by M-e and a few backspaces is more convenient >> than repeated C-w. > > I second that. I'm also using C-y in isearch quite often. Another > application for it on diffs is to do C-s C-y on a context line, then > change to the file that this diff is based on and do C-s C-s to find > the context line here. This is one of the typical examples when I use C-y in isearch too. Another one is to check two multi-line sections of the same buffer (such duplicate sections can appear after merge conflicts or after copying from different sources) and to find the first different line. But this doesn't mean that I like C-y as a keybinding. I need only its function isearch-yank-line, and would accept any other keybinding. BTW, there is one problem with multi-line lazy highlighting: isearch doesn't highlight partially visible matches, i.e. when a match begins before (window-end) and ends after it. This is due to the meaning of the argument `limit' of `search-forward' which specifies the lower bound of the search, i.e. (match-end 0). Without an ability to specify the upper bound of the search, isearch lazy highlighting can't highlight partially visible matches whose (match-beginning 0) is before (window-end), and (match-end 0) is after (window-end). -- Juri Linkov http://www.jurta.org/emacs/