unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: bruce.connor.am@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 3e9ac80: Yet another doc improvement for search commands
Date: Tue, 01 Dec 2015 21:30:51 +0200	[thread overview]
Message-ID: <83vb8ij79w.fsf@gnu.org> (raw)
In-Reply-To: <CAAdUY-LuAhBntu5cJs4jmG2K=A28wir2H1m0hiKBJJU3ZWh5ug@mail.gmail.com>

> Date: Tue, 1 Dec 2015 18:05:54 +0000
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: emacs-devel <emacs-devel@gnu.org>
> 
> On 1 Dec 2015 3:37 pm, "Eli Zaretskii" <eliz@gnu.org> wrote:
> > Maybe we should add a note that, although lax-whitespace matching is
> > not supported with word search, it is also not needed, because spaces
> > between words are ignored anyway?
> 
> Yes. We shouldn't say it can't do lax-whitespace, cause the reality is that it
> can't NOT do lax-whitespace. 
> 
> We can either say nothing, or say something like:
> The word search commands don't perform character folding and are not affected
> by lax whitespace matching (since they ignore the spaces between words anyway,
> @pxref{Lax Search}).

I said instead that lax-whitespace matching has no effect on these
commands.



  reply	other threads:[~2015-12-01 19:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151130173139.31071.34723@vcs.savannah.gnu.org>
     [not found] ` <E1a3SId-00085l-Mj@vcs.savannah.gnu.org>
2015-11-30 19:58   ` emacs-25 3e9ac80: Yet another doc improvement for search commands Artur Malabarba
2015-11-30 20:48     ` [Emacs-diffs] " Eli Zaretskii
2015-12-01 10:36       ` Artur Malabarba
2015-12-01 15:37         ` [Emacs-diffs] " Eli Zaretskii
2015-12-01 18:05           ` Artur Malabarba
2015-12-01 19:30             ` Eli Zaretskii [this message]
2015-12-01 20:04               ` Artur Malabarba
2015-12-01 21:06                 ` Drew Adams
     [not found]     ` <<83oaebkybx.fsf@gnu.org>
2015-11-30 21:47       ` Drew Adams

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=83vb8ij79w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bruce.connor.am@gmail.com \
    --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).