From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: text-quoting-style Date: Fri, 28 Aug 2015 10:37:42 +0300 Message-ID: <83pp2750e1.fsf@gnu.org> References: <55E0085D.3000404@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1440747485 29737 80.91.229.3 (28 Aug 2015 07:38:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 28 Aug 2015 07:38:05 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 28 09:37:52 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 1ZVEEP-0007GJ-OW for ged-emacs-devel@m.gmane.org; Fri, 28 Aug 2015 09:37:49 +0200 Original-Received: from localhost ([::1]:46505 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZVEEO-0004h1-Tc for ged-emacs-devel@m.gmane.org; Fri, 28 Aug 2015 03:37:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38798) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZVEEL-0004go-LQ for emacs-devel@gnu.org; Fri, 28 Aug 2015 03:37:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZVEEI-0006ll-EA for emacs-devel@gnu.org; Fri, 28 Aug 2015 03:37:45 -0400 Original-Received: from mtaout29.012.net.il ([80.179.55.185]:54361) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZVEEI-0006lb-6B for emacs-devel@gnu.org; Fri, 28 Aug 2015 03:37:42 -0400 Original-Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0NTS007007M4IS00@mtaout29.012.net.il> for emacs-devel@gnu.org; Fri, 28 Aug 2015 10:37:53 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NTS00LGE7V3VUD0@mtaout29.012.net.il>; Fri, 28 Aug 2015 10:37:53 +0300 (IDT) In-reply-to: <55E0085D.3000404@cs.ucla.edu> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.185 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:189249 Archived-At: > From: Paul Eggert > Date: Fri, 28 Aug 2015 00:06:05 -0700 > > It would simplify things somewhat to remove the text-quoting-style variable, and > to have Emacs behave as it does now when text-quoting-style is nil: namely, > generate curved quotes in buffers and strings if displayable, and generate grave > accent and apostrophe otherwise. That should suffice for Alan's preferences, as > he can run Emacs in an environment where curved quotes aren't displayable, e.g., > with LC_ALL=C in the environment. Telling people who don't see the Unicode quotes to run under LC_ALL=C is not a good idea, for at least two reasons: . on platforms that honor LC_ALL in the environment, it will disable many useful Emacs features unrelated to the issue at hand . on platforms that don't honor LC_ALL in the environment (Windows), it won't have any effect > It sounds like you may be thinking of something even simpler, though: namely, > always generate curved quotes in strings and buffers, but display them as grave > accent and apostrophe if curved quotes are not displayable. I'd prefer that > approach too, though I expect Alan would not (otherwise why introduce > text-quoting-style?). Given the controversy this generated, and few distinct flavors of what people like or dislike about it, I think it's only prudent to have this customizable. Once Emacs 25 is released, we can see from user feedback more clearly where do winds blow, and then decide whether this option should be kept or modified in some sense.