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: A simple solution to "Upcoming loss of usability ..." Date: Thu, 25 Jun 2015 18:37:11 +0300 Message-ID: <558C2027.5000308@yandex.ru> References: <87egkzg7gb.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 1435246669 15599 80.91.229.3 (25 Jun 2015 15:37:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Jun 2015 15:37:49 +0000 (UTC) To: Oleh Krehel , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 25 17:37:36 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 1Z89Db-00032P-FR for ged-emacs-devel@m.gmane.org; Thu, 25 Jun 2015 17:37:35 +0200 Original-Received: from localhost ([::1]:56244 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z89Da-00071W-Tm for ged-emacs-devel@m.gmane.org; Thu, 25 Jun 2015 11:37:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52824) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z89DU-00071I-CV for emacs-devel@gnu.org; Thu, 25 Jun 2015 11:37:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z89DO-00087M-5H for emacs-devel@gnu.org; Thu, 25 Jun 2015 11:37:28 -0400 Original-Received: from mail-wg0-x22d.google.com ([2a00:1450:400c:c00::22d]:32829) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z89DN-00083v-VW for emacs-devel@gnu.org; Thu, 25 Jun 2015 11:37:22 -0400 Original-Received: by wgck11 with SMTP id k11so66090742wgc.0 for ; Thu, 25 Jun 2015 08:37:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=is/KN9RgOQozWs/NaZilXIeE9Kc2qslnSavY4DMgYdM=; b=Cit1avJqtmPspiT9UJqmxOytTfOcErLWUpUeRkHqRRUJpxfg2t3VW7gZVRa14IG7LD vC7tUVjJRepA8zI+FnkNrd0PQX9y94XFy06oZSnIauaG/gOOMFRscMbgYCFjmQ7O1/L5 hLbrBeukHfTpuDBr24lgjCIoZ+ghixPtkI2CLtm/ZUBg2xGB+6fDARgzbJcOrLhXCtp8 ps/WyeUFDiSahZRm8Huk+eHI5LMr1LArYMqxPB5mO0z1iVUsVAvzv2WlV5FwzVWfJach j7qHQLVRiAZJ6tpEPSwZY9YnedjeKi7An1Yw6ELIsZo4OAGVGWn/SgAg1PZGiMjOqdIx WIIw== X-Received: by 10.194.235.227 with SMTP id up3mr7655820wjc.132.1435246633227; Thu, 25 Jun 2015 08:37:13 -0700 (PDT) Original-Received: from [192.168.0.185] (static-nbl2-118.cytanet.com.cy. [212.31.107.118]) by mx.google.com with ESMTPSA id ny7sm8187118wic.11.2015.06.25.08.37.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jun 2015 08:37:13 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 In-Reply-To: <87egkzg7gb.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22d 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:187522 Archived-At: On 06/25/2015 05:59 PM, Oleh Krehel wrote: > It seems that even though many conservative people disagree, the > "experiment" isn't going away. > > So I'm proposing the following change that could satisfy both Paul and > the conservatives (myself included): I'm not sure it'll satisfy Paul, because he seems intent on introducing actual curly quotes in the Elisp source code. Myself, I'd very much prefer this approach. > (font-lock-add-keywords > 'emacs-lisp-mode > '(("\\(`\\)\\([a-zA-Z-0-9]+\\)\\('\\)" > (0 > (compose-region > (match-beginning 1) > (match-end 1) > "‘")) > (0 > (compose-region > (match-beginning 3) > (match-end 3) > "’"))))) Otherwise, this looks pretty close to the proposed font-lock-only solution in http://lists.gnu.org/archive/html/emacs-devel/2015-06/msg00547.html And yes, we can add similar font-lock rules in emacs-lisp-mode buffers, but they'll have to handle escaped quotes a bit differently (do not hide the escaping chars).