From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 37036@debbugs.gnu.org
Subject: bug#37036: [PATCH] Inconsistent ASCII and Latin char categories
Date: Thu, 15 Aug 2019 19:59:53 +0300 [thread overview]
Message-ID: <83pnl6pdo6.fsf@gnu.org> (raw)
In-Reply-To: <C0236B82-354A-49C6-B525-7BBF535FA786@acm.org> (message from Mattias Engdegård on Thu, 15 Aug 2019 18:30:47 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Thu, 15 Aug 2019 18:30:47 +0200
> Cc: 37036@debbugs.gnu.org
>
> 15 aug. 2019 kl. 18.23 skrev Eli Zaretskii <eliz@gnu.org>:
> >
> > In any case, how to justify the fact that, say, "naïve", has
> > characters from different scripts?
>
> The proposed change does not change the categories of any character in that string.
What about "abcdef^A^B"? Does M-f stop before the control characters?
I guess I don't understand the rationale for the change. Categories
are Emacs's invention, and their purpose is mostly to allow us to use
regexps for searching certain characters, and other similar
subtleties. Your rationale seems to be some attempt to be formally
"consistent". But this is not a formal attribute, it is entirely
ad-hoc, as can be easily seen by just looking at the list of the
categories.
So I wonder why would we want to rock that particular boat.
next prev parent reply other threads:[~2019-08-15 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 12:17 bug#37036: [PATCH] Inconsistent ASCII and Latin char categories Mattias Engdegård
2019-08-15 15:27 ` Eli Zaretskii
2019-08-15 15:46 ` Mattias Engdegård
2019-08-15 16:23 ` Eli Zaretskii
2019-08-15 16:30 ` Mattias Engdegård
2019-08-15 16:59 ` Eli Zaretskii [this message]
2019-08-15 17:37 ` Mattias Engdegård
2019-08-15 19:23 ` Eli Zaretskii
2019-08-15 19:46 ` Eli Zaretskii
2019-08-15 22:19 ` Mattias Engdegård
2019-08-16 9:33 ` Eli Zaretskii
2019-08-16 10:48 ` Mattias Engdegård
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=83pnl6pdo6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37036@debbugs.gnu.org \
--cc=mattiase@acm.org \
/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.