From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#30815: 26.0.91; unicode right single quote mark with syntax entry of w not respected by forward-word Date: Wed, 14 Mar 2018 18:09:11 +0200 Message-ID: <838tauskpk.fsf@gnu.org> References: <87fu53xxzc.fsf@gmail.com> <87y3ivwg0h.fsf@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1521043695 21691 195.159.176.226 (14 Mar 2018 16:08:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 14 Mar 2018 16:08:15 +0000 (UTC) Cc: 30815@debbugs.gnu.org, npostavs@gmail.com To: Aaron Jensen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Mar 14 17:08:10 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ew8wj-0005W7-EB for geb-bug-gnu-emacs@m.gmane.org; Wed, 14 Mar 2018 17:08:09 +0100 Original-Received: from localhost ([::1]:47164 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ew8yk-0004Ge-R9 for geb-bug-gnu-emacs@m.gmane.org; Wed, 14 Mar 2018 12:10:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43800) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ew8yc-0004GK-01 for bug-gnu-emacs@gnu.org; Wed, 14 Mar 2018 12:10:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ew8yY-0003SF-QS for bug-gnu-emacs@gnu.org; Wed, 14 Mar 2018 12:10:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:53825) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ew8yY-0003S9-Lv for bug-gnu-emacs@gnu.org; Wed, 14 Mar 2018 12:10:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ew8yY-0001PH-Fo for bug-gnu-emacs@gnu.org; Wed, 14 Mar 2018 12:10:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 14 Mar 2018 16:10:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30815 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: confirmed notabug Original-Received: via spool by 30815-submit@debbugs.gnu.org id=B30815.15210437665327 (code B ref 30815); Wed, 14 Mar 2018 16:10:02 +0000 Original-Received: (at 30815) by debbugs.gnu.org; 14 Mar 2018 16:09:26 +0000 Original-Received: from localhost ([127.0.0.1]:33485 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ew8xx-0001Nr-Tj for submit@debbugs.gnu.org; Wed, 14 Mar 2018 12:09:26 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:52653) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ew8xw-0001Ne-Md for 30815@debbugs.gnu.org; Wed, 14 Mar 2018 12:09:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ew8xo-0002wj-Ai for 30815@debbugs.gnu.org; Wed, 14 Mar 2018 12:09:19 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:56559) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ew8xo-0002wb-6s; Wed, 14 Mar 2018 12:09:16 -0400 Original-Received: from [176.228.60.248] (port=1372 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ew8xn-0007Pe-MP; Wed, 14 Mar 2018 12:09:16 -0400 In-reply-to: (message from Aaron Jensen on Tue, 13 Mar 2018 19:43:03 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:144265 Archived-At: > From: Aaron Jensen > Date: Tue, 13 Mar 2018 19:43:03 -0700 > Cc: 30815@debbugs.gnu.org > > Is the case for this when two words of different scripts are next to > each other? I suppose that'd make sense if they also didn't have a > space between them for some reason (probably possible with some > languages) > > > Maybe there is some other way to get the wanted behaviour though. I > > also found Bug#13129 asking about this. > > Since the right quote is part of the General Punctuation script > (afaict), what if some scripts, like that one, were treated neutrally? > That is, they derived their behavior solely from the syntax entry. > This is probably a bad idea for a number of reasons I don't even know > I don't know. We could introduce a new script, say, 'punctuation', and treat that specially. Doing that with all the characters of the 'symbol' script is probably not what users will expect, I invite you to look in charscript.el where you will see what Unicode blocks belong to 'symbol'. So we will have to decide which characters to assign to that new script. But before we discuss this issue more, I think we need to talk about the goals. E.g., is this only for text-derived modes, or also for programming modes? More generally, why did you want to change the syntax entry of ’ ? The next question is what other characters need this special handling, and how many of them are there? Armed with answers to these questions, we could then decide how to implement the requested feature, if at all. Btw, you should know that in some quarters using ’ as an apostrophe is anathema: they maintain one should use u+02B7 MODIFIER LETTER APOSTROPHE instead, in particular because it doesn't have the script disparity issue in this context. See, for example, this URL: https://tedclancy.wordpress.com/2015/06/03/which-unicode-character-should-represent-the-english-apostrophe-and-why-the-unicode-committee-is-very-wrong/