From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/international and lisp/leim Date: Tue, 1 Sep 2015 22:33:13 +0300 Message-ID: <55E5FD79.3060309@yandex.ru> References: <20150831061236.27796.57762@vcs.savannah.gnu.org> <55E3F434.2060507@yandex.ru> <55E496DC.1030608@cs.ucla.edu> <877foas9jh.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1441136024 23174 80.91.229.3 (1 Sep 2015 19:33:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Sep 2015 19:33:44 +0000 (UTC) Cc: Paul Eggert , emacs-devel@gnu.org To: Stefan Monnier , Oleh Krehel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 01 21:33:39 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 1ZWrJJ-0001bP-9f for ged-emacs-devel@m.gmane.org; Tue, 01 Sep 2015 21:33:37 +0200 Original-Received: from localhost ([::1]:57424 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWrJI-0001Yu-CR for ged-emacs-devel@m.gmane.org; Tue, 01 Sep 2015 15:33:36 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWrJ5-0001YU-2m for emacs-devel@gnu.org; Tue, 01 Sep 2015 15:33:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWrJ1-0006tt-0r for emacs-devel@gnu.org; Tue, 01 Sep 2015 15:33:23 -0400 Original-Received: from mail-wi0-x234.google.com ([2a00:1450:400c:c05::234]:37821) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWrJ0-0006t8-QW for emacs-devel@gnu.org; Tue, 01 Sep 2015 15:33:18 -0400 Original-Received: by wicfx3 with SMTP id fx3so23395565wic.0 for ; Tue, 01 Sep 2015 12:33:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=2aPyLbAStOGxsb1DSMAlQpzUDP53Yji0b5Ti782u4fM=; b=U84FqBAEiy/Z1Rp1wmACpgHWumuTwlTkfhy+BHhpnsqpqF9FTJZ+E0GCjoA8kDRJLo pIEDFrXmOCw6MPh+8HD0O0NlGbeOJAdkenH/jgz4KlSKXIw22KQEgd/m+a9MgdN7cS5R HQbv6lewLFctOKMeihbfwqtSLKr9BK1Tdxwg+w9iIDt55u5JjzHYJTzW2d39AUToWxDd xXdBstUwCmlbi7TNtvIo18kRSdty7QI4nRvqozmlRQ5o+Quizki15UYGP28jjXpAfbtE GfhLbgS0GI3GLkMUHQSVFyDVPsN8hcfbIyb7f4Y5tdo5bujtLWseb1GD59O4kFC0Au7W MPxA== X-Received: by 10.194.58.130 with SMTP id r2mr35902155wjq.72.1441135998090; Tue, 01 Sep 2015 12:33:18 -0700 (PDT) Original-Received: from [10.9.0.103] (nat.webazilla.com. [78.140.128.228]) by smtp.googlemail.com with ESMTPSA id p3sm4203398wib.16.2015.09.01.12.33.16 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Sep 2015 12:33:17 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Thunderbird/40.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::234 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:189420 Archived-At: On 09/01/2015 06:39 PM, Stefan Monnier wrote: > So I thought we were going to replace the `...' markup with ‘...’ markup > (which fixes both points at the same time if we assume that we keep > sticking to ASCII quotes for the rest, tho at the cost of using > non-ASCII markup). That would undermine another stated goal (by Paul): improve the typography in Emacs. > 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. > So maybe a better option is to refine the `...' markup to get rid of > the ambiguity. E.g.: > - `...' is only considered valid markup if ... doesn't contain any > whitespace (or some such restriction: it should be a simple rule that > still accepts most existing uses, especially those where we want to > place a hyperlink). 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. > - All other occurrences of ` and ' are treated a standalone ASCII chars > rather than as part of some markup. > So `C-x C-f' is not valid markup any more (and won't be prettified). If you like (though I'd rather keep prettifying them until we introduce a better way to emphasize them as key sequences: there's no apparent value in not making them pretty).