From: Stefan Monnier <monnier@iro.umontreal.ca>
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 10:41:05 -0400 [thread overview]
Message-ID: <jwvhcd3oafw.fsf-monnier+emacsbugreports__13953.4083697528$1210603975$gmane$org@gnu.org> (raw)
In-Reply-To: <85iqxke9ju.fsf@lola.goethe.zz> (David Kastrup's message of "Mon, 12 May 2008 00:54:29 +0200")
>>> `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
next prev parent reply other threads:[~2008-05-12 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 15:52 isearch-repeat-forward: wrong overlay after failure David Reitter
2008-05-11 16:59 ` Juri Linkov
2008-05-11 21:48 ` bug#222: " David Reitter
2008-05-11 21:48 ` David Reitter
2008-05-11 22:54 ` David Kastrup
2008-05-11 23:00 ` Lennart Borgman (gmail)
2008-05-11 23:25 ` David Kastrup
2008-05-11 23:59 ` Juri Linkov
2008-05-12 7:21 ` bug#222: " David Reitter
2008-05-12 7:56 ` David Reitter
2008-05-12 7:56 ` David Reitter
2008-05-13 0:30 ` Juri Linkov
2008-05-12 7:21 ` David Reitter
2008-05-11 23:59 ` bug#222: " Juri Linkov
2008-05-11 23:25 ` David Kastrup
2008-05-11 23:00 ` Lennart Borgman (gmail)
2008-05-12 14:41 ` Stefan Monnier [this message]
2008-05-12 14:41 ` Stefan Monnier
2011-07-09 17:39 ` bug#222: " Glenn Morris
2008-05-11 22:54 ` David Kastrup
-- strict thread matches above, loose matches on Subject: below --
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jwvhcd3oafw.fsf-monnier+emacsbugreports__13953.4083697528$1210603975$gmane$org@gnu.org' \
--to=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.