From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Please stop putting curly quotes into doc strings! Date: Thu, 10 Sep 2015 17:46:33 +0200 Message-ID: <87k2ry6zvq.fsf@fencepost.gnu.org> References: <55EA4821.2050401@yandex.ru> <55EBC5B8.80208@cs.ucla.edu> <55EE1B01.3010201@cs.ucla.edu> <55EEDBE7.8050903@yandex.ru> <55EEE97F.1040008@cs.ucla.edu> <55EF5FE3.4020209@yandex.ru> <55EF763E.5060500@cs.ucla.edu> <22000.36504.734886.651251@retriever.mtv.corp.google.com> <87bndag13h.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1441900047 1246 80.91.229.3 (10 Sep 2015 15:47:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 10 Sep 2015 15:47:27 +0000 (UTC) Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu, dgutov@yandex.ru, rms@gnu.org, "T.V Raman" To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 10 17:47:12 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 1Za43z-0003UM-81 for ged-emacs-devel@m.gmane.org; Thu, 10 Sep 2015 17:47:03 +0200 Original-Received: from localhost ([::1]:49969 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Za43y-0005Af-Os for ged-emacs-devel@m.gmane.org; Thu, 10 Sep 2015 11:47:02 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54884) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Za43g-0005AJ-SU for emacs-devel@gnu.org; Thu, 10 Sep 2015 11:46:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Za43f-000374-JS for emacs-devel@gnu.org; Thu, 10 Sep 2015 11:46:44 -0400 Original-Received: from fencepost.gnu.org ([208.118.235.10]:44319) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Za43d-00034B-8I; Thu, 10 Sep 2015 11:46:41 -0400 Original-Received: from localhost ([127.0.0.1]:57353 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.82) (envelope-from ) id 1Za43V-0002AO-Oj; Thu, 10 Sep 2015 11:46:34 -0400 Original-Received: by lola (Postfix, from userid 1000) id 09447DF4FD; Thu, 10 Sep 2015 17:46:33 +0200 (CEST) In-Reply-To: (Stefan Monnier's message of "Thu, 10 Sep 2015 11:12:21 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.10 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:189808 Archived-At: Stefan Monnier writes: >> git grep =E2=80=98 > > I don't see anything serious in this output. Again, if there's > a problem somewhere, make a specific request. We don't have a general > rule against arbitrary character code appearing in our code base. Well, various text files like etc/NEWS:nil for Emacs local time, t for Universal Time, \u2018wall\u2019 f= or system wall etc/NEWS:clock time, or a string as in \u2018set-time-zone-rule\u2019 for a= time zone etc/NEWS:rule. The affected functions are \u2018current-time-string\u2019, etc/NEWS:\u2018current-time-zone\u2019, \u2018decode-time\u2019, and \u2018= format-time-string\u2019. The etc/NEWS:function \u2018encode-time\u2019, which already accepted a simple = time zone rule etc/PROBLEMS: No fonts match \u2018-*-fixed-medium-r-*--6-*-*-*-*-*-iso885= 9-1\u2019 Comments and messages like lisp/cedet/mode-local.el:;; \u2018require\u2019 by (defvar find-function-re= gexp-alist) and lisp/cedet/mode-local.el: "For \u2018elisp-xref-find-def-functions\u2019; = add overloads for SYMBOL." lisp/cedet/mode-local.el: ;; don't want to list the same function twic= e. So order \u2018modes\u2019 lisp/cedet/mode-local.el: "Regexp used by \u2018xref-find-definitions\u201= 9 when searching for a lisp/cedet/mode-local.el: "Function used by \u2018xref-find-definitions\u2= 019 when searching for an outcommented stuff that would become non-standard when commented back in: lisp/emacs-lisp/advice.el:;; (y-or-n-p (format "\u2018%s\u2019 doe= s not exist, create? " (ad-get-arg 0)))) lisp/emacs-lisp/bytecomp.el: ;; (message "%s not compiled because of \= u2018no-byte-compile: %s\u2019" lisp/emacs-lisp/bytecomp.el: ;; "\u2018%s\u2019 is n= ot a known condition name lisp/emacs-lisp/bytecomp.el: ;; "\u2018%s\u2019 is not a known c= ondition name (in condition-case)" various messages like lisp/info.el: (format "*Index for \u2018%s\u2019*::" (cdr (nth= 0 nodeinfo))) lisp/info.el: (format "*Index for \u2018%s\u2019*" topic= )))) lisp/info.el: (insert "This is a list of search results produced by \u201= 8info-apropos\u2019.\n\n") lisp/info.el: (insert "Index entries that match \u2018" (nth 1 nodeinfo) = "\u2019:\n\n") lisp/info.el: (setq nodename (format "Index for \u2018%s\u2019" string)) lisp/info.el: "The following packages match the keyword \u2018" nodenam= e "\u2019:\n\n") lisp/info.el: "Description of the package \u2018" nodename "\u2019:\n\n= ") The English adventure "dunnet" lisp/play/dunnet.el: open it. You may just use \u2018in\u2019 or walk in = the direction of the door. lisp/play/dunnet.el:- You can save your game with the \u2018save\u2019 comm= and, and use restore it lisp/play/dunnet.el: with the \u2018restore\u2019 command. lisp/play/dunnet.el: (dun-mprincl "No more questions, just do \u2018an= swer foo\u2019.") lisp/play/dunnet.el:says: This VAX is named \u2018pokey\u2019. To type on = the console, use the lisp/play/dunnet.el:\u2018type\u2019 command. The exit is to the east." lisp/play/dunnet.el:is a sign on the wall that reads: \u2018receiving room\= u2019." lisp/play/dunnet.el:that says \u2018put treasures here for points\u2019." lisp/play/dunnet.el:switch on the wall labeled \u2018BL\u2019. There are d= oors to the west and north." lisp/play/dunnet.el:history. On the blackboard is written, \u2018No childr= en allowed downstairs.\u2019 lisp/play/dunnet.el:There is a door to the east with an \u2018exit\u2019 si= gn on it. There is another lisp/play/dunnet.el:does have a sign that says: This machine's name is \u20= 18endgame\u2019. The lisp/play/dunnet.el:order to get by. Use the \u2018answer\u2019 command to= answer the question." lisp/play/dunnet.el: Type the \u2018reset\u2019 command to type on= the PC. lisp/play/dunnet.el:"The paper says: Don't forget to type \u2018help\u2019 = for help. Also, remember lisp/play/dunnet.el:this word: \u2018worms\u2019" lisp/play/dunnet.el:written: \u2018For key upgrade, put key in here.\u2019" lisp/play/dunnet.el:"It says \u2018express mail\u2019 on it." lisp/play/dunnet.el:"It is a 35 passenger bus with the company name \u2018m= obytours\u2019 on it." and a few others. You stated that you considered the source to be in "pristine state" without curly quotes and I said that this was not quite accurate. Now you try to make it about how "serious" this is supposed to be, conveniently eliding the whole preceding context not supporting this subject. I don't think I know any other mailing list where this sort of quoting game is as popular as on the Emacs developer list. Appears to be some culture thing but it's definitely annoying, not least of all because it leads to the same points being made over and over and promotes exasperation as a main decision-finding process. --=20 David Kastrup