From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Andreas Schwab <schwab@linux-m68k.org>, 10145@debbugs.gnu.org
Subject: bug#10145: 24.0.91; Word Isearch backward
Date: Wed, 30 Nov 2011 17:32:45 +0200 [thread overview]
Message-ID: <87aa7dd48q.fsf@mail.jurta.org> (raw)
In-Reply-To: <jwvipm17luy.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 30 Nov 2011 09:02:05 -0500")
>> In the patch below the first line is a complete sentence,
>> and `wordify' is renamed to a better and more correct name
>> `word-regexp':
>
> While `wordify' was OK as a local function in search.c, I think that
> both `wordify' and `word-regexp' are too terse names for (global)
> Elisp functions. Maybe `search-words-regexp' would be appropriate.
I constructed that name based on the naming pattern of related functions
`word-search-forward' and `word-search-backward'. A similar name
would be `word-search-regexp'. However, it is used not only for search,
but for `looking-at' too, so we have to eliminate the `search' part
from the name. Therefore `word-regexp'.
Another naming pattern would be `regexp-quote' that takes a string
and returns a regexp. `quote' is a verb here, so using a verb
would produce a name like `regexp-wordify'.
Yet another naming pattern is `number-to-string'. Using that
we get the name `words-to-regexp'.
> Of course, I also see no reason why it should be implemented in C, so
> moving it to Elisp would be welcome.
I'll provide an Elisp version once the function name is agreed upon.
next prev parent reply other threads:[~2011-11-30 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 20:26 bug#10145: 24.0.91; Word Isearch backward Dani Moncayo
2011-11-29 0:33 ` Juri Linkov
2011-11-29 8:40 ` Andreas Schwab
2011-11-30 9:46 ` Juri Linkov
2011-11-30 14:02 ` Stefan Monnier
2011-11-30 15:32 ` Juri Linkov [this message]
2011-11-30 19:11 ` Stefan Monnier
2011-12-01 7:27 ` Juri Linkov
2011-12-01 16:00 ` Stefan Monnier
2011-12-02 10:22 ` Juri Linkov
2011-12-02 10:48 ` Eli Zaretskii
2011-12-02 14:38 ` Stefan Monnier
2011-12-02 17:11 ` Juri Linkov
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=87aa7dd48q.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=10145@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=schwab@linux-m68k.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.