From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#20385: [PATCH] Support curved quotes in doc strings Date: Fri, 15 May 2015 22:09:20 +0300 Message-ID: <55564460.4020208@yandex.ru> References: <1429555155-4695-1-git-send-email-eggert@cs.ucla.edu> <5552FDAC.4080004@cs.ucla.edu> <55534080.6010400@yandex.ru> <555369FD.30701@cs.ucla.edu> <5553D12F.7000809@yandex.ru> <5554155E.70000@cs.ucla.edu> <55547DC6.3090509@yandex.ru> <5555A4ED.8090500@cs.ucla.edu> <55562BB0.2010605@yandex.ru> <555640E9.4060203@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 1431717029 20449 80.91.229.3 (15 May 2015 19:10:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 May 2015 19:10:29 +0000 (UTC) To: Paul Eggert , 20385@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 15 21:10:15 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1YtKzt-0003gB-3E for geb-bug-gnu-emacs@m.gmane.org; Fri, 15 May 2015 21:10:13 +0200 Original-Received: from localhost ([::1]:32798 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtKzs-0005sp-E3 for geb-bug-gnu-emacs@m.gmane.org; Fri, 15 May 2015 15:10:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtKzo-0005rZ-HV for bug-gnu-emacs@gnu.org; Fri, 15 May 2015 15:10:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YtKzk-00039y-Fp for bug-gnu-emacs@gnu.org; Fri, 15 May 2015 15:10:08 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:36498) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtKzk-00038t-C2 for bug-gnu-emacs@gnu.org; Fri, 15 May 2015 15:10:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YtKzj-0006Q2-Ft for bug-gnu-emacs@gnu.org; Fri, 15 May 2015 15:10:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 15 May 2015 19:10:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20385 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 20385-submit@debbugs.gnu.org id=B20385.143171697124632 (code B ref 20385); Fri, 15 May 2015 19:10:03 +0000 Original-Received: (at 20385) by debbugs.gnu.org; 15 May 2015 19:09:31 +0000 Original-Received: from localhost ([127.0.0.1]:46473 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YtKzD-0006PE-1e for submit@debbugs.gnu.org; Fri, 15 May 2015 15:09:31 -0400 Original-Received: from mail-wg0-f42.google.com ([74.125.82.42]:36505) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YtKzB-0006P1-EH for 20385@debbugs.gnu.org; Fri, 15 May 2015 15:09:30 -0400 Original-Received: by wgbhc8 with SMTP id hc8so90499784wgb.3 for <20385@debbugs.gnu.org>; Fri, 15 May 2015 12:09:23 -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=6A7eoJrX8xs5mCSRxU0uGIv1fe1MzoFbMYtPUqGut7I=; b=r41CNNqhBwahDKbrrtWN30J1NpayVT3KXjjffeaz5BiSFP/upKu6cNk3tylPfWMGIA dN2hHyMO0v7fxaeZ7E2on1YeZjsV4FT91H0mafcWy3/HNlKMIFbcAOkbZ5omZC8FHVwh kgde68XkxL1Osc11LTWETgN4jsGv6KcW+p/ae0Y7KuqrcQwaThnHZS2Qu4FaGDWDWwXo HNsnHC1QLeUE4UqzBuuktA+OtF4xTscKBkrWAd58rFHg1YaiGzM7GpVHdY5DjQA+TUPb J5BOqiRgNMClet6uteXh0bLoKctuc8yVc8LONDVq81PZA1+GlVP3gsSyrVR0t6fgFe6b reGQ== X-Received: by 10.194.178.227 with SMTP id db3mr20819486wjc.82.1431716963904; Fri, 15 May 2015 12:09:23 -0700 (PDT) Original-Received: from [192.168.1.2] ([82.102.93.54]) by mx.google.com with ESMTPSA id i6sm3818428wjf.29.2015.05.15.12.09.23 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 May 2015 12:09:23 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 In-Reply-To: <555640E9.4060203@cs.ucla.edu> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:102840 Archived-At: On 05/15/2015 09:54 PM, Paul Eggert wrote: > That's an independent issue: it can be done no matter what quoting > regime the source code uses. Terrific. Then there's no need to worry too much about the diagnostic messages. > I'm not that worried about the cost of implementation now. I'm worried > about the long-term cost of having a quoting regime that requires > documentation and explanation. What's there to explain? Quoting will work as before, it'll only be displayed differently (and users could even opt out of that). > It's simpler and easier to explain if > the doc string looks the same in the UI as it does while you're editing > it. My "lambda"s have been rendered in Greek for quite a while. We even have a minor mode for things like this now. > For example, you can easily cut and paste from the UI into the doc > string source when composing a new doc string, which is something that > doesn't work well for either GCC or Coreutils. Why wouldn't that work in Emacs either way? The only place that seems like it'll have this problem is the Info buffers, but they have a lot of other markup that looks differently in the source anyway. >> - Using unicode for markup is a complication (e.g. with certain mail >> clients, but some other instances might come up). > > It's a complication we already have, as we already use UTF-8 in a few > doc strings. For example, the documentation for prettify-symbols-mode > uses UTF-8 curved double-quotes. Does it? I can't find that. But either way, allowing unicode in sources (why we do, obviously) and using unicode characters as ubiquitous markup are two very different things. > Nor do I. This is a transition process, with the long-term goal of > quoting via quotes rather than via grave accent and apostrophe. If we use rendering via font-lock, there will be no transition process.