all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: uyennhi.qm@gmail.com, 54804@debbugs.gnu.org,
	schwab@linux-m68k.org, rpluim@gmail.com,
	spwhitton@spwhitton.name
Subject: bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter
Date: Wed, 18 May 2022 09:25:46 +0200	[thread overview]
Message-ID: <87y1yzmhdx.fsf@gmail.com> (raw)
In-Reply-To: <87ee27fd1a.fsf@gmail.com>

Eli Zaretskii <eliz@gnu.org> writes:

>> diff --git a/test/lisp/simple-tests.el b/test/lisp/simple-tests.el
>> index dcab811bb5..2baf7124d7 100644
>> --- a/test/lisp/simple-tests.el
>> +++ b/test/lisp/simple-tests.el
>> @@ -971,5 +971,27 @@ test-undo-region
>>      ;;(should (= (length (delq nil (undo-make-selective-list 5 9))) 0))
>>      (should (= (length (delq nil (undo-make-selective-list 6 9))) 0))))
>>  
>> +\f
>> +;;; Tests for `zap-to-char'
>
> Should we have the tests for zap-* functions in one place, rather than
> two?

My understanding is that we only test in `foo-tests.el' functions
beloging to `foo.el'.
For historical reasons:
`zap-to-char' is defined in simple.el
`zap-up-to-char' is defined in misc.el

We can move the latter to simple.el, then test the functions in the same file.
Some people dislike that because it affects the Git history.
I am OK with whatever the people prefer here.





  parent reply	other threads:[~2022-05-18  7:25 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 [this message]
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

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

  git send-email \
    --in-reply-to=87y1yzmhdx.fsf@gmail.com \
    --to=tino.calancha@gmail.com \
    --cc=54804@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rpluim@gmail.com \
    --cc=schwab@linux-m68k.org \
    --cc=spwhitton@spwhitton.name \
    --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 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.