[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter
From: |
Eli Zaretskii |
Subject: |
bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter |
Date: |
Tue, 17 May 2022 16:38:43 +0300 |
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Tue, 17 May 2022 14:53:41 +0200 (CEST)
> cc: Eli Zaretskii <eliz@gnu.org>, Tino Calancha <tino.calancha@gmail.com>,
> 54804@debbugs.gnu.org, spwhitton@spwhitton.name, uyennhi.qm@gmail.com,
> juri@linkov.net
>
>
>
> On Tue, 17 May 2022, Stefan Monnier wrote:
>
> >>> 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.
> >
> > Am I misunderstanding something or are you two violently agreeing?
>
> We both agree with a sword in a hand.
>
> I don't want to change the behavior on Lisp call!
> Just let me know the nice way to detect that the call is interactive and
> then I will inject the feature :-)
If you only make the search case-sensitive in the 'interactive' form,
that happens automagically.
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, (continued)
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Andreas Schwab, 2022/05/11
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Tino Calancha, 2022/05/11
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Andreas Schwab, 2022/05/11
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Tino Calancha, 2022/05/11
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Tino Calancha, 2022/05/12
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Eli Zaretskii, 2022/05/13
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Tino Calancha, 2022/05/17
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Eli Zaretskii, 2022/05/17
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Stefan Monnier, 2022/05/17
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Tino Calancha, 2022/05/17
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter,
Eli Zaretskii <=
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Stefan Monnier, 2022/05/17
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Juri Linkov, 2022/05/17
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Tino Calancha, 2022/05/18
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Sean Whitton, 2022/05/20
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Eli Zaretskii, 2022/05/21
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Tino Calancha, 2022/05/21
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Sean Whitton, 2022/05/21
- bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter, Eli Zaretskii, 2022/05/11