unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: 222@emacsbugs.donarmstrong.com, emacs-pretest-bug@gnu.org
Subject: bug#222: isearch-repeat-forward: wrong overlay after failure
Date: Mon, 12 May 2008 01:00:22 +0200	[thread overview]
Message-ID: <48277A86.9070606__11772.6124277853$1210547566$gmane$org@gmail.com> (raw)
In-Reply-To: <85iqxke9ju.fsf@lola.goethe.zz>

David Kastrup wrote:
> David Reitter <david.reitter@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?






  parent reply	other threads:[~2008-05-11 23:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D33C5B65-3FAC-4CAB-8819-A9B91CC859F7@gmail.com>
     [not found] ` <87tzh4rd41.fsf@jurta.org>
2008-05-11 21:48   ` bug#222: isearch-repeat-forward: wrong overlay after failure David Reitter
     [not found]   ` <1D559CDD-D9EE-42D5-94F3-D7D33B9A1326@gmail.com>
2008-05-11 22:54     ` David Kastrup
     [not found]     ` <85iqxke9ju.fsf@lola.goethe.zz>
2008-05-11 23:00       ` Lennart Borgman (gmail) [this message]
     [not found]       ` <48277A86.9070606@gmail.com>
2008-05-11 23:25         ` David Kastrup
     [not found]         ` <85bq3ce83d.fsf@lola.goethe.zz>
2008-05-11 23:59           ` Juri Linkov
     [not found]           ` <87ej88mlxz.fsf@jurta.org>
2008-05-12  7:21             ` David Reitter
2008-05-12  7:56               ` David Reitter
2008-05-12 14:41       ` Stefan Monnier
     [not found]       ` <jwvhcd3oafw.fsf-monnier+emacsbugreports@gnu.org>
2011-07-09 17:39         ` Glenn Morris
2008-05-11 15:52 David Reitter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='48277A86.9070606__11772.6124277853$1210547566$gmane$org@gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=222@emacsbugs.donarmstrong.com \
    --cc=dak@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).