unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 10885@debbugs.gnu.org
Subject: bug#10885: Replace expressions: enhance functionality when searching in filled paragraphs
Date: Fri, 7 Sep 2012 10:33:19 +0200	[thread overview]
Message-ID: <CAH8Pv0iXHDQYoBf1iT98G8S3LnBst=m+Na3mLr3VC0a2bQqnHA@mail.gmail.com> (raw)
In-Reply-To: <jwvpq5y26bf.fsf-monnier+emacs@gnu.org>

On Thu, Sep 6, 2012 at 11:25 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> `isearch-regexp-lax-whitespace' was necessary to provide
>> backward-compatibility for old functionality.  Very likely
>> it will be declared obsolete.  But of course, it would be better
>> to have `replace-regexp-lax-whitespace' for consistency until
>> they both will be declared obsolete simultaneously.
>
> I don't think it makes sense to add something only for "consistency"
> reasons, knowing it'll be obsoleted soon.

I think replace-regexp-lax-whitespace is needed while the Isearch
counterpart (isearch-regexp-lax-whitespace) exists, if you want to
support the option I was asking for, whereby the lax-whitespace
settings in query-replace[-regexp] are "connected" (or "redirected")
to the Isearch counterparts.

And IMO this option is important, for a consistent user-experience.

But FWIW, as I said, I consider this lax-whitespace feature confusing
and unnecesary in regexp search/replace.  Thus, I'll rather remove
both isearch-regexp-lax-whitespace and replace-regexp-lax-whitespace.

-- 
Dani Moncayo





  reply	other threads:[~2012-09-07  8:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-26  1:02 bug#10885: Replace expressions: enhance functionality when searching in filled paragraphs linuxfever
2012-02-26  1:57 ` Glenn Morris
2012-02-26  7:16   ` Kevin Rodgers
2012-02-28 10:04     ` Dani Moncayo
2012-02-28 10:09       ` Dani Moncayo
2012-02-28 10:42       ` Juri Linkov
2012-02-29  0:12         ` Glenn Morris
2012-02-29  0:41           ` Juri Linkov
2012-03-11  8:59             ` Dani Moncayo
2012-03-11 10:48               ` Juri Linkov
2012-09-02  9:45                 ` Juri Linkov
2012-09-02 11:32                   ` Juri Linkov
2012-09-05  8:38                     ` Juri Linkov
2012-09-05 14:38                       ` Stefan Monnier
2012-09-06  8:54                         ` Juri Linkov
2012-09-06 15:54                           ` Dani Moncayo
2012-09-06 16:50                             ` Juri Linkov
2012-09-06 17:39                               ` Dani Moncayo
2012-09-06 19:11                                 ` Juri Linkov
2012-09-06 19:15                                   ` Juri Linkov
2012-09-06 19:45                                   ` Dani Moncayo
2012-09-06 20:21                                     ` Dani Moncayo
2012-09-06 21:25                               ` Stefan Monnier
2012-09-07  8:33                                 ` Dani Moncayo [this message]
2012-09-07  9:28                                   ` Juri Linkov
2012-09-09 22:15                                     ` Juri Linkov
2012-09-05 14:39                       ` Stefan Monnier
2012-02-26 10:10   ` linuxfever
2012-02-26 21:22     ` Stefan Monnier
2012-02-26 10:17 ` Dani Moncayo
2012-02-27 10:58   ` Juri Linkov
2012-02-27 13:27     ` Dani Moncayo

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='CAH8Pv0iXHDQYoBf1iT98G8S3LnBst=m+Na3mLr3VC0a2bQqnHA@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=10885@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).