all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 26580@debbugs.gnu.org, ynyaaa@gmail.com,
	Tino Calancha <tino.calancha@gmail.com>,
	Juri Linkov <juri@linkov.net>
Subject: bug#26580: 25.1; inappropriate case folding while isearch-forward-regexp
Date: Sat, 22 Apr 2017 00:17:54 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1704212359510.15176@calancha-pc> (raw)
In-Reply-To: <87efwlyjjb.fsf@linux-m68k.org>



On Fri, 21 Apr 2017, Andreas Schwab wrote:

> On Apr 21 2017, Tino Calancha <tino.calancha@gmail.com> wrote:
>
>> OK, i just picked up \W from you.  Let's changed to \T:
>
> Since \T has no meaning nobody would use it anyway.
Someone might want to use it to disable the case sensitivity search.

After Eli e-mail, i agree with the OP and you that would be more
consistent if '\cCa' disables case sensitive searches as '\cc\A' does.

In case that is difficult to implement, we might want to document
that the  slash trick just works for single characters.  Then, the user
would just use '\cca' which loks even simpler.





  reply	other threads:[~2017-04-21 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 17:55 bug#26580: 25.1; inappropriate case folding while isearch-forward-regexp ynyaaa
2017-04-21  3:40 ` Tino Calancha
2017-04-21  9:22   ` Andreas Schwab
2017-04-21  9:50     ` Tino Calancha
2017-04-21 12:04       ` Andreas Schwab
2017-04-21 12:16         ` Tino Calancha
2017-04-21 13:26           ` Eli Zaretskii
2017-04-21 14:59             ` Tino Calancha
2017-04-21 13:31           ` Andreas Schwab
2017-04-21 15:17             ` Tino Calancha [this message]
2017-04-21 17:42               ` Andreas Schwab
2017-04-25 20:57               ` Juri Linkov

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=alpine.DEB.2.20.1704212359510.15176@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=26580@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=schwab@linux-m68k.org \
    --cc=ynyaaa@gmail.com \
    /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.