unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: 22494@debbugs.gnu.org, mbork@mbork.pl,
	Richard Stallman <rms@gnu.org>,
	Dan Jacobson <jidanni@jidanni.org>
Subject: bug#22494: still can't search for two spaces
Date: Mon, 1 Feb 2016 15:15:55 +0100	[thread overview]
Message-ID: <CAH8Pv0gE15VE-3YzVzwjt=0Rt8SNs915Os4AS13W+vDuAihESA@mail.gmail.com> (raw)
In-Reply-To: <mvmvb68ekxu.fsf@hawking.suse.de>

>>   > What is in the search string is a search pattern.  How it is
>>   > interpreted is the question.
>>
>> Right.  And I am proposing a way to interpret part of it.  Namely,
>> two spaces in a row means to match two spaces in the buffer.
>
> But if you isearch-yank them they should be normalized so that they
> continue to do lax matching.

Quoting from [1]:

  IMO, Emacs should refrain from making permanent changes to the search
  string, as given by the user.  IOW, the search string should be kept
  untouched, and any transformations of it should be done "on the fly"
  to achieve the intended behavior, based on both the _current_ search
  string and the _current_ user options that govern the search behavior.

  That way, if/when either the search string or the user options
  changes, Emacs will be able to exhibit the expected behavior.

IOW, I don't think that normalization is a good idea.

But I agree with you that two (or more) consecutive spaces should
be treated specially _only_ if they were *typed* by the user (not
yanked from the kill ring or grabbed from the buffer)

---
Dani Moncayo

[1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16546#43





  reply	other threads:[~2016-02-01 14:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<<87h9hvshi3.fsf@jidanni.org>
     [not found] ` <<<E1aPdiw-0001yi-W4@fencepost.gnu.org>
     [not found]   ` <<54a07b7d-1fbd-4ed1-a8a0-e22eb5787c97@default>
     [not found]     ` <<871t8yit11.fsf@mbork.pl>
     [not found]       ` <<77b5b6df-4889-4142-a04d-526dd94c3a48@default>
     [not found]         ` <<E1aPyeg-0003QJ-B5@fencepost.gnu.org>
2016-01-31 21:29           ` bug#22494: still can't search for two spaces Drew Adams
2016-02-01 11:01             ` Richard Stallman
2016-02-01 11:20               ` Andreas Schwab
2016-02-01 14:15                 ` Dani Moncayo [this message]
2016-02-03  6:45             ` John Wiegley
2016-02-03 14:57               ` Drew Adams
2016-02-03 18:56                 ` John Wiegley
2016-02-03 19:08                   ` Drew Adams
2016-02-03 15:28               ` Eli Zaretskii
2016-02-03 15:44               ` Nicolas Richard
     [not found] <<87h9hvshi3.fsf@jidanni.org>
     [not found] ` <<8337tfy0p3.fsf@gnu.org>
     [not found]   ` <<E1aPdiw-0001yi-W4@fencepost.gnu.org>
2016-01-30 22:28     ` Drew Adams
2016-01-30 22:47       ` Marcin Borkowski
2016-01-31  0:02         ` Drew Adams
2016-01-31 20:31           ` Richard Stallman
2016-01-31  0:08       ` Juri Linkov
2016-01-30  6:34 積丹尼 Dan Jacobson
2016-01-30  7:40 ` Eli Zaretskii
2016-01-30 22:10   ` Richard Stallman
2016-01-31  5:39     ` John Wiegley
2016-01-31 16:08       ` Drew Adams
2016-02-01  0:13 ` 積丹尼 Dan Jacobson
2016-02-01  1:57   ` Drew Adams
2016-02-01  3:10 ` 積丹尼 Dan Jacobson

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='CAH8Pv0gE15VE-3YzVzwjt=0Rt8SNs915Os4AS13W+vDuAihESA@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=22494@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=mbork@mbork.pl \
    --cc=rms@gnu.org \
    --cc=schwab@suse.de \
    /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).