unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: jwiegley@gmail.com, per@starback.se, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: lax matching is not a great default behavior
Date: Sat, 05 Dec 2015 13:15:18 +0200	[thread overview]
Message-ID: <83fuzhf8op.fsf@gnu.org> (raw)
In-Reply-To: <6741424b-fb48-48d1-a2fe-a5b755373c46@default>

> Date: Sat, 5 Dec 2015 01:27:03 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: per@starback.se, jwiegley@gmail.com, rms@gnu.org, emacs-devel@gnu.org
> 
> > > Whether it is formally defined or not does not answer the
> > > question about the name to use for Emacs users.
> > 
> > "Character folding" is the accepted terminology for this, we didn't
> > invent it.  Likewise "character sequence equivalence".
> 
> I've already agreed (from the beginning) that "character
> folding" is the right term for Emacs to use.  And that
> speaking of character equivalences is also appropriate.
> 
> (There has been some talk of adding multi-character string
> equivalences, but even if we match strings instead of just
> chars, speaking of "character foldings" makes sense to me.)

Yes, multi-character string equivalences are supported.

> I mentioned "ad hoc" character equivalences because I didn't
> think that the quotation-mark equivalences we've added are
> included in any of the Unicode equivalences (whether
> "canonically equivalent" or "compatible").

Indeed, we added equivalences for quote characters that are not
defined by Unicode database.  I think that these equivalences should
just be the initial value for the user-customizable part of the
feature.  And I don't think these few additions justify new
terminology, the existing one still describes even that.



  reply	other threads:[~2015-12-05 11:15 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<d77851fd-da55-4020-82e8-abbd13f9b048@default>
     [not found] ` <<83twnxfi0h.fsf@gnu.org>
2015-12-05  9:27   ` lax matching is not a great default behavior Drew Adams
2015-12-05 11:15     ` Eli Zaretskii [this message]
     [not found]   ` <<6741424b-fb48-48d1-a2fe-a5b755373c46@default>
     [not found]     ` <<83fuzhf8op.fsf@gnu.org>
2015-12-05 15:59       ` Drew Adams
2015-12-06  1:37         ` John Wiegley
2015-11-28  5:04 Drew Adams
2015-11-28  8:29 ` Andreas Schwab
2015-11-28 14:50   ` Drew Adams
2015-12-01  9:23   ` Andreas Röhler
2015-12-01 10:38     ` Andreas Schwab
2015-12-01 10:42       ` Yuri Khan
2015-12-01 15:38         ` Eli Zaretskii
2015-12-01 15:36     ` Eli Zaretskii
2015-11-28  8:44 ` Eli Zaretskii
     [not found]   ` <<m2mvtv1ldi.fsf@newartisans.com>
2015-11-30 16:51   ` John Wiegley
2015-12-01 14:40     ` Richard Stallman
2015-12-01 15:55       ` Eli Zaretskii
2015-12-01 18:49         ` Mark Oteiza
2015-12-01 18:56           ` Eli Zaretskii
2015-12-01 19:32             ` David Kastrup
2015-12-01 19:36               ` Eli Zaretskii
2015-12-01 19:38             ` Mark Oteiza
2015-12-01 19:36           ` Artur Malabarba
2015-12-01 19:51             ` Mark Oteiza
2015-12-01 20:01               ` Eli Zaretskii
2015-12-01 20:04                 ` Eli Zaretskii
2015-12-01 23:31                   ` Artur Malabarba
2015-12-01 23:45                     ` Drew Adams
2015-12-02  3:37                     ` Eli Zaretskii
2015-12-02  8:23                       ` martin rudalics
2015-12-02 13:45                         ` Eli Zaretskii
2015-12-02 13:06                       ` Artur Malabarba
2015-12-02 13:44                         ` Eli Zaretskii
2015-12-02 17:25                           ` Artur Malabarba
     [not found]               ` <<83r3j6j5vj.fsf@gnu.org>
     [not found]                 ` <<83poyqj5qb.fsf@gnu.org>
2015-12-01 21:17                   ` Drew Adams
2015-12-02 17:52         ` Richard Stallman
2015-12-03 22:27         ` Per Starbäck
2015-12-03 23:00           ` Drew Adams
2015-12-04  0:09             ` Artur Malabarba
2015-12-04  8:28           ` Eli Zaretskii
2015-12-04  9:33             ` Per Starbäck
2015-12-04 10:10               ` Eli Zaretskii
2015-12-04 10:57                 ` David Kastrup
2015-12-04 11:19                   ` Eli Zaretskii
2015-12-04 12:04                 ` Per Starbäck
2015-12-04 14:42                   ` Eli Zaretskii
2015-12-04 17:47                     ` John Wiegley
2015-12-05  8:02                       ` Eli Zaretskii
2015-12-04 15:55             ` Drew Adams
2015-12-04 19:05               ` Eli Zaretskii
     [not found]       ` <<83610ikvto.fsf@gnu.org>
     [not found]         ` <<CADkQgvs-WvPX=qZ0B_un9j53RF6S4V5OmDTATSW1ZwTY50o2Rg@mail.gmail.com>
     [not found]           ` <<83bna6ipn7.fsf@gnu.org>
     [not found]             ` <<45e1580a-863c-4bd7-82ec-38c27a0d930e@default>
     [not found]               ` <<831tb2ghkf.fsf@gnu.org>
2015-12-04 21:30                 ` Drew Adams
2015-12-04 22:16                   ` David Kastrup
2015-12-04 22:37                     ` Artur Malabarba
2015-12-04 23:08                       ` David Kastrup
2015-12-04 23:57                     ` Drew Adams
2015-12-05  7:53                   ` Eli Zaretskii
2015-12-01  3:54   ` Discussions that led to changes in the defaults, was: " Dmitry Gutov
2015-11-28  8:49 ` David Kastrup
     [not found] <<c9f3197f-b5f3-42f3-817c-bf560842b4d7@default>

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=83fuzhf8op.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=per@starback.se \
    --cc=rms@gnu.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 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).