From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#52459: 28.0.90; prin1-to-string does not escape bidi control characters despite print-escape-control-characters=t Date: Tue, 14 Dec 2021 20:39:29 +0200 Message-ID: <83pmpzjaji.fsf@gnu.org> References: <83v8ztmu75.fsf@gnu.org> <93d63756-f75d-c53e-de02-2e8270d07311@daniel-mendler.de> <83r1agn184.fsf@gnu.org> <0eabc668-ecb2-8f77-17cf-f9cb6dcf0626@daniel-mendler.de> <0504d4a8-1a4b-a451-d7d3-fea1c116b96d@daniel-mendler.de> <8335mwmssm.fsf@gnu.org> <7027aad4-d156-12ae-7356-4d55be5716b1@daniel-mendler.de> <83wnk8l9ha.fsf@gnu.org> <2511c498-1e36-07b2-b9b8-5849902cd416@daniel-mendler.de> <83tufcl5qd.fsf@gnu.org> <4ac4a4ce-2bb4-4120-d52d-665a029cab4e@daniel-mendler.de> <83sfuwl4mf.fsf@gnu.org> <83r1agl3um.fsf@gnu.org> <0491af1e-b57d-c5bd-c17d-b9bc1ef34929@daniel-mendler.de> <83pmq0l2h5.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33064"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mail@daniel-mendler.de, 52459@debbugs.gnu.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Dec 14 19:40:36 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mxCj5-0008OO-Vr for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Dec 2021 19:40:36 +0100 Original-Received: from localhost ([::1]:35942 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mxCj4-00048Y-Ax for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Dec 2021 13:40:34 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:45678) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mxCiY-00048K-St for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 13:40:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:47989) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mxCiY-0007B2-JD for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 13:40:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mxCiY-00048y-8g for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 13:40:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 14 Dec 2021 18:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 52459 X-GNU-PR-Package: emacs Original-Received: via spool by 52459-submit@debbugs.gnu.org id=B52459.163950719215906 (code B ref 52459); Tue, 14 Dec 2021 18:40:02 +0000 Original-Received: (at 52459) by debbugs.gnu.org; 14 Dec 2021 18:39:52 +0000 Original-Received: from localhost ([127.0.0.1]:59535 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mxCiN-00048U-Pk for submit@debbugs.gnu.org; Tue, 14 Dec 2021 13:39:52 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:44824) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mxCiM-00048I-LC for 52459@debbugs.gnu.org; Tue, 14 Dec 2021 13:39:51 -0500 Original-Received: from [2001:470:142:3::e] (port=49896 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mxCi7-00076u-JY; Tue, 14 Dec 2021 13:39:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=rSwfEVWKmKpueP9+0TwqBUGEEQZzAyJEYRIkx8U5oZE=; b=rX2Ri4HxO/tR aOuxlQtBPTXbxJGkd8LD+JmN32/tf/5Jra8CZSjf+PlESemH7IqNLSQkVKRmql4s2sIAPIOA8UtsF /lZWB2DFDWr3KbYJ1bePbH/jrPfWYcMKE2fBfC3Z+XsAJ1eIN/0LRZIj/sNx3heUB4b6S8ct+Ra/A AoAgUPsNvccU8U1F/x2j8nmQg1rar2EV/XZ7VseXS3A0qKw3t4ZOFmeBekyB3fh7fDr0T+SAGb1qz ri8wEyKiaV3ySbvRAhpwhuZqcpzprsbD5NrLYwIlLSGec9sZL0OpSVpycinM5E9PPX6HzGhEVBZc+ Nyrw0lze/5U8mgjh+v6eLg==; Original-Received: from [87.69.77.57] (port=4860 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mxCi4-00034R-4O; Tue, 14 Dec 2021 13:39:33 -0500 In-Reply-To: (message from Dmitry Gutov on Tue, 14 Dec 2021 21:23:27 +0300) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:222382 Archived-At: > Cc: 52459@debbugs.gnu.org > From: Dmitry Gutov > Date: Tue, 14 Dec 2021 21:23:27 +0300 > > > And, to reiterate once more, I'm against partial solutions that affect > > only some functions that produce strings, and don't affect at all any > > text displayed from a buffer. It would be a broken solution, because > > we will never be able to explain why 'prin1' produces escapes whereas > > 'format' and 'message' don't. > > I just did a little testing, and it seems > 'print-escape-control-characters' only affects 'prin1-to-string' and > 'prin1' but not 'message' or 'format'. > > Is that a problem? It could be. I guess the only reason no one complained about it is that those print functions are used in very specialized cases. But in this case, the requirement was to use it for displaying human-readable text in a UI, and I think in that context it would be highly surprising, to say the least, to have it supported by prin1, but not by formatted printing APIs. > If not, adding a new variable which makes the same distinction seems > consistent with the current design. The goal is explicitly different, and specifically targets the display of text to users. And IMO that is not consistent with the current design, because these variables definitely weren't meant to affect how text is presented to users. We have other similar features for that, like nobreak-char-display etc.