unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: ??? Dan Jacobson <jidanni@jidanni.org>
Cc: 22494@debbugs.gnu.org, mbork@mbork.pl, rms@gnu.org
Subject: bug#22494: still can't search for two spaces
Date: Sun, 31 Jan 2016 17:57:45 -0800 (PST)	[thread overview]
Message-ID: <da129102-b5fc-4990-85da-b7009cc3e5de@default> (raw)
In-Reply-To: <87powhz3sa.fsf@jidanni.org>

> All I know is an Auntie Nelda-like person (me) typed those two spaces
> and expected them to match. I don't know about all that other stuff.

I, at least, have agreed with you and your Auntie Nelda.
And I think that Richard has also agreed about this.

FWIW, I said so (in emacs-devel@gnu.org) before Isearch was changed
to provide lax whitespace search as a possibility, and I opposed
(unsuccessfully) making it the default behavior.

For me, as for your Auntie Nelda also, it seems, literal search is
clearest as a default behavior for C-s.  I disagree that C-s should
default to a "handy", Emacs-knows-what-you-really-want/need behavior.





  reply	other threads:[~2016-02-01  1:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30  6:34 bug#22494: still can't search for two spaces 積丹尼 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 [this message]
2016-02-01  3:10 ` 積丹尼 Dan Jacobson
     [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
     [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           ` Drew Adams
2016-02-01 11:01             ` Richard Stallman
2016-02-01 11:20               ` Andreas Schwab
2016-02-01 14:15                 ` Dani Moncayo
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

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=da129102-b5fc-4990-85da-b7009cc3e5de@default \
    --to=drew.adams@oracle.com \
    --cc=22494@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=mbork@mbork.pl \
    --cc=rms@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).