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: [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/international and lisp/leim Date: Tue, 01 Sep 2015 16:15:28 +0200 Message-ID: <87d1y2445b.fsf@fencepost.gnu.org> References: <20150831061236.27796.57762@vcs.savannah.gnu.org> <55E3F434.2060507@yandex.ru> <55E496DC.1030608@cs.ucla.edu> <877foas9jh.fsf@gmail.com> <87vbbu4c5w.fsf@fencepost.gnu.org> <55E5A89A.70507@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1441117014 13826 80.91.229.3 (1 Sep 2015 14:16:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Sep 2015 14:16:54 +0000 (UTC) Cc: emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 01 16:16:53 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 1ZWmMn-0007IR-0B for ged-emacs-devel@m.gmane.org; Tue, 01 Sep 2015 16:16:53 +0200 Original-Received: from localhost ([::1]:54529 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWmMl-0007UF-VI for ged-emacs-devel@m.gmane.org; Tue, 01 Sep 2015 10:16:51 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45221) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWmMR-0007Tl-W6 for emacs-devel@gnu.org; Tue, 01 Sep 2015 10:16:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWmMQ-00010S-VO for emacs-devel@gnu.org; Tue, 01 Sep 2015 10:16:31 -0400 Original-Received: from fencepost.gnu.org ([208.118.235.10]:47095) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWmMK-0000zd-Gx; Tue, 01 Sep 2015 10:16:24 -0400 Original-Received: from localhost ([127.0.0.1]:60128 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.82) (envelope-from ) id 1ZWmMI-000593-JO; Tue, 01 Sep 2015 10:16:23 -0400 Original-Received: by lola (Postfix, from userid 1000) id 900AFE32D9; Tue, 1 Sep 2015 16:15:28 +0200 (CEST) In-Reply-To: <55E5A89A.70507@cs.ucla.edu> (Paul Eggert's message of "Tue, 1 Sep 2015 06:31:06 -0700") 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:189385 Archived-At: Paul Eggert writes: > David Kastrup wrote: >> I repeat the documentation help >> from the `quote' macro: > > That was a typo, which I fixed in master commit > a3c31adea4970b8a7fc7f495e6a6a6d4a93e69ce by escaping the apostrophe. > Thanks for reporting it. Not as much a typo as an oversight. That commit fixes 48 such oversights and I think that everybody should read the accompanying diff and ask himself whether he likes the results. The respective necessary changes are a nuisance to read and a nuisance to write. I think this would be a better sell if the DOC strings got some general markup for code/example that would then be output in an (unmolested) typewriter font, with the source code inside of that markup again being unmolested. It would also be nicer in case people wanted to convert DOC strings into Texinfo or HTML or other output formats where offsetting code is a good possibility. I very much should think that people would be more amenable to offset code passages in some manner rather than mangle every quote character. It's also a better sell to teach people to properly offset code passages in mailing lists/discussion groups "for best results" rather than teach the quote mangling. That means coming up with a nice form of entering code, both inline and as block, and then walk through all the doc strings (naturally, this concerns even material not containing any quote characters). It's probably a larger task than what has been done so far. But I think that the end result would be much more satisfactory and offer _independent_ benefits. And of course it would still allow selective turning off all quote treatment reasonably easily. -- David Kastrup