From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: isearch-repeat-forward: wrong overlay after failure Date: Mon, 12 May 2008 10:41:05 -0400 Message-ID: References: <87tzh4rd41.fsf@jurta.org> <1D559CDD-D9EE-42D5-94F3-D7D33B9A1326@gmail.com> <85iqxke9ju.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1210603302 10863 80.91.229.12 (12 May 2008 14:41:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 12 May 2008 14:41:42 +0000 (UTC) Cc: Juri Linkov , David Reitter , 222@emacsbugs.donarmstrong.com, emacs-pretest-bug@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 12 16:42:19 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JvZEA-0004C2-BN for ged-emacs-devel@m.gmane.org; Mon, 12 May 2008 16:42:10 +0200 Original-Received: from localhost ([127.0.0.1]:54501 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JvZDS-0002ZQ-7q for ged-emacs-devel@m.gmane.org; Mon, 12 May 2008 10:41:26 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JvZDN-0002Ym-KO for emacs-devel@gnu.org; Mon, 12 May 2008 10:41:21 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JvZDM-0002YJ-Er for emacs-devel@gnu.org; Mon, 12 May 2008 10:41:21 -0400 Original-Received: from [199.232.76.173] (port=39724 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JvZDM-0002Y4-5o for emacs-devel@gnu.org; Mon, 12 May 2008 10:41:20 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:55553) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JvZDI-0002x2-Mj for emacs-devel@gnu.org; Mon, 12 May 2008 10:41:16 -0400 Original-Received: from mx10.gnu.org ([199.232.76.166]:35734) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JvZCQ-0004Ms-9U for emacs-pretest-bug@gnu.org; Mon, 12 May 2008 10:40:22 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JvZDD-0002tx-B6 for emacs-pretest-bug@gnu.org; Mon, 12 May 2008 10:41:15 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:32773) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JvZD8-0002s9-4F; Mon, 12 May 2008 10:41:06 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AocDAGLzJ0jO+JgrdGdsb2JhbACBU5A7ASeYKw X-IronPort-AV: E=Sophos;i="4.27,473,1204520400"; d="scan'208";a="20411585" Original-Received: from smtp.pppoe.ca (HELO smtp.teksavvy.com) ([65.39.196.238]) by ironport2-out.teksavvy.com with ESMTP; 12 May 2008 10:41:05 -0400 Original-Received: from pastel.home ([206.248.152.43]) by smtp.teksavvy.com (Internet Mail Server v1.0) with ESMTP id STB65605; Mon, 12 May 2008 10:41:05 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 418657F83; Mon, 12 May 2008 10:41:05 -0400 (EDT) In-Reply-To: <85iqxke9ju.fsf@lola.goethe.zz> (David Kastrup's message of "Mon, 12 May 2008 00:54:29 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:97028 gmane.emacs.pretest.bugs:22282 Archived-At: >>> `isearch-repeat-forward' is not an entry point to the incremental >>> search: >>> it doesn't activate isearch mode neither deactivates it. IIUC, it was >>> never intended for non-incremental search, so it doesn't guarantee to >>> work when isearch mode is not active. >>> >>> If you want to find the next occurrence without highlighting it >>> and without activating isearch mode, you can use the command >>> `search-forward'. >> >> isearch-repeat-forward is interactive, which is why I thought it would >> be a decent entry point. > Which I would call a reasonable expectation. However, keybindings even > in specialized keymaps need to be bound to interactive functions. So if > we have functions that are only intended for use in specialized keymaps, > there is no way to keep people from binding them to normal keymaps. > So it is sort of a combined documentation/expectation problem. I have > no good idea how to approach this. It's a very general problem: many keybindings used in major-mode or minor modes only work properly if the corresponding mode is currently active. Of course, many work perfectly in other contexts too, and yet many more work 98% OK as well. I don't think it makes sense to document each and every function describing whether it's expected to work in other modes or not. Stefan