From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Lisp mode syntax table Date: Tue, 18 Feb 2014 09:00:57 -0500 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1392732071 26426 80.91.229.3 (18 Feb 2014 14:01:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Feb 2014 14:01:11 +0000 (UTC) Cc: Emacs developers To: Fabrice Popineau Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 18 15:01:18 2014 Return-path: Envelope-to: ged-emacs-devel@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 1WFlEb-0002We-Ny for ged-emacs-devel@m.gmane.org; Tue, 18 Feb 2014 15:01:17 +0100 Original-Received: from localhost ([::1]:49434 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFlEa-00068a-Tt for ged-emacs-devel@m.gmane.org; Tue, 18 Feb 2014 09:01:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60406) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFlER-00068E-4p for emacs-devel@gnu.org; Tue, 18 Feb 2014 09:01:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WFlEI-0005Cy-Qg for emacs-devel@gnu.org; Tue, 18 Feb 2014 09:01:07 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:19263) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFlEI-0005Co-MY for emacs-devel@gnu.org; Tue, 18 Feb 2014 09:00:58 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFLd/lO/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GsR+QDpEKA4hhnBmBXoMV X-IPAS-Result: Av4EABK/CFFLd/lO/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GsR+QDpEKA4hhnBmBXoMV X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="47952204" Original-Received: from 75-119-249-78.dsl.teksavvy.com (HELO pastel.home) ([75.119.249.78]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 18 Feb 2014 09:00:57 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 3087860091; Tue, 18 Feb 2014 09:00:57 -0500 (EST) In-Reply-To: (Fabrice Popineau's message of "Tue, 18 Feb 2014 06:53:30 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:169739 Archived-At: > The problem may not be the class of ?| per se, but the interaction with ?: > The whole thing |rdf|:|someClass| should be considered as a symbol. Right, that is something Emacs syntax tables can't currently express. > At the moment, using smartparen to push a ?) through this symbol, > you start by putting it here : > |rdf|):|someClass| I think this step is largely unavoidable: your symbol is not syntactically atomic, instead it has structure. To avoid this step, Emacs would need to understand that the ":" infix operator can't take a parenthesized expression on its left hand side. > then here > |rdf| :)|someParen| This step OTOH is definitely avoidable. E.g. SMIE's forward-sexp would know to skip ":|someClass|" rather than just ":". > (notice that a space has been added) Seems like a misfeature of smartparen. > if ?| shouldn't be part of the symbol rather than a string delimiter. As mentioned, it has string syntax for things like |)| and | |. > In CL standard syntax, it is also used in multi lines comments > #| ... |# Yes, Emacs understands those, IIRC, Stefan