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: Why is ,. (comma-dot) treated specially? Date: Thu, 22 Jan 2015 08:54:01 -0500 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1421934853 13555 80.91.229.3 (22 Jan 2015 13:54:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 22 Jan 2015 13:54:13 +0000 (UTC) Cc: emacs-devel To: Artur Malabarba Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 22 14:54:12 2015 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 1YEID5-0000hr-L1 for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2015 14:54:11 +0100 Original-Received: from localhost ([::1]:53339 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YEID4-0004Pf-Uh for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2015 08:54:10 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56243) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YEID1-0004Pa-QM for emacs-devel@gnu.org; Thu, 22 Jan 2015 08:54:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YEICx-0003Z1-Oc for emacs-devel@gnu.org; Thu, 22 Jan 2015 08:54:07 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:33942) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YEICx-0003Yl-Lp for emacs-devel@gnu.org; Thu, 22 Jan 2015 08:54:03 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwPAOwQflSnWBWM/2dsb2JhbABbgweDYIVaxR0EAgKBJBcBAQEBAQF8hAMBAQMBViMFCwsOJhIUGA0kiEoJ1lkBAQEHAQEBAR6QbweESAWLAaYmhBkhgncBAQE X-IPAS-Result: AjwPAOwQflSnWBWM/2dsb2JhbABbgweDYIVaxR0EAgKBJBcBAQEBAQF8hAMBAQMBViMFCwsOJhIUGA0kiEoJ1lkBAQEHAQEBAR6QbweESAWLAaYmhBkhgncBAQE X-IronPort-AV: E=Sophos;i="5.07,502,1413259200"; d="scan'208";a="108464466" Original-Received: from 167-88-21-140.cpe.teksavvy.com (HELO pastel.home) ([167.88.21.140]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 Jan 2015 08:54:02 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id F053F2A58; Thu, 22 Jan 2015 08:54:01 -0500 (EST) In-Reply-To: (Artur Malabarba's message of "Wed, 21 Jan 2015 21:58:20 -0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.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:181595 Archived-At: > Is this a feature that was planned but is not yet finished? Why is the > dot handled specially after a comma if we don't do anything with it? Using special characters (like dot) in symbols is risky. Always has been always will be. > I ran into a problem the other day where writing > `(message ,.some-var) > unexpectedly split the .some-var symbol without evaluating anything: > (message (\,\. some-var)) I'm not surprised it doesn't do what you expected, but I'm admittedly surprised of the actual behavior. In any case, this looks like a plain bug. Stefan