unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: uyennhi.qm@gmail.com, 54804@debbugs.gnu.org, rpluim@gmail.com,
	tino.calancha@gmail.com
Subject: bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter
Date: Sat, 21 May 2022 08:38:44 +0300	[thread overview]
Message-ID: <83bkvra1i3.fsf@gnu.org> (raw)
In-Reply-To: <878rqvzu72.fsf@athena.silentflame.com> (message from Sean Whitton on Fri, 20 May 2022 15:59:45 -0700)

> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: 54804@debbugs.gnu.org, Robert Pluim <rpluim@gmail.com>, Eli Zaretskii
>  <eliz@gnu.org>, uyennhi.qm@gmail.com
> Date: Fri, 20 May 2022 15:59:45 -0700
> 
> > commit 86750ab021ea889766a717458ed28a54e6a40ad3
> > Author: Tino Calancha <tino.calancha@gmail.com>
> > Date:   Thu May 12 17:48:09 2022 +0200
> >
> >     zap-to-char: case sensitive for upper-case characters
> >
> >     In interactive calls, behave case-sensitively if the given char
> >     is an upper-case character.  Same for zap-up-to-char.
> >
> >     This is analog to what the user-level incremental search feature does.
> 
> Could we have a defcustom to always be case-sensitive, please?

We already have: case-fold-search.

> I like the way C-s works by default but for zap-* I'd prefer case
> sensitivity in every case.

Why?

It is a slippery slope to have a separate case-sensitivity option for
each command or a couple of commands.  If that is what you want, you
can always write your own one-line wrapper around each of these
commands, but I don't see any reason that Emacs should provide that
for everyone.

So I don't think we should provide such a defcustom for these two
commands.





  reply	other threads:[~2022-05-21  5:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 22:03 bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter Tino Calancha
2022-04-09  6:03 ` Eli Zaretskii
2022-04-16 10:58   ` Tino Calancha
2022-04-16 11:33     ` Eli Zaretskii
2022-05-09 16:17       ` Sean Whitton
2022-05-10 21:14       ` Tino Calancha
2022-05-11 11:15         ` Eli Zaretskii
2022-05-11 14:43           ` Tino Calancha
2022-05-11 14:50             ` Lars Ingebrigtsen
2022-05-11 15:00             ` Robert Pluim
2022-05-11 15:19               ` Tino Calancha
2022-05-11 15:27               ` Andreas Schwab
2022-05-11 15:38                 ` Tino Calancha
2022-05-11 16:11                   ` Andreas Schwab
2022-05-11 16:18                     ` Tino Calancha
2022-05-12 15:55                       ` Tino Calancha
2022-05-13  6:48                         ` Eli Zaretskii
2022-05-17 12:34                           ` Tino Calancha
2022-05-17 12:41                             ` Eli Zaretskii
2022-05-17 12:51                               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-17 12:53                                 ` Tino Calancha
2022-05-17 13:38                                   ` Eli Zaretskii
2022-05-17 14:31                                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-17 19:32                             ` Juri Linkov
2022-05-18  7:25                           ` Tino Calancha
2022-05-20 22:59                         ` Sean Whitton
2022-05-21  5:38                           ` Eli Zaretskii [this message]
2022-05-21  9:30                             ` Tino Calancha
2022-05-21 18:53                             ` Sean Whitton
2022-05-11 15:57             ` Eli Zaretskii

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=83bkvra1i3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54804@debbugs.gnu.org \
    --cc=rpluim@gmail.com \
    --cc=spwhitton@spwhitton.name \
    --cc=tino.calancha@gmail.com \
    --cc=uyennhi.qm@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 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).