From: Andreas Schwab <schwab@linux-m68k.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: uyennhi.qm@gmail.com, Robert Pluim <rpluim@gmail.com>,
54804@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
spwhitton@spwhitton.name
Subject: bug#54804: 29.0.50; zap-to-char: case sensitive for upper-case letter
Date: Wed, 11 May 2022 18:11:13 +0200 [thread overview]
Message-ID: <8735hguk0u.fsf@igel.home> (raw)
In-Reply-To: <4548a66-c8f8-57de-58db-6241a1f16cc4@gmail.com> (Tino Calancha's message of "Wed, 11 May 2022 17:38:55 +0200 (CEST)")
On Mai 11 2022, Tino Calancha wrote:
> On Wed, 11 May 2022, Andreas Schwab wrote:
>
>> On Mai 11 2022, Robert Pluim wrote:
>>
>>> Return non-@code{nil} if @var{char} is an uppercase character
>>> according to Unicode. Be aware that if the Unicode tables are not yet
>>> available, e.g. during bootstrap, this gives the correct answer only
>>> for @acronym{ASCII} characters; for other characters it always returns
>>> @code{nil}.
>>
>> I don't think it is necessary to talk about bootstrapping in the manual.
> Right... How about replacing?
> "available, e.g. during bootstrap, this gives the correct answer only..."
>
> with
>
> "available, e.g. while compiling the Emac source code, this gives the
> correct answer only..."
I don't think there is a need for this at all in the manual. It could
be added as a comment in the source, though.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-05-11 16:11 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 [this message]
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
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=8735hguk0u.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=54804@debbugs.gnu.org \
--cc=eliz@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).