GNU bug report logs - #222
isearch-repeat-forward: wrong overlay after failure

Previous Next

Full log

View this message in rfc822 format

From: David Kastrup <dak <at> gnu.org>
To: "Lennart Borgman \(gmail\)" <lennart.borgman <at> gmail.com>
Cc: David Reitter <david.reitter <at> gmail.com>, Juri Linkov <juri <at> jurta.org>,
        emacs-pretest-bug <at> gnu.org, 222 <at> debbugs.gnu.org
Subject: bug#222: isearch-repeat-forward: wrong overlay after failure
Date: Mon, 12 May 2008 01:25:58 +0200

"Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com> writes:

> David Kastrup wrote:
>> David Reitter <david.reitter <at> gmail.com> writes:
>>
>>> On 11 May 2008, at 17:59, Juri Linkov wrote:
>>>> `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.
>
> Maybe an error message that explains/points to an explanation?

What should trigger an error here?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.