unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 54804@debbugs.gnu.org, juri@linkov.net, uyennhi.qm@gmail.com,
	monnier@iro.umontreal.ca, spwhitton@spwhitton.name
Subject: bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter
Date: Tue, 17 May 2022 15:41:53 +0300	[thread overview]
Message-ID: <83pmkcgwku.fsf@gnu.org> (raw)
In-Reply-To: <874k1onxs1.fsf@gmail.com> (message from Tino Calancha on Tue, 17 May 2022 14:34:06 +0200)

> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: 54804@debbugs.gnu.org,  spwhitton@spwhitton.name,uyennhi.qm@gmail.com,
>  <monnier@iro.umontreal.ca>, juri@linkov.net
> Date: Tue, 17 May 2022 14:34:06 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> I have added Stefan, who suggests using the interactive arg (see
> explanation below).
> I have also added Juri, who is expert on isearch.
> 
> >> From: Tino Calancha <tino.calancha@gmail.com>
> >>     * lisp/misc.el (zap-up-to-char): Add an optional arg INTERACTIVE.
> >>     Perform a case-sensitive search when INTERACTIVE is non-nil and
> >>     CHAR is an upper-case character.
> >
> > I don't understand why the need for the new INTERACTIVE argument.
> 
> > And, as mentioned above, I don't think I understand why we need to do
> > this only in interactive calls.  Non-interactive invocations already
> > have a way to request case-sensitivity, by let-binding
> > case-fold-search, right?
> 
> I'll try to explain this.
> 
> This is what Emacs does for isearch/search.

Search is a much more complex set of features and commands in Emacs.
These two commands are much simpler, and I see no reason to try to be
compatible with search commands, since these two commands don't search
anything.

> I want the analog behavior for zap-to... commands: automatic
> case sensitivity when the char is uppercase.
> I want this behavior on interactive calls only, for instance when users
> do `M-z'.

As I said I disagree: these are DWIMish features that are best
reserved for interactive invocation.  In calls from Lisp, it is
confusing to have the behavior change so drastically depending on the
letter-case of an argument.





  reply	other threads:[~2022-05-17 12:41 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 [this message]
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
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=83pmkcgwku.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54804@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=monnier@iro.umontreal.ca \
    --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).