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: [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/international and lisp/leim Date: Tue, 01 Sep 2015 22:34:11 -0400 Message-ID: References: <20150831061236.27796.57762@vcs.savannah.gnu.org> <55E3F434.2060507@yandex.ru> <55E496DC.1030608@cs.ucla.edu> <877foas9jh.fsf@gmail.com> <55E5FD79.3060309@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1441162741 2127 80.91.229.3 (2 Sep 2015 02:59:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 2 Sep 2015 02:59:01 +0000 (UTC) Cc: Paul Eggert , Oleh Krehel , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 02 04:58:51 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 1ZWyGB-0005lF-Lo for ged-emacs-devel@m.gmane.org; Wed, 02 Sep 2015 04:58:51 +0200 Original-Received: from localhost ([::1]:60917 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWyGB-0007zf-3t for ged-emacs-devel@m.gmane.org; Tue, 01 Sep 2015 22:58:51 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37754) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWyFy-0007zV-QV for emacs-devel@gnu.org; Tue, 01 Sep 2015 22:58:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWyFu-00031q-Qr for emacs-devel@gnu.org; Tue, 01 Sep 2015 22:58:38 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:46225) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWxsL-0000m0-Mj for emacs-devel@gnu.org; Tue, 01 Sep 2015 22:34:13 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AzFgA731xV//rn92hcgxCEAoVVu0CHSwQCAoE8OhMBAQEBAQEBgQpBBYNdAQEDAVYjBQsLDiYSFBgNJC6ICQjPIwEBAQEGAgEfizqFBQeELQW1BCOCO4FZIoJ4AQEB X-IPAS-Result: A0AzFgA731xV//rn92hcgxCEAoVVu0CHSwQCAoE8OhMBAQEBAQEBgQpBBYNdAQEDAVYjBQsLDiYSFBgNJC6ICQjPIwEBAQEGAgEfizqFBQeELQW1BCOCO4FZIoJ4AQEB X-IronPort-AV: E=Sophos;i="5.13,465,1427774400"; d="scan'208";a="162123402" Original-Received: from 104-247-231-250.cpe.teksavvy.com (HELO pastel.home) ([104.247.231.250]) by ironport2-out.teksavvy.com with ESMTP; 01 Sep 2015 22:34:11 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id C7FB96236A; Tue, 1 Sep 2015 22:34:11 -0400 (EDT) In-Reply-To: <55E5FD79.3060309@yandex.ru> (Dmitry Gutov's message of "Tue, 1 Sep 2015 22:33:13 +0300") 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:189443 Archived-At: > That would undermine another stated goal (by Paul): improve the typography > in Emacs. I think this goal should have very low priority. >> But if we start using curly quotes everywhere, then we're back with the >> ambiguity, so that's not a good solution. > So what's the exact ambiguity that you have in mind? Code references or > snippets vs. everything else like key sequences? > Then I definitely misunderstood you a while back. W.r.t ambiguity, the main problem I see is that we currently can never be sure that when we see a ` followed by a ' the two actually form a pair. A human usually can tell, but a program can't get it right 100% of the time. > We might also want to support code snippets like `(progn (foo bar foo))'. > At least, elisp-completion-at-point relies on snippets being quoted > that way now. We can detect these using paired parens. Not sure I want to go down that road. What about `(foo 'a 'b)' ? AFAIK it's not very common (yet?) to quote code that way, and I'm not sure we want to get into the habit of quoting it that way. I could see the need/advantage of quoting code reliably, but I don't think `...' is a good way to do it. Stefan