From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 11381@debbugs.gnu.org
Subject: bug#11381: 23.3; isearch-search-and-update issue?
Date: Thu, 17 May 2012 03:08:33 +0300 [thread overview]
Message-ID: <87vcjvwtxa.fsf@mail.jurta.org> (raw)
In-Reply-To: <jwvlikszweb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 15 May 2012 22:35:48 -0400")
>> Below is a complete patch that moves them to Elisp:
>
> Feel free to install it on the trunk, thanks,
Installed.
Regarding the addition of symbol search functions, I hesitate to define
7 more functions for every search type. If now add
symbol-search-forward, symbol-search-backward,
symbol-search-forward-lax, symbol-search-backward-lax,
and two functions to activate the symbol search
isearch-forward-symbol, isearch-backward-symbol,
then later someone might ask to add a subword search type
with subword-search-forward, subword-search-backward,
subword-search-forward-lax, subword-search-backward-lax,
isearch-forward-subword, isearch-backward-subword,
and so on. This will grow isearch.el unnecessarily.
When trying to achieve simplicity, all what is needed to define
for every regexp-based search type is just:
1. Define a string-to-regexp conversion function
(like `word-search-regexp').
2. Define a key sequence to activate this search type.
This is a minimal set of requirements to define a new regexp-based
search type.
I believe a set of search filters for bug#11378
could be defined in the same simple way:
1. Define a filter predicate function
(like `isearch-filter-visible').
2. Define a key sequence to activate this search filter.
next prev parent reply other threads:[~2012-05-17 0:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 22:31 bug#11381: 23.3; isearch-search-and-update issue? Andy Grover
2012-04-30 0:27 ` Juri Linkov
2012-05-01 9:03 ` Juri Linkov
2012-05-01 13:08 ` Stefan Monnier
2012-05-01 15:17 ` Juri Linkov
2012-05-15 21:35 ` Juri Linkov
2012-05-16 2:35 ` Stefan Monnier
2012-05-17 0:08 ` Juri Linkov [this message]
2012-05-20 0:15 ` Juri Linkov
2012-05-21 1:36 ` Stefan Monnier
2012-05-21 2:23 ` Stefan Monnier
2012-05-27 9:43 ` Juri Linkov
2012-05-28 4:48 ` Stefan Monnier
2012-05-28 8:55 ` Juri Linkov
2012-05-28 14:08 ` Stefan Monnier
2012-05-29 9:49 ` Juri Linkov
2012-05-29 13:34 ` Stefan Monnier
2012-05-27 9:35 ` Juri Linkov
2012-05-28 4:23 ` Stefan Monnier
2012-05-28 15:44 ` Eli Zaretskii
2012-05-28 17:34 ` bug#11381: use and doc of function symbol properties [was: bug#11381: 23.3; isearch-search-and-update issue?] Drew Adams
2012-05-28 19:34 ` bug#11381: 23.3; isearch-search-and-update issue? Stefan Monnier
2012-05-29 0:27 ` Juri Linkov
2012-05-29 1:26 ` Stefan Monnier
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=87vcjvwtxa.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=11381@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).