From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#22147: Obsolete search-forward-lax-whitespace Date: Tue, 17 May 2016 14:55:49 -0700 (PDT) Message-ID: References: <87wpsk7dcs.fsf@mail.linkov.net> <87d1ubz3w9.fsf@mail.linkov.net> <87r3ipoofk.fsf@mail.linkov.net> <87zixcblno.fsf@mail.linkov.net> <874mfjchp1.fsf@mail.linkov.net> <87r3d4z7uf.fsf@mail.linkov.net> <8ec0f5d4-a500-42c1-bab8-eaba00f0915c@default> <87shxjjb0h.fsf@mail.linkov.net> <8e655300-1a72-4df6-87cf-91fd006cb3d7@default> <8737pgwgiu.fsf@mail.linkov.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1463536592 21103 80.91.229.3 (18 May 2016 01:56:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 18 May 2016 01:56:32 +0000 (UTC) Cc: 22147@debbugs.gnu.org, Artur Malabarba To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed May 18 03:56:18 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b2qig-0002Hy-Eb for geb-bug-gnu-emacs@m.gmane.org; Wed, 18 May 2016 03:56:18 +0200 Original-Received: from localhost ([::1]:42120 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2qic-0000Xk-F1 for geb-bug-gnu-emacs@m.gmane.org; Tue, 17 May 2016 21:56:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49043) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2qPz-0005Ck-VC for bug-gnu-emacs@gnu.org; Tue, 17 May 2016 21:37:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b2mz8-0007zH-Oo for bug-gnu-emacs@gnu.org; Tue, 17 May 2016 17:57:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43993) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2mz8-0007zC-Kv for bug-gnu-emacs@gnu.org; Tue, 17 May 2016 17:57:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1b2mz8-0001rp-9Q for bug-gnu-emacs@gnu.org; Tue, 17 May 2016 17:57:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 17 May 2016 21:57:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22147 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22147-submit@debbugs.gnu.org id=B22147.14635221677115 (code B ref 22147); Tue, 17 May 2016 21:57:02 +0000 Original-Received: (at 22147) by debbugs.gnu.org; 17 May 2016 21:56:07 +0000 Original-Received: from localhost ([127.0.0.1]:56330 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b2myE-0001qh-R2 for submit@debbugs.gnu.org; Tue, 17 May 2016 17:56:07 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:21715) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b2myD-0001qC-0f for 22147@debbugs.gnu.org; Tue, 17 May 2016 17:56:05 -0400 Original-Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u4HLtw83027478 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 17 May 2016 21:55:58 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u4HLtvu1031400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 17 May 2016 21:55:58 GMT Original-Received: from abhmp0013.oracle.com (abhmp0013.oracle.com [141.146.116.19]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u4HLtote015566; Tue, 17 May 2016 21:55:56 GMT In-Reply-To: <8737pgwgiu.fsf@mail.linkov.net> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6744.5000 (x86)] X-Source-IP: userv0022.oracle.com [156.151.31.74] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:118364 Archived-At: > > Another consideration (for me, at least): I think (and hope) that > > eventually users will be able to have multiple such lists (sets) > > of char mappings that they can choose (and mix and match - sets of > > such sets, for different purposes/contexts). IOW, I don't see just > > a single set of ad-hoc char mappings. But this is anyway for the > > future. >=20 > Yes, we have to take into consideration that in addition to the > plain customizable list we are adding to the next release, > in later versions we might also add more customizable lists, > e.g. with categories and other character groups. One possibility is to (now), instead of having an option with a single list= of ad-hoc mappings as value, have an option with an alist of such lists as= its value, where the car of an alist entry names the particular ad-hoc map= ping. See my suggestion in an earlier mail in this thread. =20 > >> Another thing we need to do is to allow customization to remove > >> default mappings. Maybe this is possible by using the same > >> defcustom with a rule like: remove default mappings when a char > >> is mapped to an empty list, e.g. > >> > >> - adding more mappings for =E2=80=98`=E2=80=99: > >> (defcustom char-fold-ad-hoc '((?` "=E2=9D=9B" "=E2=80=98" "=E2=80=9B= " "=F3=A0=80=A2" "=E2=9D=AE" "=E2=80=B9")) > >> > >> - removing default mappings for =E2=80=98`=E2=80=99: > >> (defcustom char-fold-ad-hoc '((?`)) > > > > Yes, I would think that would work (already). But I could be wrong. > > > > Thanks for taking a look at this. >=20 > After long-planned terminology improvements, I'd wait for sync between > branches to avoid merge conflicts, and then I'll submit a patch taking > into account all opinions about the default value for users who will > enable this feature in the next release. Sounds good. Thx.