all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: John Wiegley <johnw@gnu.org>
Cc: 22494@debbugs.gnu.org, mbork@mbork.pl, rms@gnu.org, jidanni@jidanni.org
Subject: bug#22494: still can't search for two spaces
Date: Wed, 3 Feb 2016 11:08:08 -0800 (PST)	[thread overview]
Message-ID: <74c1c1b9-8bce-4cc9-8319-c1b9fce1fb1d@default> (raw)
In-Reply-To: <m21t8t1v3j.fsf@newartisans.com>

> > 4. I raised a question about whether lax w-s matching should
> >    be automatically turned OFF if you _paste_ (not type) text
> >    that contains multiple, contiguous w-s chars.
> 
> I think it should be, as with typing them.

Maybe.  But it's easy to copy some text (e.g. non-code) from
some external source (not Emacs), and search for it (by yanking).

You might not even know whether it contains more than one
whitespace char in a row.  And if it does, I'm guessing that
some users might be surprised to see lax whitespace matching
turned off after the yank.

Not a big deal, as long as they are clearly notified, in a
way that they understand _why_ the search mode has changed
(e.g. the search string now contains more than one w-s char
in a row).

But I still have the question of what the right approach is.
There are different possibilities, when someone yanks some
text to add to the search string, regarding the intention
wrt searching for whitespace.

My guess is that whatever behavior we choose some users will
be confused.  This just underlines the importance of letting
the user know (a) that a change in behavior has taken place
and (b) why it has.





  reply	other threads:[~2016-02-03 19:08 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=74c1c1b9-8bce-4cc9-8319-c1b9fce1fb1d@default \
    --to=drew.adams@oracle.com \
    --cc=22494@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=johnw@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.