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: Fri, 26 Jun 2015 00:10:19 +0300 Message-ID: <558C6E3B.5040105@yandex.ru> References: <87egkzg7gb.fsf@gmail.com> <558C2E25.10303@cs.ucla.edu> <87mvzng1ud.fsf@gmail.com> <558C690D.3000208@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1435266660 29431 80.91.229.3 (25 Jun 2015 21:11:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Jun 2015 21:11:00 +0000 (UTC) Cc: emacs-devel@gnu.org To: Paul Eggert , Oleh Krehel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 25 23:11:00 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 1Z8EQE-0003Dq-QA for ged-emacs-devel@m.gmane.org; Thu, 25 Jun 2015 23:10:58 +0200 Original-Received: from localhost ([::1]:57466 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8EQE-0000VJ-6z for ged-emacs-devel@m.gmane.org; Thu, 25 Jun 2015 17:10:58 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44951) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8EPr-0000VD-J9 for emacs-devel@gnu.org; Thu, 25 Jun 2015 17:10:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z8EPm-0003Qf-QB for emacs-devel@gnu.org; Thu, 25 Jun 2015 17:10:35 -0400 Original-Received: from mail-wg0-x234.google.com ([2a00:1450:400c:c00::234]:36631) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8EPm-0003BM-JD for emacs-devel@gnu.org; Thu, 25 Jun 2015 17:10:30 -0400 Original-Received: by wguu7 with SMTP id u7so72758751wgu.3 for ; Thu, 25 Jun 2015 14:10:21 -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=56JL5fyES95wheNSnM3YPbvu3UFjHbF5ugA+cmxNVl8=; b=LNF4SlrTDuVNGICPZmNBSvjK8D6NwqSw3uK/d3juDdDn4c1AqLq+ZfSrXia7vMFPI5 +Hmux6+9FKD9FT0v61XL6o1Q0edtvwQywjIJDTGRuu0jxW7kGS+n+AKvUtNVyvWvBRe0 xN5Zvz6Qzw4Cu7t/Xr6mPskNwZ+MQCgDK+d9ZDJnoz6hyx7X8VKjMBFUvx/9HSEAdvQI 8w1dxEe2TgU5QjE/asjE1hq38DvScIA92lLLGC0NlFIUiVyQ5ZOXBigyIju98Q4defKP N9BZJ14G7N24NYFl9dqLDm7lUsnu+LPgfurE+aucEL/aMRnamqjygi/efiPcvEvfoan7 C+OA== X-Received: by 10.180.73.10 with SMTP id h10mr9309128wiv.3.1435266621580; Thu, 25 Jun 2015 14:10:21 -0700 (PDT) Original-Received: from [192.168.1.2] ([82.102.93.54]) by mx.google.com with ESMTPSA id a9sm9321481wiv.13.2015.06.25.14.10.20 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jun 2015 14:10:21 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 In-Reply-To: <558C690D.3000208@cs.ucla.edu> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::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:187534 Archived-At: On 06/25/2015 11:48 PM, Paul Eggert wrote: > Yes, I would like the markup to head that way. But the Emacs source > docstrings have largely not needed to change, and there's no need to > change them right now. That's sneaky wording. You obviously want them to change. The majority of people opposing don't want the curly quotes in docstrings, nor do they want to have two standards at the same time (now and then effectively forever). Of course, the question of whether to use curly quotes in the docstrings or render them later is orthogonal enough to the choice of using font-lock or substitute-command-keys, but I think I gave a few arguments in favor of the former. > But if we want to > use font-lock to alter how quotes are displayed, these heuristics won't > work well, as they'll fail to alter many quotes that they should alter. Why do you think so? We can alter any quotes we want using font-lock too. No real need to alter them in pairs either, if we want to disregard Richard's advice, and we're fine with using escaping more often.