From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#23425: master branch: `message' wrongly corrupts ' to curly quote. Date: Fri, 9 Jun 2017 15:51:03 -0700 (PDT) Message-ID: <0846dd8a-804d-4df9-8a45-979a9d49b5d6@default> References: <20170603205331.GA2130@acm.fritz.box> <20170605162737.GA30946@acm.fritz.box> <20170605203753.GB30946@acm.fritz.box> <20170607191344.GB2430@acm.fritz.box> <20170608173400.GA2662@acm.fritz.box> <20170609194141.GA3410@acm.fritz.box> <3b2a119e-7c2e-e906-dea0-ae91aca80f33@cs.ucla.edu> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1497048733 31241 195.159.176.226 (9 Jun 2017 22:52:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 9 Jun 2017 22:52:13 +0000 (UTC) Cc: 23425@debbugs.gnu.org To: Paul Eggert , Alan Mackenzie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jun 10 00:52:09 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dJSlE-0007nB-LU for geb-bug-gnu-emacs@m.gmane.org; Sat, 10 Jun 2017 00:52:08 +0200 Original-Received: from localhost ([::1]:56607 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dJSlI-0002qB-Hx for geb-bug-gnu-emacs@m.gmane.org; Fri, 09 Jun 2017 18:52:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46645) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dJSlC-0002pv-8F for bug-gnu-emacs@gnu.org; Fri, 09 Jun 2017 18:52:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dJSl8-00083p-8S for bug-gnu-emacs@gnu.org; Fri, 09 Jun 2017 18:52:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:34855) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dJSl8-00083f-5F for bug-gnu-emacs@gnu.org; Fri, 09 Jun 2017 18:52:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dJSl7-0003aK-Ob for bug-gnu-emacs@gnu.org; Fri, 09 Jun 2017 18:52:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 09 Jun 2017 22:52:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 23425 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 23425-submit@debbugs.gnu.org id=B23425.149704867913727 (code B ref 23425); Fri, 09 Jun 2017 22:52:01 +0000 Original-Received: (at 23425) by debbugs.gnu.org; 9 Jun 2017 22:51:19 +0000 Original-Received: from localhost ([127.0.0.1]:37532 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dJSkR-0003ZK-At for submit@debbugs.gnu.org; Fri, 09 Jun 2017 18:51:19 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:38978) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dJSkP-0003Z6-IX for 23425@debbugs.gnu.org; Fri, 09 Jun 2017 18:51:18 -0400 Original-Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v59Mp749003737 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 9 Jun 2017 22:51:07 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id v59Mp73J011834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Jun 2017 22:51:07 GMT Original-Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id v59Mp46Q009558; Fri, 9 Jun 2017 22:51:05 GMT In-Reply-To: <3b2a119e-7c2e-e906-dea0-ae91aca80f33@cs.ucla.edu> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 12.0.6767.5000 (x86)] X-Source-IP: userv0022.oracle.com [156.151.31.74] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.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" Xref: news.gmane.org gmane.emacs.bugs:133424 Archived-At: > Although the proposed function is similar to the message > function, it differs in that it does not restyle quotes. It is function `message', not your proposed function `memo', that should not "restyle" quote chars. If you want a function that restyles quote chars then _that_ should be a new function. Existing code - and future code - that uses `message' should not have any such "restyling" imposed on it. If you had simply offered to add such a new function, I doubt that anyone would have complained. Seriously. Instead, you had to impose this incompatible and specialized prettification on the longstanding and ubiquitous, stalwart workhorse function `message'. That was a grave design error. It should never have been allowed. > it depends not only on doing the work for Emacs itself, but also for > third-party software written in Elisp. These are significant costs. Really? You are actually arguing for concern about 3rd-party maintenance work now? This is like DJT complaining about fake news from others. Where was that concern when you hijacked `message'? Where was your proposal to create another function, then? > Users should not be required to litter their code with hard-to-read > formats like "Can%'t encode %`0x%x%' with this buffer%'s coding system" > to get decent quoting. And now you are concerned about users? Where was that concern when you imposed an incompatible change on `message'? > existing callers such as (message "%s" filename) would continue > to operate as before, and would not need to be changed. Where was your concern about letting `message' callers be able to continue operating as before, before?