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#10494: 24.0.92; Syntax table and non-ASCII character interaction Date: Sat, 13 Aug 2016 21:35:23 +0300 Message-ID: <83lh00cyac.fsf@gnu.org> References: <87wpjoxi5q.fsf@users.sourceforge.net> <83h9arfhw9.fsf@gnu.org> <87h9apy5ob.fsf@users.sourceforge.net> <83eg5tdume.fsf@gnu.org> <87lh00x0r1.fsf@users.sourceforge.net> <83vaz4dca8.fsf@gnu.org> <87inv4wy2x.fsf@users.sourceforge.net> <83shu8d9kb.fsf@gnu.org> <87fuq8wn6u.fsf@users.sourceforge.net> 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 1471113380 25335 195.159.176.226 (13 Aug 2016 18:36:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 13 Aug 2016 18:36:20 +0000 (UTC) Cc: 10494@debbugs.gnu.org, aaronecay@gmail.com To: npostavs@users.sourceforge.net Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Aug 13 20:36:16 2016 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 1bYdn6-0006RL-Bz for geb-bug-gnu-emacs@m.gmane.org; Sat, 13 Aug 2016 20:36:16 +0200 Original-Received: from localhost ([::1]:58250 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYdn3-00033m-B7 for geb-bug-gnu-emacs@m.gmane.org; Sat, 13 Aug 2016 14:36:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46272) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYdmx-00033e-JK for bug-gnu-emacs@gnu.org; Sat, 13 Aug 2016 14:36:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bYdms-00061j-Fp for bug-gnu-emacs@gnu.org; Sat, 13 Aug 2016 14:36:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:58866) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYdms-00061f-Cu for bug-gnu-emacs@gnu.org; Sat, 13 Aug 2016 14:36:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bYdms-0003Z5-5i for bug-gnu-emacs@gnu.org; Sat, 13 Aug 2016 14:36: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: Sat, 13 Aug 2016 18:36:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 10494 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: confirmed Original-Received: via spool by 10494-submit@debbugs.gnu.org id=B10494.147111334613679 (code B ref 10494); Sat, 13 Aug 2016 18:36:02 +0000 Original-Received: (at 10494) by debbugs.gnu.org; 13 Aug 2016 18:35:46 +0000 Original-Received: from localhost ([127.0.0.1]:56578 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bYdmc-0003YY-IL for submit@debbugs.gnu.org; Sat, 13 Aug 2016 14:35:46 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:55258) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bYdma-0003YL-NT for 10494@debbugs.gnu.org; Sat, 13 Aug 2016 14:35:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bYdmU-00060P-84 for 10494@debbugs.gnu.org; Sat, 13 Aug 2016 14:35:39 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:36506) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYdmO-000609-GI; Sat, 13 Aug 2016 14:35:32 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1863 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bYdmL-0003GA-AN; Sat, 13 Aug 2016 14:35:30 -0400 In-reply-to: <87fuq8wn6u.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net) 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:122180 Archived-At: > From: npostavs@users.sourceforge.net > Cc: 10494@debbugs.gnu.org, aaronecay@gmail.com > Date: Sat, 13 Aug 2016 14:14:49 -0400 > > > Sorry, I guess I was thinking of \cl. It will not match ’, although > > it might be expected. > > Which could be fixed by (modify-category-entry ?’ ?l). This is Emacs, right? But the fact that you can do this doesn't yet mean you should want to, or that we should encourage it. > I would suggest this additional docstring patch, because I was confused > at first as to what CATEGORY was supposed to be (I looked around a bit > for how to create some kind of "category object"): > > diff --git i/src/category.c w/src/category.c > index 4397f66..31ac2ec 100644 > --- i/src/category.c > +++ w/src/category.c > @@ -336,6 +336,7 @@ DEFUN ("modify-category-entry", Fmodify_category_entry, > the current buffer's category table. > CHARACTER can be either a single character or a cons representing the > lower and upper ends of an inclusive character range to modify. > +CATEGORY must be a category name (a character between ` ' and `~'). > If optional fourth argument RESET is non-nil, > then delete CATEGORY from the category set instead of adding it. */) > (Lisp_Object character, Lisp_Object category, Lisp_Object table, Lisp_Object reset) How about mentioning describe-categories as well? > > Anyway, my point is that these char-tables should really be treated as > > read-only by Lisp applications. > > Right, but I think this bug is about the user modifying stuff. Which is even less recommendable, IMO. How many users really understand the implications?