From: Dani Moncayo <dmoncayo@gmail.com>
To: Chong Yidong <cyd@gnu.org>
Cc: Bastien <bzg@gnu.org>,
emacs-devel@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: Interpretation of a space in regexp isearch?
Date: Sun, 26 Aug 2012 19:31:41 +0200 [thread overview]
Message-ID: <CAH8Pv0joxTnmW=F6HPLv-nmaVJ_abCHJqfEJjBbnzrZUCYz=Rg@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0h+13JpY2jAqkNguxy2ffjCwoZCNwx8x-DF0NuY_cdhCQ@mail.gmail.com>
> While testing your change, I've noticed a couple of things that I'd
> like to understand:
>
> 1. Info mode has its own variable `Info-search-whitespace-regexp'.
> Why is it necessary? I guess there's a reason (which I don't know by
> now) so it seems that your change should also affect to this variable.
>
> 2. Why don't you include \n and \r by default in the regexp? IMO
> that'd be TRT for most users.
3. Why should this feature be limited to _incremental_ searches? I
don't think it should. The documentation states this limitation (see
[1][2][3]) but according to the tests I've done, non-incremental
searches also take `search-whitespace-regexp' into account.
-----------
[1] Docstring of command `isearch-forward'.
[2] Docstring of variable `search-whitespace-regexp'.
[3] Info node "(emacs) Regexp Search".
--
Dani Moncayo
next prev parent reply other threads:[~2012-08-26 17:31 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 4:40 Interpretation of a space in regexp isearch? Dmitry Gutov
2012-08-15 5:27 ` Bastien
2012-08-15 9:11 ` Dani Moncayo
2012-08-15 9:13 ` Dani Moncayo
2012-08-15 9:19 ` Dani Moncayo
2012-08-15 13:59 ` Drew Adams
2012-08-15 14:31 ` Davis Herring
2012-08-15 16:43 ` Drew Adams
2012-08-15 17:54 ` Davis Herring
2012-08-15 22:53 ` Dmitry Gutov
2012-08-15 23:21 ` Drew Adams
2012-08-16 2:25 ` Dmitry Gutov
2012-08-16 5:37 ` Drew Adams
2012-08-26 4:06 ` Chong Yidong
2012-08-26 6:59 ` Bastien
2012-08-26 15:19 ` Dani Moncayo
2012-08-26 17:31 ` Dani Moncayo [this message]
2012-08-28 8:28 ` Juri Linkov
2012-08-28 9:07 ` Dani Moncayo
2012-08-28 23:01 ` Juri Linkov
2012-08-27 18:34 ` Johan Bockgård
2012-08-28 8:30 ` Juri Linkov
2012-08-28 12:53 ` Stefan Monnier
2012-08-28 22:54 ` Juri Linkov
2012-08-28 23:52 ` Drew Adams
2012-08-29 8:38 ` Juri Linkov
2012-08-29 16:01 ` Drew Adams
2012-08-29 23:49 ` Juri Linkov
2012-08-30 8:19 ` Chong Yidong
2012-08-30 8:31 ` Chong Yidong
2012-08-30 8:54 ` Juri Linkov
2012-08-30 14:47 ` Stefan Monnier
2012-08-31 0:02 ` Juri Linkov
2012-08-31 0:07 ` Juri Linkov
2012-08-31 5:40 ` Chong Yidong
2012-08-31 9:31 ` Juri Linkov
2012-08-31 14:55 ` Chong Yidong
2012-09-01 0:47 ` Juri Linkov
2012-09-01 3:15 ` Chong Yidong
2012-09-01 11:50 ` Juri Linkov
2012-09-01 16:02 ` Chong Yidong
2012-08-29 6:46 ` Chong Yidong
2012-08-29 8:28 ` Juri Linkov
2012-08-29 13:55 ` Stefan Monnier
2012-08-29 15:11 ` Dani Moncayo
2012-08-29 23:51 ` Juri Linkov
2012-08-28 8:27 ` Juri Linkov
2012-08-29 6:59 ` Chong Yidong
2012-08-29 8:34 ` Juri Linkov
2012-08-30 9:01 ` Chong Yidong
2012-08-30 9:18 ` Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2012-08-14 23:45 Dmitry Gutov
2012-08-14 23:03 Bastien
2012-08-14 23:45 ` Davis Herring
2012-08-14 23:53 ` Bastien
2012-08-15 3:42 ` Chong Yidong
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='CAH8Pv0joxTnmW=F6HPLv-nmaVJ_abCHJqfEJjBbnzrZUCYz=Rg@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=bzg@gnu.org \
--cc=cyd@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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).